Skip to content

[4.21][Storage] Manual Cherry-Pick: Add Velero backup hooks opt-out tests - #5924

Merged
rnetser merged 2 commits into
RedHatQE:cnv-4.21from
ema-aka-young:velero-hooks-automation-cnv-4.21
Aug 11, 2026
Merged

[4.21][Storage] Manual Cherry-Pick: Add Velero backup hooks opt-out tests#5924
rnetser merged 2 commits into
RedHatQE:cnv-4.21from
ema-aka-young:velero-hooks-automation-cnv-4.21

Conversation

@ema-aka-young

@ema-aka-young ema-aka-young commented Aug 6, 2026

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

This is a manual cherry-pick of #5478.

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

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

Summary by CodeRabbit

  • New Features

    • Added support for opting virtual machines out of Velero backup hooks using an annotation.
    • Added coverage for running and paused virtual machines to ensure backup hooks are not injected when opted out.
  • Tests

    • Added automated validation for namespace-scoped backups and backup-hook behavior.
    • Added checks confirming expected backup-hook annotations are absent.

Signed-off-by: Emanuele Prella <eprella@redhat.com>

Implements automated test coverage for the Velero backup hook opt-out
feature (CNV-79727), which allows users to annotate VMs with
`kubevirt.io/skip-backup-hooks` to prevent Velero from injecting
freeze/unfreeze hooks on the virt-launcher pod during backup — intended
for metadata-only workflows where a third-party solution handles data
protection.

**Deliverables:**

- `test_backup_paused_vm_hooks_disabled` (CNV-16267) — verifies no
Velero hook annotations are present on the virt-launcher pod when
backing up a paused VM with the opt-out annotation set
- `test_backup_running_vm_hooks_disabled` (CNV-16268) — same
verification for a running VM

**New fixtures (tests/data_protection/oadp/conftest.py):**

- `namespace_for_hooks_backup` — dedicated namespace for hooks opt-out
tests
- `rhel_vm_with_hooks_opt_out` — RHEL VM with
`kubevirt.io/skip-backup-hooks: "true"` annotation, verified at fixture
setup time
- `paused_rhel_vm_with_hooks_opt_out` — derives from the above, pauses
the VM before yielding

**New utility (`tests/data_protection/oadp/utils.py`):**

- `assert_velero_backup_hooks_not_injected` — inspects the virt-launcher
pod and fails if any of the six known Velero hook annotation keys are
present

**New constants (`utilities/constants/oadp.py`):**

- `SKIP_BACKUP_HOOKS_ANNOTATION` — the VM-level opt-out annotation key
- `VELERO_BACKUP_HOOK_ANNOTATIONS` — the five virt-launcher annotation
keys Velero injects when hooks are enabled

**Scope note:** The STD originally included
`test_full_backup_restore_hooks_disabled`. Restore verification was
intentionally dropped from this PR because the hooks opt-out feature is
orthogonal to restore correctness — backup completing without hook
injection is the meaningful signal. A follow-up can cover restore if
deemed necessary.

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

Assysted by Quality Flow AI Tool

<!-- full-ticket-url needs to be provided. This would add a link to the
pull request to the jira and close it when the pull request is merged
If the task is not tracked by a Jira ticket, just write "NONE".
-->
https://redhat.atlassian.net/browse/CNV-88655

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

* Added coverage for virtual machines that opt out of Velero backup
hooks.
* Added scenarios for both running and paused virtual machines using
namespace-scoped backups.
* Added validation that Velero backup hook annotations are not injected
when opt-out is enabled.
* Improved test collection and logging for backup hook scenarios.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Emanuele Prella <eprella@redhat.com>
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (4)
  • main
  • cnv-4.20
  • cnv-4.19
  • cnv-4.18

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 19434fa3-49da-474a-9fda-7f0df937d957

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Changes

Velero backup-hook opt-out

Layer / File(s) Summary
Hook annotation contract and assertion
utilities/constants.py, tests/data_protection/oadp/utils.py
Adds Velero hook annotation constants and a helper that fails when hooks appear on a VM’s virt-launcher pod.
Opted-out VM fixtures
tests/data_protection/oadp/conftest.py
Creates a test namespace and running or paused RHEL VMs with kubevirt.io/skip-backup-hooks=true.
Paused and running VM backup tests
tests/data_protection/oadp/test_velero_backup_hooks.py
Creates Velero backups and verifies that hooks are not injected for paused and running VMs.

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

Possibly related PRs

Suggested labels: cherry-pick-cnv-4.21

Suggested reviewers: dshchedr, rnetser, acinko-rh, dalia-frank, geetikakay

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the branch context and the main change: adding Velero backup hook opt-out tests.
Description check ✅ Passed The description explains the manual cherry-pick and provides the Jira ticket, while the blank optional sections do not prevent understanding the change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 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-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 (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
  • jpeimer
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • Ahmad-Hafe
  • RoniKishner
  • acinko-rh
  • dalia-frank
  • dshchedr
  • ema-aka-young
  • geetikakay
  • josemacassan
  • jpeimer
  • kgoldbla
  • kshvaika
  • 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.

@ema-aka-young

Copy link
Copy Markdown
Contributor Author

/retest all

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

Verification failed for PR #5924.
The pipeline did not reach the test execution stage.

Execution details
pytest -s -o log_cli=true -m tier2 --jira tests/data_protection/oadp/test_velero_backup_hooks.py

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

Verification failed for PR #5924.
The pipeline did not reach the test execution stage.

Execution details
pytest -s -o log_cli=true -m tier2 --jira tests/data_protection/oadp/test_velero_backup_hooks.py

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

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

@rnetser

rnetser commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

@coderabbitai review

@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-5924 published

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/verified

All tests passed for PR #5924.
Job: openshift-virtualization-tests-runner #6114

Execution details
pytest -s -o log_cli=true -m tier2 --jira tests/data_protection/oadp/test_velero_backup_hooks.py
Image: openshift-virtualization-tests:pr-5924

@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"

Comment thread tests/data_protection/oadp/conftest.py
@coderabbitai

coderabbitai Bot commented Aug 10, 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

echo '=== PR metadata and changed files ==='
gh pr view 5924 --json baseRefName,headRefName,headRefOid,files --jq '{base: .baseRefName, head: .headRefName, sha: .headRefOid, files: [.files[].path]}'

echo '=== Diff with zero context ==='
git diff --unified=0 HEAD^ HEAD -- \
  tests/data_protection/oadp/conftest.py \
  tests/data_protection/oadp/test_velero_backup_hooks.py \
  tests/data_protection/oadp/utils.py \
  utilities/constants.py

echo '=== AST outlines ==='
ast-grep outline tests/data_protection/oadp/conftest.py --items all
ast-grep outline tests/data_protection/oadp/test_velero_backup_hooks.py --items all
ast-grep outline tests/data_protection/oadp/utils.py --items all
ast-grep outline utilities/constants.py --items all

echo '=== Modified utility function declarations ==='
git diff HEAD^ HEAD --unified=0 -- tests/data_protection/oadp/utils.py utilities/constants.py \
  | grep -E '^[+-][[:space:]]*(async[[:space:]]+)?def[[:space:]]+' || true

echo '=== Direct references to changed helper and constants in tests ==='
rg -n -C 4 '\bassert_velero_backup_hooks_not_injected\b|\bSKIP_BACKUP_HOOKS_ANNOTATION\b|\bVELERO_BACKUP_HOOK_ANNOTATIONS\b' tests utilities

echo '=== Fixture and test references in OADP test subtree ==='
rg -n -C 5 '\b(namespace_for_hooks_backup|rhel_vm_with_hooks_opt_out|paused_rhel_vm_with_hooks_opt_out)\b' tests

echo '=== Smoke-marked test files ==='
rg -l '`@pytest`\.mark\.smoke' tests || true

echo '=== Gating-marked test files ==='
rg -l '`@pytest`\.mark\.gating' tests || true

echo '=== All OADP conftest files ==='
fd -a '^conftest\.py$' tests/data_protection tests 2>/dev/null | sort

Length of output: 49336


🏁 Script executed:

#!/bin/bash
set -euo pipefail

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

echo '=== Full PR file patches ==='
gh api "repos/${repo}/pulls/${pr}/files?per_page=100" \
  --jq '.[] | "FILE: \(.filename)\nSTATUS: \(.status)\nPATCH:\n\(.patch // "<no patch>")\n---"'

echo '=== Relevant source ranges ==='
sed -n '1,340p' tests/data_protection/oadp/conftest.py
sed -n '1,140p' tests/data_protection/oadp/test_velero_backup_hooks.py
sed -n '1,135p' tests/data_protection/oadp/utils.py
sed -n '985,1010p' utilities/constants.py

echo '=== All repository references to changed symbols ==='
rg -n -C 3 '\bassert_velero_backup_hooks_not_injected\s*\(|\bSKIP_BACKUP_HOOKS_ANNOTATION\b|\bVELERO_BACKUP_HOOK_ANNOTATIONS\b' .

echo '=== Same-file calls to the changed helper ==='
rg -n -C 3 '\bassert_velero_backup_hooks_not_injected\s*\(' tests/data_protection/oadp/utils.py

echo '=== Fixture wrappers and cleanup paths ==='
rg -n -U -C 4 '`@pytest`\.fixture|yield from|yield |with VirtualMachineForTests|def (namespace_for_hooks_backup|rhel_vm_with_hooks_opt_out|paused_rhel_vm_with_hooks_opt_out)\b' \
  tests/data_protection/oadp/conftest.py

echo '=== Marker-specific direct references ==='
for marker in smoke gating; do
  echo "--- ${marker} test files that reference changed symbols ---"
  while IFS= read -r file; do
    if rg -q '\bassert_velero_backup_hooks_not_injected\b|\bSKIP_BACKUP_HOOKS_ANNOTATION\b|\bVELERO_BACKUP_HOOK_ANNOTATIONS\b' "$file"; then
      echo "$file"
    fi
  done < <(rg -l "`@pytest`\.mark\.${marker}" tests)
done

echo '=== Smoke and gating conftest hierarchy references ==='
python3 - <<'PY'
from pathlib import Path
import re

symbols = re.compile(r"\b(assert_velero_backup_hooks_not_injected|SKIP_BACKUP_HOOKS_ANNOTATION|VELERO_BACKUP_HOOK_ANNOTATIONS)\b")
for marker in ("smoke", "gating"):
    print(f"--- {marker} ---")
    marked = []
    for test in Path("tests").rglob("test_*.py"):
        if re.search(rf"`@pytest`\.mark\.{marker}\b", test.read_text(errors="replace")):
            marked.append(test)
    print(f"marked_files={len(marked)}")
    matches = set()
    for test in marked:
        current = test.parent
        while True:
            conf = current / "conftest.py"
            if conf.exists() and symbols.search(conf.read_text(errors="replace")):
                matches.add(str(conf))
            if current == Path("tests"):
                break
            current = current.parent
    print("hierarchy_matches=" + (", ".join(sorted(matches)) if matches else "<none>"))
PY

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

Length of output: 44433


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr=5924
symbols='\b(assert_velero_backup_hooks_not_injected|SKIP_BACKUP_HOOKS_ANNOTATION|VELERO_BACKUP_HOOK_ANNOTATIONS)\b'

for marker in smoke gating; do
  echo "=== ${marker}: marked test files with direct changed-symbol references ==="
  rg -l "`@pytest`\.mark\.${marker}" tests > "/tmp/${marker}-files.txt" || true
  cat "/tmp/${marker}-files.txt"
  found=0
  while IFS= read -r file; do
    [ -n "$file" ] || continue
    if rg -q "$symbols" "$file"; then
      echo "DIRECT: $file"
      found=1
    fi
  done < "/tmp/${marker}-files.txt"
  [ "$found" -eq 1 ] || echo '<none>'

  echo "=== ${marker}: parent conftest files with changed-symbol references ==="
  python3 - "$marker" "/tmp/${marker}-files.txt" <<'PY'
from pathlib import Path
import re
import sys

marker, listing = sys.argv[1:]
symbols = re.compile(r"\b(assert_velero_backup_hooks_not_injected|SKIP_BACKUP_HOOKS_ANNOTATION|VELERO_BACKUP_HOOK_ANNOTATIONS)\b")
matches = set()
for raw in Path(listing).read_text().splitlines():
    test = Path(raw)
    directory = test.parent
    while True:
        conftest = directory / "conftest.py"
        if conftest.is_file() and symbols.search(conftest.read_text(errors="replace")):
            matches.add(str(conftest))
        if directory == Path("tests"):
            break
        directory = directory.parent
print("\n".join(sorted(matches)) if matches else "<none>")
PY
done

echo '=== Inline target validation ==='
gh pr view "$pr" --repo "$repo" --json headRefOid --jq .headRefOid
gh api "repos/${repo}/pulls/${pr}/files?per_page=100" \
  --jq '.[0] | {filename, patch: (.patch | split("\n")[:8] | join("\n"))}'

Length of output: 5946


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="RedHatQE/openshift-virtualization-tests"
pr=5924
commit_id="7ee46b2e0ac8855b2e5a1c5305c350715db59cd8"
body=$(cat <<'EOF'
## Test Execution Plan

**Run smoke tests: False.** No smoke-marked test directly uses `assert_velero_backup_hooks_not_injected`, `SKIP_BACKUP_HOOKS_ANNOTATION`, or `VELERO_BACKUP_HOOK_ANNOTATIONS`. No parent `conftest.py` in a smoke test hierarchy references these symbols.

**Run gating tests: False.** No gating-marked test directly uses these symbols. No parent `conftest.py` in a gating test hierarchy references these symbols.

**Affected tests to run**
- `tests/data_protection/oadp/test_velero_backup_hooks.py::TestVeleroBackupHookOptOut::test_backup_paused_vm_hooks_disabled` (polarion: `CNV-16267`)
- `tests/data_protection/oadp/test_velero_backup_hooks.py::TestVeleroBackupHookOptOut::test_backup_running_vm_hooks_disabled` (polarion: `CNV-16268`)

The tests exercise the full dependency path: test → `paused_rhel_vm_with_hooks_opt_out` or `rhel_vm_with_hooks_opt_out` → `namespace_for_hooks_backup` → `VirtualMachineForTests` with `SKIP_BACKUP_HOOKS_ANNOTATION` → `assert_velero_backup_hooks_not_injected` → `VirtualMachineInstance.virt_launcher_pod`.

**Real tests (cluster required)**

Error path: paused VM with backup-hook opt-out.
```bash
pytest -s -o log_cli=true -m tier2 --jira tests/data_protection/oadp/test_velero_backup_hooks.py::TestVeleroBackupHookOptOut::test_backup_paused_vm_hooks_disabled

Expected: the Velero backup completes and the virt-launcher pod has none of the configured Velero pre/post hook annotations.

Happy path: running VM with backup-hook opt-out.

pytest -s -o log_cli=true -m tier2 --jira tests/data_protection/oadp/test_velero_backup_hooks.py::TestVeleroBackupHookOptOut::test_backup_running_vm_hooks_disabled

Expected: the Velero backup completes and the virt-launcher pod has none of the configured Velero pre/post hook annotations.
EOF
)

gh api
--method POST
"repos/${repo}/pulls/${pr}/comments"
-f body="$body"
-f commit_id="$commit_id"
-f path="tests/data_protection/oadp/conftest.py"
-F line=4
-f side="RIGHT"
--jq '{id, path, line, side}'


Length of output: 2435

---

</details>

`@openshift-virtualization-qe-bot-3`: The inline test execution plan was posted on the first changed line of `tests/data_protection/oadp/conftest.py`.

You are interacting with an AI system.

@josemacassan

Copy link
Copy Markdown
Contributor

/lgtm

@Ahmad-Hafe

Copy link
Copy Markdown
Contributor

/lgtm

@jpeimer

jpeimer commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@rnetser

rnetser commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@rnetser
rnetser merged commit e9084ad into RedHatQE:cnv-4.21 Aug 11, 2026
26 checks passed
@openshift-virtualization-qe-bot-6

Copy link
Copy Markdown

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

@ema-aka-young

Copy link
Copy Markdown
Contributor Author

/cherry-pick cnv-4.20

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

Cherry-picked PR [4.21][Storage] Manual Cherry-Pick: Add Velero backup hooks opt-out tests into cnv-4.20: #5961

@openshift-virtualization-qe-bot-6

Copy link
Copy Markdown

New container for quay.io/openshift-cnv/openshift-virtualization-tests:cnv-4.21 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.