Bug 2052752 - Intermittently vmim associated with kubevirt workload update is reporting to be in failed state even though vmi is running on updated launcher pod
Summary: Intermittently vmim associated with kubevirt workload update is reporting to ...
Keywords:
Status: CLOSED DUPLICATE of bug 2026357
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.10.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.12.0
Assignee: Antonio Cardace
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-09 22:45 UTC by Debarati Basu-Nag
Modified: 2023-09-18 04:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 11:16:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-16325 0 None None None 2022-10-27 18:00:03 UTC

Comment 3 Fabian Deutsch 2022-02-10 09:57:39 UTC 
@acardace could this be a dupe of bug #2026357?
Comment 4 Antonio Cardace 2022-02-10 10:19:55 UTC 
@fdeutsch definitely looks like it but cannot say with 100% certainty, have to spend some time on it.
Comment 5 sgott 2022-02-16 13:12:02 UTC 
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.
Comment 6 sgott 2022-02-23 13:26:59 UTC 
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.
Comment 7 Fabian Deutsch 2022-02-23 14:30:53 UTC 
Adjusting severity to high, as this can be confusing to many users, and cause noise if everything is actually alright.
Comment 11 Kedar Bidarkar 2022-03-24 14:07:13 UTC 
Deferring this bug to 4.12 due to capacity.
Comment 13 Antonio Cardace 2022-04-21 11:16:22 UTC 

*** This bug has been marked as a duplicate of bug 2026357 ***
Comment 14 Red Hat Bugzilla 2023-09-18 04:31:47 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.