Skip to content

refactor(iuo): migrate iuo and observability imports to submodules#5316

Open
vsibirsk wants to merge 2 commits into
RedHatQE:mainfrom
vsibirsk:vk-migrate-iuo-imports
Open

refactor(iuo): migrate iuo and observability imports to submodules#5316
vsibirsk wants to merge 2 commits into
RedHatQE:mainfrom
vsibirsk:vk-migrate-iuo-imports

Conversation

@vsibirsk

@vsibirsk vsibirsk commented Jun 23, 2026

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

Replace from utilities.constants import with direct submodule imports in tests/install_upgrade_operators/ and tests/observability/. Images remains on the package shim in two observability files until the compat layer is removed.

Generated-by: Claude Sonnet 4.6

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

This is a next PR in a series.
https://redhat.atlassian.net/browse/CNV-80952 and a follow up of #5188

jira-ticket:

https://redhat.atlassian.net/browse/CNV-89563

Summary by CodeRabbit

  • Chores
    • Updated the test suite to reference constants from more specific submodules (e.g., timeouts, components, architecture, cluster, monitoring), replacing broader shared imports.
    • This improves consistency and readability across tests without changing test logic or expected outcomes.

@openshift-virtualization-qe-bot-5

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 (approvers only)
  • /hold cancel - Unblock PR merging
  • /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

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

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@vsibirsk, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 20 minutes and 2 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7d592e44-2b4a-4428-b5d9-44cc2282d902

📥 Commits

Reviewing files that changed from the base of the PR and between 13e8cfe and 3426290.

📒 Files selected for processing (3)
  • tests/install_upgrade_operators/conftest.py
  • tests/install_upgrade_operators/deployment/test_hco_deployment_params.py
  • tests/install_upgrade_operators/pod_validation/test_pod_spec.py
📝 Walkthrough

Walkthrough

This PR changes test imports to use specific utilities.constants.* submodules instead of the flat utilities.constants module across install/upgrade operator and observability tests. No test logic, fixtures, or assertions change.

Changes

Constants submodule import migration

Layer / File(s) Summary
Import path updates
tests/install_upgrade_operators/cert_renewal/*, tests/install_upgrade_operators/conftest.py, tests/install_upgrade_operators/console_cli_download/*, tests/install_upgrade_operators/crds_cluster_readers_role/*, tests/install_upgrade_operators/crypto_policy/*, tests/install_upgrade_operators/csv/*, tests/install_upgrade_operators/daemonset/*, tests/install_upgrade_operators/deployment/*, tests/install_upgrade_operators/feature_gates/*, tests/install_upgrade_operators/hco_enablement_golden_image_updates/*, tests/install_upgrade_operators/json_patch/*, tests/install_upgrade_operators/launcher_updates/*, tests/install_upgrade_operators/must_gather/*, tests/install_upgrade_operators/node_component/*, tests/install_upgrade_operators/pod_security/*, tests/install_upgrade_operators/pod_validation/*, tests/install_upgrade_operators/product_install/*, tests/install_upgrade_operators/product_uninstall/*, tests/install_upgrade_operators/product_upgrade/*, tests/install_upgrade_operators/relationship_labels/*, tests/install_upgrade_operators/security/scc/*, tests/install_upgrade_operators/single_node_tests/*, tests/install_upgrade_operators/strict_reconciliation/*, tests/install_upgrade_operators/utils.py
Flat constant imports were replaced with targeted imports from utilities.constants.components, .hco, .timeouts, .architecture, .cluster, .networking, .namespaces, .pytest, .storage, .virt, .monitoring, and related submodules.
Import path updates
tests/observability/metrics/conftest.py, tests/observability/metrics/test_*.py, tests/observability/metrics/utils.py, tests/observability/runbook_url/*, tests/observability/upgrade/*, tests/observability/utils.py
Flat constant imports were replaced with targeted imports from utilities.constants.components, .monitoring, .timeouts, .pytest, .storage, .virt, .images, .instance_types, and .networking.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • rlobillo
  • hmeir
  • geetikakay
  • dshchedr
  • rnetser
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise, under 120 characters, and clearly matches the import-refactor changes.
Description check ✅ Passed The description follows the required template and covers the PR purpose, reviewer notes, and Jira ticket.
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.
Stp Link Required ✅ Passed No newly added test files or def test_* functions appeared in the diff; only import refactors in existing tests were changed.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Linked repositories: Your configuration references 1 linked repositories, but your current plan allows 0. Analyzed ``, skipped RedHatQE/openshift-virtualization-tests-design-docs.


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.

@vsibirsk vsibirsk changed the title refactor(constants): migrate iuo and observability imports to submodules refactor(iuo): migrate iuo and observability imports to submodules Jun 23, 2026
@vsibirsk

Copy link
Copy Markdown
Collaborator Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

@coderabbitai full review

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Full review finished.

coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 23, 2026
Replace `from utilities.constants import` with direct submodule imports in
tests/install_upgrade_operators/ and tests/observability/. Images remains on
the package shim in two observability files until the compat layer is removed.

Generated-by: Claude Sonnet 4.6
Signed-off-by: vsibirsk <vsibirsk@redhat.com>
@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"

HCO_CR_CERT_CONFIG_SERVER_KEY,
)
from utilities.constants import TIMEOUT_1MIN, TIMEOUT_11MIN
from utilities.constants.timeouts import (

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test Execution Plan

Run smoke tests: False
No traced path: tests/install_upgrade_operators/csv/test_csv.py (smoke-marked) was not modified, and no utilities/ or libs/ symbols were changed in this PR to create a transitive dependency.

Run gating tests: True
Direct modification path:

  • tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py — file directly modified (import refactor), carries @pytest.mark.gating
  • tests/install_upgrade_operators/deployment/test_hco_deployment_params.py — file directly modified (import refactor), carries @pytest.mark.gating

Affected tests to run

All changes are pure import-path refactoring (no logic changes). A --collect-only run was already verified (893/904 collected). The affected gating tests should be smoke-checked for import resolution:

tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py  (gating)
tests/install_upgrade_operators/deployment/test_hco_deployment_params.py  (gating)

Real tests (cluster required)

Happy path (regression — verify imports resolve at collection time):

pytest tests/install_upgrade_operators/ tests/observability/ --collect-only

Expected: all tests collect without ImportError (already confirmed: 893/904 collected).

Targeted gating run:

pytest tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py tests/install_upgrade_operators/deployment/test_hco_deployment_params.py -m gating

@coderabbitai

coderabbitai Bot commented Jun 24, 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

PR_NUMBER=5316
REPO="RedHatQE/openshift-virtualization-tests"

echo "=== PR Files Changed (first file) ==="
gh pr view "$PR_NUMBER" --repo "$REPO" --json files --jq '.files[0]'

echo ""
echo "=== All changed files ==="
gh pr view "$PR_NUMBER" --repo "$REPO" --json files --jq '[.files[].path]'

echo ""
echo "=== Check smoke markers in affected test dirs ==="
rg -l '`@pytest.mark.smoke`' tests/install_upgrade_operators/ tests/observability/ 2>/dev/null || echo "No smoke markers found"

echo ""
echo "=== Check gating markers in affected test dirs ==="
rg -l '`@pytest.mark.gating`' tests/install_upgrade_operators/ tests/observability/ 2>/dev/null || echo "No gating markers found"

echo ""
echo "=== Get PR diff to find first changed file and line number ==="
gh api "repos/$REPO/pulls/$PR_NUMBER/files" --jq '.[0] | {filename: .filename, patch: .patch}' | head -50

Length of output: 7746


🏁 Script executed:

#!/bin/bash
set -euo pipefail

PR_NUMBER=5316
REPO="RedHatQE/openshift-virtualization-tests"

# Get the latest commit SHA for the PR
COMMIT_SHA=$(gh api "repos/$REPO/pulls/$PR_NUMBER" --jq '.head.sha')
echo "Commit SHA: $COMMIT_SHA"

# Post inline review comment on the first changed line of the first file
# File: tests/install_upgrade_operators/cert_renewal/conftest.py
# First changed line in new file: line 22 (the `from utilities.constants.timeouts import (` line)

COMMENT_BODY="## Test Execution Plan

**Run smoke tests: False**
No traced path: \`tests/install_upgrade_operators/csv/test_csv.py\` (smoke-marked) was not modified, and no \`utilities/\` or \`libs/\` symbols were changed in this PR to create a transitive dependency.

**Run gating tests: True**
Direct modification path:
- \`tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py\` — file directly modified (import refactor), carries \`@pytest.mark.gating\`
- \`tests/install_upgrade_operators/deployment/test_hco_deployment_params.py\` — file directly modified (import refactor), carries \`@pytest.mark.gating\`

**Affected tests to run**

All changes are pure import-path refactoring (no logic changes). A \`--collect-only\` run was already verified (893/904 collected). The affected gating tests should be smoke-checked for import resolution:

\`\`\`
tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py  (gating)
tests/install_upgrade_operators/deployment/test_hco_deployment_params.py  (gating)
\`\`\`

**Real tests (cluster required)**

Happy path (regression — verify imports resolve at collection time):
\`\`\`
pytest tests/install_upgrade_operators/ tests/observability/ --collect-only
\`\`\`
Expected: all tests collect without ImportError (already confirmed: 893/904 collected).

Targeted gating run:
\`\`\`
pytest tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py tests/install_upgrade_operators/deployment/test_hco_deployment_params.py -m gating
\`\`\`"

gh api "repos/$REPO/pulls/$PR_NUMBER/comments" \
  --method POST \
  --field body="$COMMENT_BODY" \
  --field commit_id="$COMMIT_SHA" \
  --field path="tests/install_upgrade_operators/cert_renewal/conftest.py" \
  --field line=22 \
  --field side="RIGHT"

echo "Inline comment posted successfully"

Length of output: 6956



@rnetser

rnetser commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@vsibirsk

Copy link
Copy Markdown
Collaborator Author

/verified

#5316 (comment)

@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 Jun 28, 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="5316"

echo "=== First changed file metadata ==="
gh api "repos/$repo/pulls/$pr/files" --paginate \
  | jq -r '.[0] | {filename, status, additions, deletions, patch}'

echo
echo "=== All changed files ==="
gh pr view "$pr" --repo "$repo" --json files \
  --jq '.files[].path'

echo
echo "=== Changed conftest files ==="
gh pr view "$pr" --repo "$repo" --json files \
  --jq '.files[].path' | rg '/conftest\.py$|^tests/.*/conftest\.py$' || true

echo
echo "=== Changed test files with markers (smoke/gating) ==="
changed_tmp="$(mktemp)"
gh pr view "$pr" --repo "$repo" --json files --jq '.files[].path' > "$changed_tmp"
while IFS= read -r f; do
  [ -f "$f" ] || continue
  if rg -n '`@pytest`\.mark\.(smoke|gating)\b' "$f" >/dev/null 2>&1; then
    echo "--- $f"
    rg -n '`@pytest`\.mark\.(smoke|gating)\b' "$f"
  fi
done < "$changed_tmp"

echo
echo "=== All smoke files in affected top-level areas ==="
rg -l '`@pytest`\.mark\.smoke\b' tests/install_upgrade_operators tests/observability || true

echo
echo "=== All gating files in affected top-level areas ==="
rg -l '`@pytest`\.mark\.gating\b' tests/install_upgrade_operators tests/observability || true

echo
echo "=== Descendant test files under changed conftest directories with smoke/gating markers ==="
while IFS= read -r f; do
  [ -n "$f" ] || continue
  dir="$(dirname "$f")"
  echo "--- CONFTST DIR: $dir"
  fd -t f 'test_.*\.py$' "$dir" | while IFS= read -r tf; do
    if rg -n '`@pytest`\.mark\.(smoke|gating)\b' "$tf" >/dev/null 2>&1; then
      echo "FILE $tf"
      rg -n '`@pytest`\.mark\.(smoke|gating)\b' "$tf"
    fi
  done
done < <(gh pr view "$pr" --repo "$repo" --json files --jq '.files[].path' | rg '/conftest\.py$|^tests/.*/conftest\.py$' || true)

rm -f "$changed_tmp"

Length of output: 9881


🏁 Script executed:

#!/bin/bash
set -euo pipefail

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

echo "=== Parent conftest for smoke file ==="
python - <<'PY'
from pathlib import Path
smoke = Path("tests/install_upgrade_operators/csv/test_csv.py")
p = smoke.parent
while True:
    cf = p / "conftest.py"
    if cf.exists():
        print(cf)
    if p == Path(".") or str(p) == ".":
        break
    p = p.parent
PY

echo
echo "=== Changed files under directories with changed conftest.py ==="
python - <<'PY'
from pathlib import Path
import subprocess, json

repo="RedHatQE/openshift-virtualization-tests"
pr="5316"
files = subprocess.check_output(
    ["gh","pr","view",pr,"--repo",repo,"--json","files","--jq",".files[].path"],
    text=True
).splitlines()
changed = set(files)
conftests = [Path(f) for f in files if f.endswith("conftest.py")]
for cf in conftests:
    d = cf.parent
    descendants = sorted(f for f in changed if f.startswith(str(d) + "/") and f.endswith(".py") and Path(f).name != "conftest.py")
    print(f"--- {cf}")
    for f in descendants:
        print(f)
PY

echo
echo "=== Marker lines in key affected files ==="
for f in \
  tests/install_upgrade_operators/csv/test_csv.py \
  tests/install_upgrade_operators/deployment/test_hco_deployment_params.py \
  tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py \
  tests/install_upgrade_operators/product_upgrade/test_upgrade.py \
  tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py
do
  if [ -f "$f" ]; then
    echo "--- $f"
    rg -n '`@pytest`\.mark\.(smoke|gating)\b' "$f" || true
  fi
done

echo
echo "=== Post corrected inline test execution plan ==="
commit_sha="$(gh api "repos/$repo/pulls/$pr" --jq '.head.sha')"

read -r -d '' body <<'EOF' || true
## Test Execution Plan

**Run smoke tests: True**  
Dependency path: `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)` → parent `tests/install_upgrade_operators/conftest.py` (changed, imported at collection/session startup) → updated constant imports from `utilities.constants.architecture` / `utilities.constants.components`.  
Why this is required: shared `conftest.py` changes execute before tests run, so import-path regressions surface at collection time and can block the whole subtree.

**Run gating tests: True**  
Dependency paths:
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)` / `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py` → parent `tests/install_upgrade_operators/product_upgrade/conftest.py` (changed at collection/session startup)

**Affected tests to run**
- `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)`
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)`
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`

**Real tests (cluster required)**

Error/fix path (collection/session startup validation for the changed shared conftest imports):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/ tests/observability/ --collect-only`

Happy path (regression on representative smoke + gating coverage):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/csv/test_csv.py tests/install_upgrade_operators/deployment/test_hco_deployment_params.py tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py tests/install_upgrade_operators/product_upgrade/test_upgrade.py tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`
EOF

gh api "repos/$repo/pulls/$pr/comments" \
  --method POST \
  --field body="$body" \
  --field commit_id="$commit_sha" \
  --field path="tests/install_upgrade_operators/cert_renewal/conftest.py" \
  --field line=22 \
  --field side="RIGHT" >/dev/null

Length of output: 14358


🏁 Script executed:

#!/bin/bash
set -euo pipefail

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

read -r -d '' body <<'EOF' || true
## Test Execution Plan

**Run smoke tests: True**  
Dependency path: `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)` → parent `tests/install_upgrade_operators/conftest.py` (changed, imported at collection/session startup) → updated constant imports from `utilities.constants.architecture` / `utilities.constants.components`.  
Why this is required: shared `conftest.py` changes execute before tests run, so import-path regressions surface at collection time and can block the whole `tests/install_upgrade_operators/` subtree.

**Run gating tests: True**  
Dependency paths:
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)` / `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py` → parent `tests/install_upgrade_operators/product_upgrade/conftest.py` (changed at collection/session startup)

**Affected tests to run**
- `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)`
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)`
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`

**Real tests (cluster required)**

Error/fix path (collection/session startup validation for the changed shared conftest imports):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/ tests/observability/ --collect-only`

Happy path (regression on representative smoke + gating coverage):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/csv/test_csv.py tests/install_upgrade_operators/deployment/test_hco_deployment_params.py tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py tests/install_upgrade_operators/product_upgrade/test_upgrade.py tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`
EOF

# Fallback path requested by the bot when inline review comments are not possible.
gh api "repos/$repo/issues/$pr/comments" \
  --method POST \
  --field body="$body" >/dev/null

Length of output: 3325



@openshift-virtualization-qe-bot-3

CRITICAL: I could not complete the requested posting step because GitHub rejected both APIs with Resource not accessible by integration (HTTP 403):

  • inline review comment endpoint
  • fallback regular PR comment endpoint

That means this is a permissions blocker, not an analysis blocker.

Prepared Test Execution Plan to post:

## Test Execution Plan

**Run smoke tests: True**  
Dependency path: `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)` → parent `tests/install_upgrade_operators/conftest.py` (changed, imported at collection/session startup) → updated constant imports from `utilities.constants.architecture` / `utilities.constants.components`.  
Why this is required: shared `conftest.py` changes execute before tests run, so import-path regressions surface at collection time and can block the whole `tests/install_upgrade_operators/` subtree.

**Run gating tests: True**  
Dependency paths:
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)` → same file modified (import-path update)
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)` / `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py` → parent `tests/install_upgrade_operators/product_upgrade/conftest.py` (changed at collection/session startup)

**Affected tests to run**
- `tests/install_upgrade_operators/csv/test_csv.py` `(smoke)`
- `tests/install_upgrade_operators/deployment/test_hco_deployment_params.py` `(gating)`
- `tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade.py` `(gating)`
- `tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`

**Real tests (cluster required)**

Error/fix path (collection/session startup validation for the changed shared conftest imports):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/ tests/observability/ --collect-only`

Happy path (regression on representative smoke + gating coverage):
`uv run pytest -rA -s -o log_cli=true --tc-file=tests/global_config_amd64.py --tc-format=python --cluster-sanity-skip-check --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --skip-deprecated-api-test tests/install_upgrade_operators/csv/test_csv.py tests/install_upgrade_operators/deployment/test_hco_deployment_params.py tests/install_upgrade_operators/hco_enablement_golden_image_updates/test_custom_golden_images_namespace.py tests/install_upgrade_operators/product_upgrade/test_upgrade.py tests/install_upgrade_operators/product_upgrade/test_upgrade_iuo.py`

@rnetser

rnetser commented Jun 28, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

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