Bug 1803666

Summary: VMI error is showing on VMs list when removing a running VM
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Nelly Credi <ncredi>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: aos-bugs, fkrepins, gouyang
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: VMI error was showing on VMs list when removing a running VM Fix: stale deleted VMIs with an VM owner are not shown in the VM list anymore
Story Points: ---
Clone Of:
: 1807031 (view as bug list) Environment:
Last Closed: 2020-08-04 18:00:35 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:
Bug Depends On:    
Bug Blocks: 1807031    
Attachments:
Description Flags
vmi is showing when delete running vm none

Description Guohua Ouyang 2020-02-17 08:10:34 UTC
Created attachment 1663467 [details]
vmi is showing when delete running vm

Description of problem:
When delete a running VM from VMs list, the associated VMI with status (VM error) is showing in the list.

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-10-111955

How reproducible:
100%

Steps to Reproduce:
1. Create a VM and start it.
2. Delete the VM.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Guohua Ouyang 2020-03-31 06:46:13 UTC
verified on 4.5.0-0.nightly-2020-03-29-224016.

Comment 6 errata-xmlrpc 2020-08-04 18:00:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409