Add STD for vnic_info metric NAD swap test#4601
Add STD for vnic_info metric NAD swap test#4601OhadRevah wants to merge 2 commits intoRedHatQE:mainfrom
Conversation
Add test stub with STD for verifying that kubevirt_vm_vnic_info and kubevirt_vmi_vnic_info Prometheus metrics update their network label after swapping a VM's secondary NAD reference. Parametrized for both metric variants. assisted by: claude code claude-opus-4-6 Signed-off-by: Ohad <orevah@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA new parametrized test method is introduced to validate that vnic_info metrics accurately reflect VM specifications after swapping secondary network references between network attachment definitions. The test is disabled from pytest discovery. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. 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
AI Features
💡 Tips
For more information, please refer to the project documentation or contact the maintainers. |
|
Clean rebase detected — no code changes compared to previous head ( |
|
D/S test |
|
D/S test |
|
|
||
| Steps: | ||
| 1. Swap the VM secondary network reference from NAD-A to NAD-B | ||
| 2. Wait for the live migration triggered by the swap to complete |
There was a problem hiding this comment.
In network tests we probably won't wait for this condition since the migration is not exposed to the user
Do you usually wait for seamless migration to complete in metrics tests?
Short description:
Add test stub with STD for verifying that
kubevirt_vm_vnic_info and kubevirt_vmi_vnic_info Prometheus metrics update their network label after swapping a VM's secondary NAD reference. Parametrized for both metric variants.
assisted by: claude code claude-opus-4-6
More details:
As part of NAD reference live-update STP
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:
https://redhat.atlassian.net/browse/CNV-85546
Summary by CodeRabbit