Bug 2052752
| Summary: | Intermittently vmim associated with kubevirt workload update is reporting to be in failed state even though vmi is running on updated launcher pod | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Debarati Basu-Nag <dbasunag> |
| Component: | Virtualization | Assignee: | Antonio Cardace <acardace> |
| Status: | CLOSED DUPLICATE | QA Contact: | Kedar Bidarkar <kbidarka> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.10.0 | CC: | acardace, cnv-qe-bugs, dshchedr, fdeutsch, sgott |
| Target Milestone: | --- | ||
| Target Release: | 4.12.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-04-21 11:16:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 3
Fabian Deutsch
2022-02-10 09:57:39 UTC
@fdeutsch definitely looks like it but cannot say with 100% certainty, have to spend some time on it. Because no severity was specified, we're guessing that the impact is low--because the VM succeeds. We'll need further investigation to determine if this is a duplicate. Logs possibly indicate that two migrations were started and one was moved to failed state on purpose to avoid race conditions. If that is found to be the root cause, this is likely not a bug. Debarati would it be possible to provide the migration and VMI object definitions? The VMI status might confirm a hunch: that two migrations were created, and thus it's absolutely correct that one of them moved to a failed state. Adjusting severity to high, as this can be confusing to many users, and cause noise if everything is actually alright. Deferring this bug to 4.12 due to capacity. *** This bug has been marked as a duplicate of bug 2026357 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |