- 
                Notifications
    
You must be signed in to change notification settings  - Fork 50
 
Cherry-pick: Fix kubevirt_virt_operator_ready test flakiness (PR #2155) #2167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
          
 Important Review skippedBot user detected. To trigger a single review, invoke the  You can disable this status message by setting the  Comment   | 
    
| 
           Report bugs in Issues Welcome! 🎉This pull request will be automatically processed with the following features: 🔄 Automatic Actions
 📋 Available CommandsPR Status Management
 Review & Approval
 Testing & Validation
 Container Operations
 Cherry-pick Operations
 Label Management
 ✅ Merge RequirementsThis PR will be automatically approved when the following conditions are met: 
 📊 Review ProcessApprovers and ReviewersApprovers: 
 Reviewers: 
 Available Labels
 💡 Tips
 For more information, please refer to the project documentation or contact the maintainers.  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
D/S test tox -e verify-bugs-are-open failed: cnv-tests-tox-executor/17209
🍒 Automated Cherry-pick from PR
This PR contains the cherry-pick of PR #2155 from
OhadRevah/openshift-virtualization-tests.Original PR: Fix kubevirt_virt_operator_ready test flakiness
Author: @OhadRevah
Merge Commit: c7f9253
The cherry-pick was applied cleanly to
cnv-4.99without conflicts.Original PR Link: #2155
Original Commit: c7f9253
Original PR Description
Short description:
The test failing at the setup once in a while,
this happen because None passed as expected value
when not needed, added validation that virt_operator has replicas before proceeding.
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:
https://issues.redhat.com/browse/CNV-69870
Summary by CodeRabbit