Skip to content

Remove CNV-81829 runbook bug marker#5470

Open
OhadRevah wants to merge 1 commit into
RedHatQE:mainfrom
OhadRevah:removeCNV-81829
Open

Remove CNV-81829 runbook bug marker#5470
OhadRevah wants to merge 1 commit into
RedHatQE:mainfrom
OhadRevah:removeCNV-81829

Conversation

@OhadRevah

@OhadRevah OhadRevah commented Jul 2, 2026

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

The link for the runbook in kubemacpool prometheus rule fixed and now we can see the DS link, removing the Remove CNV-81829 runbook bug marker since the bug is fixed

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

Summary by CodeRabbit

  • Tests
    • Updated observability runbook URL test setup to rely on fewer special-case helpers.
    • Removed an outdated expected-failure condition from one check, so the test now reflects the current behavior.

The link for the runbook in kubemacpool prometheus rule fixed and now we can see the DS link, removing the Remove CNV-81829 runbook bug marker since the bug is fixed

Signed-off-by: Ohad <orevah@redhat.com>
@OhadRevah

Copy link
Copy Markdown
Contributor Author

/verified

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR removes an obsolete Jira-gated xfail condition from a Prometheus rule runbook URL test fixture and cleans up its now-unused imports (KUBEMACPOOL_PROMETHEUS_RULE, is_jira_open), leaving only the HPP-CR-related xfail check intact.

Changes

Runbook URL Test Cleanup

Layer / File(s) Summary
Remove stale Jira xfail and unused imports
tests/observability/runbook_url/conftest.py
Removes imports for the Prometheus rule constant and Jira-status helper, and deletes the corresponding xfail branch that depended on the resolved Jira ticket, retaining only the HPP-CR-related xfail condition.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

Suggested reviewers: rnetser, vsibirsk, hmeir, rlobillo


Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

  • Ignore

❌ Failed checks (1 error)

Check name Status Explanation Resolution
Description check ❌ Error The template is only partially filled; the issue list, reviewer notes, and especially the required jira-ticket field are left empty. Add the fixed issue(s), any reviewer notes, and a Jira full-ticket URL or 'NONE' in the jira-ticket section.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title is under 120 characters and clearly matches the change to remove the CNV-81829 runbook bug marker.
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 new test files or test functions were added; the only test-area change is a deletion in conftest.py, so STP links are not required.
✨ 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.

@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 Jul 2, 2026

Copy link
Copy Markdown
Contributor
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh pr diff 5470 --repo RedHatQE/openshift-virtualization-tests

Length of output: 1424


🏁 Script executed:

#!/bin/bash
cd /tmp 2>/dev/null
rg -n "cnv_alerts_runbook_urls_from_prometheus_rule" -g '!*.pyc' 
echo "---markers---"
rg -n "pytest.mark.(smoke|gating)" tests/observability/runbook_url/
echo "---file content---"
fd . tests/observability/runbook_url/
echo "---test file---"
find . -path '*/observability/runbook_url/*' -name 'test_*.py' -exec cat {} \;

Length of output: 660


🏁 Script executed:

#!/bin/bash
rg -n "cnv_alerts_runbook_urls_from_prometheus_rule"
echo "---markers---"
rg -n "pytest.mark.(smoke|gating)" tests/observability/runbook_url/
echo "---files---"
fd . tests/observability/runbook_url/
echo "---test file content---"
find tests/observability/runbook_url -name 'test_*.py' -exec cat {} \;
echo "---is_jira_open usage---"
rg -n "is_jira_open" utilities/jira.py

Length of output: 691


🏁 Script executed:

#!/bin/bash
pwd
ls
fd conftest.py tests/observability

Length of output: 637


🏁 Script executed:

#!/bin/bash
rg -n "cnv_alerts_runbook_urls_from_prometheus_rule" || true
echo "---markers---"
rg -n "pytest.mark.(smoke|gating)" tests/observability/runbook_url/ || true
echo "---files---"
fd . tests/observability/runbook_url/ || true
echo "---test file content---"
find tests/observability/runbook_url -name 'test_*.py' -exec cat {} \; 
echo "---is_jira_open usage---"
rg -n "def is_jira_open" utilities/jira.py -A 20 || true

Length of output: 565


🏁 Script executed:

#!/bin/bash
echo "hello"

Length of output: 169


🏁 Script executed:

#!/bin/bash
echo "step1"
rg -n "cnv_alerts_runbook_urls_from_prometheus_rule" .
echo "step2"

Length of output: 708


🏁 Script executed:

#!/bin/bash
cat -n tests/observability/runbook_url/test_runbook_url.py
echo "---markers dir---"
rg -n "pytest.mark" tests/observability/runbook_url/
echo "---parent conftest---"
sed -n '1,80p' tests/observability/conftest.py

Length of output: 5094


@openshift-virtualization-qe-bot-3 I don't have a capability to post a separate inline review comment pinned to a specific diff line outside of this reply thread — my available actions are limited to this comment and the standard action tags (e.g., ``). Here is the Test Execution Plan based on my analysis of the diff:

Test Execution Plan

  • Run smoke tests: False — No @pytest.mark.smoke-marked test exists in tests/observability/runbook_url/ or depends on the changed fixture.
  • Run gating tests: False — No @pytest.mark.gating-marked test exists in the affected path either.
  • Affected tests to run:
    • tests/observability/runbook_url/test_runbook_url.py::TestRunbookUrlsAndPrometheusRules::test_runbook_downstream_urls

Rationale / dependency path:
conftest.py's cnv_alerts_runbook_urls_from_prometheus_rule fixture previously called pytest.xfail(...) for the kubemacpool-prometheus-rule rule name due to Jira CNV-81829. That xfail block, along with the now-unused KUBEMACPOOL_PROMETHEUS_RULE and is_jira_open imports, has been removed. This fixture is consumed only by test_runbook_downstream_urls, so that test is the sole affected test — it will now actually validate the kubemacpool rule's runbook URL instead of being marked xfail.

Real tests (cluster required)
Since this only removes a dead xfail branch in a fixture (no session/collection-time or runtime behavior change beyond that one rule), the affected test itself is sufficient to run for verification:
pytest tests/observability/runbook_url/test_runbook_url.py::TestRunbookUrlsAndPrometheusRules::test_runbook_downstream_urls
Expected: passes cleanly for the kubemacpool prometheus rule now that its runbook URL is fixed (no xfail triggered).

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@openshift-virtualization-qe-bot-2

Copy link
Copy Markdown
Contributor

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

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 exectuion

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.

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.

4 participants