Bug 1951209 - RerunOnFailure runStrategy shows wrong VM status (Starting) on Succeeded VMI
Summary: RerunOnFailure runStrategy shows wrong VM status (Starting) on Succeeded VMI
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Filip Krepinsky
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-19 20:09 UTC by Filip Krepinsky
Modified: 2021-07-27 23:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Multiple UI features were not working properly for VMs with runStratege RerunOnFailure Fix: These UI features should work properly. Result:
Clone Of:
Last Closed: 2021-07-27 23:01:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 8708 0 None open Bug 1951209: kubevirt-plugin: take into account Succeeded VMI Phase 2021-04-19 20:15:37 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:02:07 UTC

Description Filip Krepinsky 2021-04-19 20:09:12 UTC
Description of problem:
- shows wrong VM status (Starting) on Succeeded VMI
- VM disks and nics are disabled once the VM has stopped
- VM also cannot be started again
- console shows that VM is starting up
- pending changes shouldnt be shown

How reproducible:

Steps to Reproduce:
1. create VM with RerunOnFailure runStrategy
2. run it and turn it off
3. VMI will be kept in Succeeded state causing this bug

Comment 2 Guohua Ouyang 2021-04-22 04:19:15 UTC
Didn't see this problem on latest branch

Comment 5 errata-xmlrpc 2021-07-27 23:01:52 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.