Skip to content

Fix module name matching for abbreviated ocp_resources modules - #5975

Merged
vsibirsk merged 1 commit into
RedHatQE:mainfrom
OhadRevah:fix-module-name-matching
Aug 13, 2026
Merged

Fix module name matching for abbreviated ocp_resources modules#5975
vsibirsk merged 1 commit into
RedHatQE:mainfrom
OhadRevah:fix-module-name-matching

Conversation

@OhadRevah

@OhadRevah OhadRevah commented Aug 12, 2026

Copy link
Copy Markdown
Contributor
What this PR does / why we need it:

Add import-based fallback to get_ocp_resource_module_name when the exact string match fails. Some ocp_resources modules use abbreviated names (e.g. mutating_webhook_config for MutatingWebhookConfiguration). The fallback imports the module and checks if any class has a matching kind attribute.

assisted by: claude code claude-opus-4-6

Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:

Summary by CodeRabbit

  • Tests
    • Improved automated coverage for install and upgrade scenarios.
    • Test resource discovery now adapts more reliably to related object types.
    • Added clearer handling when a matching resource type cannot be found.
  • Chores
    • Simplified test setup and resource lookup behavior for easier maintenance.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 554cb94c-f077-4a7e-9ab8-c2fc64a4736c

📥 Commits

Reviewing files that changed from the base of the PR and between 08a9205 and 091f611.

📒 Files selected for processing (2)
  • tests/install_upgrade_operators/conftest.py
  • tests/install_upgrade_operators/utils.py
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • RedHatQE/openshift-virtualization-tests-design-docs (manual)

📝 Walkthrough

Walkthrough

The resource lookup utility now resolves resources directly from related objects by scanning specified ocp_resources submodules. The ocp_resource_by_name fixture uses this helper.

Changes

Related resource lookup

Layer / File(s) Summary
Direct related-resource resolution
tests/install_upgrade_operators/utils.py
The utility scans submodules for a resource class that matches the related object kind, constructs it with client, name, and optional namespace, and raises ModuleNotFoundError if no match exists.
Fixture integration
tests/install_upgrade_operators/conftest.py
The fixture import and lookup call use get_resource_from_related_object.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: hmeir, rnetser

🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title is under 120 characters and clearly describes the fix for abbreviated ocp_resources module matching.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Pr Template Sections ✅ Passed The live PR body includes all four required headings, and the first section contains specific non-placeholder content describing the fallback and abbreviated module names.
Stp Link Required ✅ Passed The PR diff only modifies conftest.py and utils.py; it adds no test_.py file or def test_ function under tests/.
Stp Scenario Coverage ✅ Passed The PR changes only tests/install_upgrade_operators/conftest.py and utils.py; it does not add, modify, or delete any tests/**/test_*.py file, so this check is inapplicable.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified
  • Labels: Enabled categories: branch, can-be-merged, cherry-pick, has-conflicts, hold, needs-rebase, size, verified, wip

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (PR author or approvers)
  • /hold cancel - Unblock PR merging (PR author or approvers)
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status
  • /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
  • /regenerate-welcome - Regenerate this welcome message
  • /security-override - Set security check runs to pass (maintainers only)
  • /security-override cancel - Re-run security checks

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest build-container - Rebuild and test container image
  • /retest verify-bugs-are-open - verify-bugs-are-open
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3
  • /cherry-pick-retry <branch> - Retry a failed cherry-pick (merged PRs only)

Branch Management

  • /rebase - Rebase this PR branch onto its base branch

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 2 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
  5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • OhadRevah
  • RoniKishner
  • albarker-rh
  • dshchedr
  • hmeir
  • rlobillo
  • rnetser
  • vsibirsk
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
AI Features
  • Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6-1m)
Security Checks
  • Suspicious Path Detection: Monitors paths: .claude/, .vscode/, .cursor/, .devcontainer/, .pi/, .github/workflows/, .github/actions/
  • Committer Identity Check: Verifies last committer matches PR author
  • Mandatory: Security checks block merge (use /security-override to bypass — maintainers only)

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

📌 Additional Information

Custom Commands:

  • /test-plan — Triggers CodeRabbit to analyze the PR's changed files and post a test execution plan
  • /rerun-smoke — Adds retest-smoke label on the PR to trigger smoke tests execution

For more information, please refer to the project documentation or contact the maintainers.

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

Comment thread tests/install_upgrade_operators/utils.py Outdated
@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-5975 published

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/verified

All tests passed for PR #5975.
Job: openshift-virtualization-tests-runner #6135

Execution details
pytest tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py -s -o log_cli=true -m tier2 --jira
Image: openshift-virtualization-tests:pr-5975

@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-5975 published

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the full Test Execution Plan (smoke decision, gating decision, and specific affected tests).
Do NOT submit a blocking review event (REQUEST_CHANGES/APPROVE).
Post a single inline PR comment on Files Changed (non-blocking COMMENT flow).

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file

  2. Identify affected code paths, functions, and classes

  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes

  4. Trace test dependencies through imports, shared utilities, fixture inheritance, fixture teardown, and yield from cleanup in conftest

  5. Detect new tests introduced in the PR

  6. Utilities and libs impact (when utilities/ or libs/ changes):
    You MUST use shell scripts (rg, git diff) to trace the full impact.
    Follow these sub-steps in order:

    6a. Identify modified symbols: For each changed file under utilities/ or libs/,
    list every modified function or method.
    Example: git diff HEAD~1 --unified=0 -- utilities/hco.py | grep '^[+-]def '

    6b. Find direct callers: Search tests and conftest for each symbol from 6a.
    Example: rg -l 'get_hco_version' tests/

    6c. Trace fixture teardown and cleanup: Find fixtures that reach
    the modified symbol through yield from or context-manager wrappers.
    Example: rg -l 'yield from.*enable_common_boot|def.*enable_common_boot' tests/

    6d. Trace same-file callers: In each changed file, find other functions
    whose body calls a modified symbol (including code after yield
    in @contextmanager helpers).
    Example: rg 'get_hco_version|enable_common_boot' utilities/hco.py

    6e. Expand transitively: If function A calls modified B, then
    tests/fixtures that call A are affected — even when the test body
    never imports B directly.

    Do NOT limit impact to tests that import the modified symbol only.

  7. Smoke test impact: Intersect the affected set from step 6 with smoke-marked tests.
    Run: rg -l '@pytest.mark.smoke' tests/
    VERIFY the above command returned actual file paths before concluding False.
    Set True if either condition is met:

    • a smoke-marked file appears in the affected set from 6b-6e, OR
    • any conftest.py in the smoke test's parent-directory hierarchy (up to repo root)
      imports or calls a modified utilities/libs symbol — including autouse fixtures
      that depend on modified functions. ALL tests in that directory and below are affected.
      Example check: for each smoke_file, scan dirname(smoke_file)/conftest.py,
      dirname(dirname(smoke_file))/conftest.py, etc. for modified symbol imports
      and autouse fixtures that depend on modified symbols.
  8. Gating test impact: Intersect the affected set from step 6 with gating-marked tests.
    Run: rg -l '@pytest.mark.gating' tests/
    Set True if a gating-marked file also appears in the affected set from 6b-6e.
    Utilities/libs changes often affect gating tests without affecting smoke tests.
    Do NOT stop analysis after concluding Run smoke tests: False.

Output rules:
Do NOT include analysis step numbers (1-8) in your visible output.

Your deliverable:
Your inline informational comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False — If True, state the dependency path (test → fixture → changed symbol). True ONLY with a verified path.
  • Run gating tests: True / False — If True, state the dependency path. True if any gating-marked test is in the affected set.
  • Affected tests to run (required when utilities/, libs/, or shared conftest changes — list concrete paths even when smoke is False)

Use these formats:

  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When a marker covers multiple affected tests (e.g. -m gating only if ALL gating tests in scope need run)
  • Tag each listed test or group with its marker when not obvious, e.g. (gating) or (smoke)

Real test commands (MANDATORY when changes affect session/runtime code):

When the affected code runs at session/collection time (conftest fixtures, pytest plugins,
config hooks, session-scoped setup) or modifies runtime behavior that unit tests mock away,
you MUST include concrete pytest commands the PR author must run on a real cluster
to verify the change works end-to-end. Include:

  • A command for the error/fix path (the scenario the PR fixes)
  • A command for the happy path (regression: the normal case still works)
  • Use lightweight tests (e.g., --collect-only for startup failures,
    a single small test for runtime behavior)
    If the PR only changes test logic (not utilities/libs/conftest), the affected test
    paths themselves serve as the real test commands — no separate section needed.

Example output for a session-startup fix:

**Real tests (cluster required)**
Error path (the fix):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=nonexistent-sc --collect-only`
Expected: ValueError with clear message, not IndexError

Happy path (regression):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=<valid-sc> -k test_bar`
Expected: session starts normally

Guidelines:

  • Include tests affected directly OR via fixture setup/teardown, yield from cleanup, or transitive utility call chains (caller calls modified helper)
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name when only specific tests use an affected fixture or utility wrapper (preferred for partial file impact)
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal
  • Example: if leaf helper foo() changes, include tests whose fixture teardown calls wrapper bar() where bar() calls foo(), even when the test body only imports an unrelated symbol from the same utilities module

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post one non-blocking inline comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If inline comment API calls fail after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL — Verification rules for smoke and gating decisions:
- For each True decision, you must have traced a concrete path: test file → fixture → utility function → modified symbol.
- Do NOT assume impact based on scope, file proximity, or infrastructure-sounding names.
Only set True when you trace a concrete path through steps 6a-6e, then 7 or 8.
WRONG: "utilities/hco.py changed → run smoke" (no traced dependency path)
WRONG: "Run smoke tests: False" with no affected-test list when gating tests use the changed utility
RIGHT: "Run smoke tests: False, Run gating tests: True" plus tests/.../test_foo.py::TestBar::test_baz (gating)
RIGHT: "Smoke test X uses fixture Y → wrapper Z → changed function W in utilities/hco.py"

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/verified

All tests passed for PR #5975.
Job: openshift-virtualization-tests-runner #6136

Execution details
pytest tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py -s -o log_cli=true -m tier2 --jira
Image: openshift-virtualization-tests:pr-5975

Comment thread tests/install_upgrade_operators/utils.py Outdated
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr=5975

echo '=== PR metadata ==='
gh pr view "$pr" --repo "$repo" --json baseRefName,headRefName,files --jq '{baseRefName, headRefName, files: [.files[].path]}'

echo '=== Changed files and zero-context diff ==='
git diff --find-renames --unified=0 "origin/$(gh pr view "$pr" --repo "$repo" --json baseRefName --jq .baseRefName)...HEAD"

echo '=== Repository status and recent commit diff ==='
git status --short
git diff --find-renames --unified=0 HEAD~1..HEAD || true

Length of output: 1133


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr=5975

echo '=== PR file patch and changed-line data ==='
gh api "repos/$repo/pulls/$pr/files?per_page=100" \
  --jq '.[] | {filename, status, previous_filename, additions, deletions, patch}'

echo '=== Changed utility outline ==='
ast-grep outline tests/install_upgrade_operators/utils.py --items all --view expanded

echo '=== get_ocp_resource_module_name definition and same-file callers ==='
rg -n -C 8 '\b(get_ocp_resource_module_name|resource_factory)\b' tests/install_upgrade_operators/utils.py || true

echo '=== Direct imports/calls in tests and conftest files ==='
rg -n -C 4 --glob '*.py' \
  'from tests\.install_upgrade_operators\.utils import.*\bget_ocp_resource_module_name\b|import tests\.install_upgrade_operators\.utils|\bget_ocp_resource_module_name\s*\(' \
  tests || true

echo '=== Smoke and gating marker files ==='
rg -l --glob '*.py' '`@pytest`\.mark\.smoke' tests || true
echo '-- gating --'
rg -l --glob '*.py' '`@pytest`\.mark\.gating' tests || true

echo '=== Relevant conftest files ==='
fd --type f --glob 'conftest.py' tests | sort

Length of output: 14835


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== Wrapper imports and calls ==='
rg -n -C 5 --glob '*.py' \
  '\b(get_resource_from_module_name|get_ocp_resource_module_name)\b' tests \
  || true

echo '=== Importers and calls of the install/upgrade utils module ==='
rg -n -C 5 --glob '*.py' \
  '(from tests\.install_upgrade_operators\.utils import|import tests\.install_upgrade_operators\.utils|from \.\.?utils import)' \
  tests/install_upgrade_operators \
  || true

echo '=== Relevant wrapper implementation ==='
sed -n '210,300p' tests/install_upgrade_operators/utils.py

echo '=== Install/upgrade conftest call graph candidates ==='
rg -n -C 6 --glob 'conftest.py' \
  '\b(get_resource_from_module_name|get_ocp_resource_module_name)\b|tests\.install_upgrade_operators\.utils' \
  tests \
  || true

echo '=== Parent conftest checks for all smoke-marked files ==='
while IFS= read -r smoke_file; do
  echo "-- $smoke_file"
  dir="$(dirname "$smoke_file")"
  while [ "$dir" != "." ]; do
    if [ -f "$dir/conftest.py" ]; then
      matches="$(rg -n -C 2 '\b(get_resource_from_module_name|get_ocp_resource_module_name)\b|tests\.install_upgrade_operators\.utils' "$dir/conftest.py" || true)"
      if [ -n "$matches" ]; then
        printf '%s\n' "$matches"
      fi
    fi
    dir="$(dirname "$dir")"
  done
done < <(rg -l --glob '*.py' '`@pytest`\.mark\.smoke' tests)

echo '=== Markers and test definitions in affected candidate files ==='
rg -n -C 3 --glob '*.py' \
  '`@pytest`\.mark\.(smoke|gating)|^\s*(async\s+)?def test_|^\s*class Test' \
  tests/install_upgrade_operators \
  || true

Length of output: 30241


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== Direct and dynamic consumers of ocp_resource_by_name ==='
rg -n -C 6 --glob '*.py' \
  '\bocp_resource_by_name\b|getfixturevalue\(\s*["'\'']ocp_resource_by_name["'\'']\s*\)' \
  tests || true

echo '=== Fixture implementation and adjacent fixture dependencies ==='
sed -n '220,270p' tests/install_upgrade_operators/conftest.py

echo '=== Candidate test markers, definitions, and fixture arguments ==='
rg -n -C 4 --glob '*.py' \
  '`@pytest`\.mark\.(smoke|gating)|^\s*(async\s+)?def test_.*\bocp_resource_by_name\b|^\s*class Test' \
  tests/install_upgrade_operators || true

echo '=== All smoke test parent conftest files: affected-symbol check ==='
for f in $(rg -l --glob '*.py' '`@pytest`\.mark\.smoke' tests); do
  echo "-- $f"
  d="$(dirname "$f")"
  while :; do
    if [ -f "$d/conftest.py" ]; then
      rg -n -C 2 '\b(get_resource_from_module_name|get_ocp_resource_module_name|ocp_resource_by_name)\b' "$d/conftest.py" || true
    fi
    [ "$d" = "tests" ] && break
    d="$(dirname "$d")"
  done
done

echo '=== All gating test parent conftest files: affected-symbol check ==='
for f in $(rg -l --glob '*.py' '`@pytest`\.mark\.gating' tests); do
  d="$(dirname "$f")"
  while :; do
    if [ -f "$d/conftest.py" ] && rg -q '\b(get_resource_from_module_name|get_ocp_resource_module_name|ocp_resource_by_name)\b' "$d/conftest.py"; then
      echo "-- $f via $d/conftest.py"
      rg -n -C 2 '\b(get_resource_from_module_name|get_ocp_resource_module_name|ocp_resource_by_name)\b' "$d/conftest.py"
    fi
    [ "$d" = "tests" ] && break
    d="$(dirname "$d")"
  done
done

Length of output: 77947


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== Relationship-label test and its parametrization ==='
sed -n '1,150p' tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py

echo '=== Strict-reconciliation related-object test and its parametrization ==='
sed -n '1,120p' tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py

echo '=== Related-object fixture matrix and submodule list ==='
rg -n -C 8 --glob '*.py' \
  '\b(ocp_resources_submodule_list|cnv_related_object_matrix__function__|hco_status_related_objects)\b' \
  tests/install_upgrade_operators tests/conftest.py || true

echo '=== MutatingWebhookConfiguration parameter references ==='
rg -n -C 4 --glob '*.py' \
  '\b(MutatingWebhookConfiguration|mutating_webhook_config)\b' \
  tests || true

Length of output: 22374


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '=== Matrix fixture and parametrization hook ==='
rg -n -C 12 --glob '*.py' \
  '\bcnv_related_object_matrix__function__\b|def pytest_generate_tests\b|related.object.matrix' \
  . || true

echo '=== All related-object constants and abbreviated-module entries ==='
rg -n -i -C 8 --glob '*.py' \
  'mutating.?webhook|related.objects|related_object' \
  tests/install_upgrade_operators/constants.py tests/conftest.py tests/install_upgrade_operators/conftest.py 2>/dev/null || true

echo '=== Current PR review state and review API schema sample ==='
gh api "repos/RedHatQE/openshift-virtualization-tests/pulls/5975/reviews?per_page=10" \
  --jq '.[] | {user: .user.login, state, body, id}' || true

Length of output: 13549


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr=5975
head_sha="$(gh pr view "$pr" --repo "$repo" --json headRefOid --jq .headRefOid)"

body=$(cat <<'EOF'
## Test Execution Plan

- **Run smoke tests: False** — No smoke-marked test requests the non-autouse `ocp_resource_by_name` fixture.
- **Run gating tests: True** — `tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py::TestRelationshipLabels::test_verify_relationship_labels_hco_components` (gating) → `ocp_resource_by_name` → `get_resource_from_module_name` → `get_ocp_resource_module_name`.

**Affected tests to run**
- `tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py::TestRelationshipLabels::test_verify_relationship_labels_hco_components` (gating)
- `tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py::TestRelatedObjects::test_hco_related_objects`

**Real tests (cluster required)**

Error path (abbreviated `ocp_resources` module):
`pytest tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py::TestRelationshipLabels::test_verify_relationship_labels_hco_components -o log_cli=true`
Expected: every HCO related-object matrix entry resolves to its `ocp_resources` class. An abbreviated module name resolves by its class `kind`.

Happy path (normal module-name match):
`pytest tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py::TestRelatedObjects::test_hco_related_objects -o log_cli=true`
Expected: related objects resolve and label reconciliation completes.
EOF
)

gh api --method POST "repos/$repo/pulls/$pr/comments" \
  -f body="$body" \
  -f commit_id="$head_sha" \
  -f path="tests/install_upgrade_operators/utils.py" \
  -F line=228 \
  -f side="RIGHT" \
  --jq '{id, path, line, side}'

Length of output: 2119


You are interacting with an AI system.

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:pr-5975 published

Replace get_ocp_resource_module_name, get_resource, and
get_resource_from_module_name with a single get_resource_from_related_object
function. Instead of string-matching module names against kind, it imports
each module and checks if the class kind attribute matches.

Fixes MutatingWebhookConfiguration lookup failure where the module name
(mutating_webhook_config) doesn't match the kind when underscores are
stripped (mutatingwebhookconfig != mutatingwebhookconfiguration).

Signed-off-by: Ohad <orevah@redhat.com>
assisted by: claude code claude-opus-4-6
@OhadRevah
OhadRevah force-pushed the fix-module-name-matching branch from 091f611 to 2be85be Compare August 12, 2026 11:26
@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

Clean rebase detected — no code changes compared to previous head (091f611).
The following labels were preserved: commented-OhadRevah.

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/verified

All tests passed for PR #5975.
Job: openshift-virtualization-tests-runner #6139

Execution details
pytest tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py -s -o log_cli=true -m tier2 --jira
Image: openshift-virtualization-tests:pr-5975

@openshift-virtualization-qe-bot-3

Copy link
Copy Markdown
Contributor

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the full Test Execution Plan (smoke decision, gating decision, and specific affected tests).
Do NOT submit a blocking review event (REQUEST_CHANGES/APPROVE).
Post a single inline PR comment on Files Changed (non-blocking COMMENT flow).

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

  1. Examine code changes in each modified file

  2. Identify affected code paths, functions, and classes

  3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes

  4. Trace test dependencies through imports, shared utilities, fixture inheritance, fixture teardown, and yield from cleanup in conftest

  5. Detect new tests introduced in the PR

  6. Utilities and libs impact (when utilities/ or libs/ changes):
    You MUST use shell scripts (rg, git diff) to trace the full impact.
    Follow these sub-steps in order:

    6a. Identify modified symbols: For each changed file under utilities/ or libs/,
    list every modified function or method.
    Example: git diff HEAD~1 --unified=0 -- utilities/hco.py | grep '^[+-]def '

    6b. Find direct callers: Search tests and conftest for each symbol from 6a.
    Example: rg -l 'get_hco_version' tests/

    6c. Trace fixture teardown and cleanup: Find fixtures that reach
    the modified symbol through yield from or context-manager wrappers.
    Example: rg -l 'yield from.*enable_common_boot|def.*enable_common_boot' tests/

    6d. Trace same-file callers: In each changed file, find other functions
    whose body calls a modified symbol (including code after yield
    in @contextmanager helpers).
    Example: rg 'get_hco_version|enable_common_boot' utilities/hco.py

    6e. Expand transitively: If function A calls modified B, then
    tests/fixtures that call A are affected — even when the test body
    never imports B directly.

    Do NOT limit impact to tests that import the modified symbol only.

  7. Smoke test impact: Intersect the affected set from step 6 with smoke-marked tests.
    Run: rg -l '@pytest.mark.smoke' tests/
    VERIFY the above command returned actual file paths before concluding False.
    Set True if either condition is met:

    • a smoke-marked file appears in the affected set from 6b-6e, OR
    • any conftest.py in the smoke test's parent-directory hierarchy (up to repo root)
      imports or calls a modified utilities/libs symbol — including autouse fixtures
      that depend on modified functions. ALL tests in that directory and below are affected.
      Example check: for each smoke_file, scan dirname(smoke_file)/conftest.py,
      dirname(dirname(smoke_file))/conftest.py, etc. for modified symbol imports
      and autouse fixtures that depend on modified symbols.
  8. Gating test impact: Intersect the affected set from step 6 with gating-marked tests.
    Run: rg -l '@pytest.mark.gating' tests/
    Set True if a gating-marked file also appears in the affected set from 6b-6e.
    Utilities/libs changes often affect gating tests without affecting smoke tests.
    Do NOT stop analysis after concluding Run smoke tests: False.

Output rules:
Do NOT include analysis step numbers (1-8) in your visible output.

Your deliverable:
Your inline informational comment will be based on the following requirements:

Test Execution Plan

  • Run smoke tests: True / False — If True, state the dependency path (test → fixture → changed symbol). True ONLY with a verified path.
  • Run gating tests: True / False — If True, state the dependency path. True if any gating-marked test is in the affected set.
  • Affected tests to run (required when utilities/, libs/, or shared conftest changes — list concrete paths even when smoke is False)

Use these formats:

  • path/to/test_file.py - When the entire test file needs verification
  • path/to/test_file.py::TestClass::test_method - When specific test(s) needed
  • path/to/test_file.py::test_function - When specific test(s) needed
  • -m marker - When a marker covers multiple affected tests (e.g. -m gating only if ALL gating tests in scope need run)
  • Tag each listed test or group with its marker when not obvious, e.g. (gating) or (smoke)

Real test commands (MANDATORY when changes affect session/runtime code):

When the affected code runs at session/collection time (conftest fixtures, pytest plugins,
config hooks, session-scoped setup) or modifies runtime behavior that unit tests mock away,
you MUST include concrete pytest commands the PR author must run on a real cluster
to verify the change works end-to-end. Include:

  • A command for the error/fix path (the scenario the PR fixes)
  • A command for the happy path (regression: the normal case still works)
  • Use lightweight tests (e.g., --collect-only for startup failures,
    a single small test for runtime behavior)
    If the PR only changes test logic (not utilities/libs/conftest), the affected test
    paths themselves serve as the real test commands — no separate section needed.

Example output for a session-startup fix:

**Real tests (cluster required)**
Error path (the fix):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=nonexistent-sc --collect-only`
Expected: ValueError with clear message, not IndexError

Happy path (regression):
`pytest tests/storage/.../test_foo.py --storage-class-matrix=<valid-sc> -k test_bar`
Expected: session starts normally

Guidelines:

  • Include tests affected directly OR via fixture setup/teardown, yield from cleanup, or transitive utility call chains (caller calls modified helper)
  • Use a full file path only if ALL tests in that file require verification
  • Use file path + test name when only specific tests use an affected fixture or utility wrapper (preferred for partial file impact)
  • If a test marker can cover multiple files/tests, provide the marker
  • Balance coverage vs over-testing - Keep descriptions minimal
  • Example: if leaf helper foo() changes, include tests whose fixture teardown calls wrapper bar() where bar() calls foo(), even when the test body only imports an unrelated symbol from the same utilities module

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

  • Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
  • Test Plan: MUST verify both WITH and WITHOUT hardware:
    • Run affected tests on cluster WITH hardware
    • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

  1. YOUR ONLY DELIVERABLE: Post one non-blocking inline comment containing the test execution plan on the first changed line
  2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
  3. FALLBACK ONLY: If inline comment API calls fail after retrying, post as a regular PR comment
  4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

  • ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
  • ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
  • ❌ Do NOT add any follow-up comments after submitting the review
  • ❌ Do NOT reply to confirm task completion
  • ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL — Verification rules for smoke and gating decisions:
- For each True decision, you must have traced a concrete path: test file → fixture → utility function → modified symbol.
- Do NOT assume impact based on scope, file proximity, or infrastructure-sounding names.
Only set True when you trace a concrete path through steps 6a-6e, then 7 or 8.
WRONG: "utilities/hco.py changed → run smoke" (no traced dependency path)
WRONG: "Run smoke tests: False" with no affected-test list when gating tests use the changed utility
RIGHT: "Run smoke tests: False, Run gating tests: True" plus tests/.../test_foo.py::TestBar::test_baz (gating)
RIGHT: "Smoke test X uses fixture Y → wrapper Z → changed function W in utilities/hco.py"

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5975"

echo '=== PR metadata and changed files ==='
gh pr view "$pr" --repo "$repo" --json headRefOid,baseRefName,files \
  --jq '{headRefOid, baseRefName, files: [.files[] | {path, additions, deletions}]}'

echo '=== Current PR diff ==='
base="$(gh pr view "$pr" --repo "$repo" --json baseRefName --jq .baseRefName)"
git diff --find-renames --unified=20 "origin/$base...HEAD" -- \
  tests/install_upgrade_operators/conftest.py \
  tests/install_upgrade_operators/utils.py

echo '=== First changed line anchors ==='
gh api "repos/$repo/pulls/$pr/files?per_page=100" \
  --jq '.[] | {filename, patch}'

echo '=== Changed-file outlines ==='
ast-grep outline tests/install_upgrade_operators/conftest.py --items all --view expanded
ast-grep outline tests/install_upgrade_operators/utils.py --items all --view expanded

echo '=== Changed helper and fixture call sites ==='
rg -n -C 6 --glob '*.py' \
  '\b(get_resource_from_related_object|get_resource_from_module_name|get_ocp_resource_module_name|ocp_resource_by_name)\b' \
  tests

echo '=== Marker declarations and affected-test definitions ==='
rg -n -C 3 --glob '*.py' \
  '`@pytest`\.mark\.(smoke|gating)|^\s*(async\s+)?def test_|^\s*class Test' \
  tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py \
  tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py

echo '=== Smoke and gating files ==='
rg -l --glob '*.py' '`@pytest`\.mark\.smoke' tests | sort
echo '-- gating --'
rg -l --glob '*.py' '`@pytest`\.mark\.gating' tests | sort

echo '=== Parent conftest references for smoke and gating tests ==='
for marker in smoke gating; do
  while IFS= read -r test_file; do
    dir="$(dirname "$test_file")"
    while :; do
      if [ -f "$dir/conftest.py" ]; then
        matches="$(rg -n -C 2 '\b(get_resource_from_related_object|get_resource_from_module_name|get_ocp_resource_module_name|ocp_resource_by_name)\b' "$dir/conftest.py" || true)"
        if [ -n "$matches" ]; then
          echo "-- $marker: $test_file via $dir/conftest.py"
          printf '%s\n' "$matches"
        fi
      fi
      [ "$dir" = "tests" ] && break
      dir="$(dirname "$dir")"
    done
  done < <(rg -l --glob '*.py' "`@pytest`\\.mark\\.$marker" tests)
done

Length of output: 2454


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr="5975"
api="repos/$repo"

head_sha="$(gh pr view "$pr" --repo "$repo" --json headRefOid --jq .headRefOid)"
echo "=== Head SHA ==="
printf '%s\n' "$head_sha"

echo '=== Changed files and patches ==='
gh api "$api/pulls/$pr/files?per_page=100" \
  --jq '.[] | {filename, additions, deletions, patch}'

echo '=== Relevant current files ==='
for path in \
  tests/install_upgrade_operators/conftest.py \
  tests/install_upgrade_operators/utils.py \
  tests/install_upgrade_operators/relationship_labels/test_relationship_labels.py \
  tests/install_upgrade_operators/strict_reconciliation/test_hco_related_objects.py \
  tests/conftest.py \
  tests/install_upgrade_operators/constants.py
do
  echo "--- $path"
  gh api -H 'Accept: application/vnd.github.raw+json' \
    "$api/contents/$path?ref=$head_sha" || true
done

echo '=== Python test tree ==='
gh api "$api/git/trees/$head_sha?recursive=1" \
  --jq '.tree[] | select(.type == "blob" and (.path | startswith("tests/")) and (.path | endswith(".py"))) | .path' \
  > /tmp/test_paths.txt

echo '=== Candidate marker and fixture consumers ==='
while IFS= read -r path; do
  content="$(gh api -H 'Accept: application/vnd.github.raw+json' "$api/contents/$path?ref=$head_sha")"
  if grep -Eq '`@pytest`\.mark\.(smoke|gating)|\bocp_resource_by_name\b|\bget_resource_from_related_object\b' <<<"$content"; then
    echo "--- $path"
    grep -nE -C 3 '`@pytest`\.mark\.(smoke|gating)|\bocp_resource_by_name\b|\bget_resource_from_related_object\b|^\s*(async\s+)?def test_|^\s*class Test' <<<"$content" || true
  fi
done < /tmp/test_paths.txt

Length of output: 1740


@openshift-virtualization-qe-bot-3 Verification failed because repository and GitHub API access were unavailable. I could not verify the current diff, dependency paths, or inline comment anchor. Please retry the request after repository access is available.

You are interacting with an AI system.

@vsibirsk

Copy link
Copy Markdown
Collaborator

/approve

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Successfully removed PR tag: quay.io/openshift-cnv/openshift-virtualization-tests:pr-5975.

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:latest published

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants