Skip to content

CherryPicked: [cnv-4.22] [Storage] Increase libguestfs pod timeout#5426

Merged
rnetser merged 1 commit into
cnv-4.22from
CherryPicked-increase-libguestfs-timeout-39NzN
Jun 29, 2026
Merged

CherryPicked: [cnv-4.22] [Storage] Increase libguestfs pod timeout#5426
rnetser merged 1 commit into
cnv-4.22from
CherryPicked-increase-libguestfs-timeout-39NzN

Conversation

@cnv-tests-github-webhook-dollierp

Copy link
Copy Markdown

Cherry-pick from main branch, original PR: #5308, PR owner: ema-aka-young

##### What this PR does / why we need it:
Increase the timeout from TIMEOUT_1MIN (60s) to TIMEOUT_10MIN (600s) to
match the product's own 500-second timeout for the libguestfs pod to
reach Running state. The product code at
[pkg/virtctl/guestfs/guestfs.go](https://github.com/kubevirt/kubevirt/blob/759a3049c9d1fad35bdb06205207aec277f6b112/pkg/virtctl/guestfs/guestfs.go#L67)
defines timeout = 500 * time.Second for this same operation.

##### Which issue(s) this PR fixes:
Test failures on different lanes.

##### Special notes for reviewer:

##### jira-ticket:
<!-- 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".
-->
CNV-62312


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

* **Tests**
* Improved reliability of pod readiness checks by increasing the wait
timeout when using `libguestfs-tools-*` in the
`virtctl_libguestfs_by_user` fixture.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Emanuele Prella <eprella@redhat.com>
@openshift-virtualization-qe-bot-6

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

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:

  • jpeimer

Reviewers:

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

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

/build-and-push-container

@openshift-virtualization-qe-bot

Copy link
Copy Markdown

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

Execution details
pytest -s -o log_cli=true -m tier2 --jira -k test_virtctl_libguestfs_with_specific_user --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization
(1 parameters hidden from public report)

@ema-aka-young

Copy link
Copy Markdown
Contributor

/build-and-push-container

@openshift-virtualization-qe-bot-4

Copy link
Copy Markdown

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

@jpeimer

jpeimer commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

/approve
/lgtm

@ema-aka-young

Copy link
Copy Markdown
Contributor

/verified
openshift-virtualization-tests-runner/5833

-s -o log_cli=true -m tier2 --jira -k test_virtctl_libguestfs_with_specific_user --storage-class-matrix=ocs-storagecluster-ceph-rbd-virtualization --count=10

@dalia-frank

Copy link
Copy Markdown
Contributor

/lgtm

@rnetser
rnetser merged commit f6684f6 into cnv-4.22 Jun 29, 2026
23 checks passed
@rnetser
rnetser deleted the CherryPicked-increase-libguestfs-timeout-39NzN branch June 29, 2026 18:58
@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

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

@openshift-virtualization-qe-bot-5

Copy link
Copy Markdown

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

ema-aka-young added a commit to ema-aka-young/openshift-virtualization-tests that referenced this pull request Jul 3, 2026
Signed-off-by: Emanuele Prella <eprella@redhat.com>
rnetser pushed a commit that referenced this pull request Jul 9, 2026
)

##### What this PR does / why we need it:

- De-quarantine test_virtctl_libguestfs_with_specific_user.
- Replace HTTP import in favor of data source cloning.
- Wait for the libguestfs container to be created before performing
operations in it.

##### Which issue(s) this PR fixes:
CNV-47594

##### Special notes for reviewer:
manual backporting
#4556 and
#5426

##### jira-ticket:
<!-- 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".
-->

---------

Signed-off-by: Emanuele Prella <eprella@redhat.com>
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.

8 participants