Bug 1743514
| Summary: | "Pod Error" shows by restarting the VM several times | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> | ||||
| Component: | Console Kubevirt Plugin | Assignee: | Ido Rosenzwig <irosenzw> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Nelly Credi <ncredi> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.3.0 | CC: | aos-bugs, gouyang, irosenzw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.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: | 2020-01-23 11:05: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: | |||||||
| Attachments: |
|
||||||
setting severity to medium as from what i understand you would only see the error for a brief moment in the case there is another vm in pod error I'm not sure the reproduction steps are accurate - I don't think the "Pod Error" on the problematic VM affecting the valid VM you are restarting. I've been able to reproduce the issue with just restarting the VM several times in a row. The bug you describe (maybe) occurs when the UI points to the VM's old pod, since it no longer exist we see the error "Pod Error". Once the UI gets the newer pod (the one that do exist) the Error disappears. It's good you can reproduce the problem with simple steps. I didn't see the issue by restart the VM(just one vm on VM list) when I reported the bug. I can see 'Pod Error' by just restarting the VM two times and it just has one VM. on OCP 4.2.0-0.nightly-2019-09-09-073137 Now "Pod Error" does not show as the final status, but it's still showing during restart, it shows for 1-2 seconds before "starting" appears. version: 4.2.0-0.nightly-2019-10-06-011148 moved to 4.3 as the patch was merged to master branch after OpenShift 4.3 Master opened verified on 4.3.0-0.nightly-2019-11-02-092336. 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, 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:0062 |
Created attachment 1606006 [details] Click "view pod overview" leads to 404. Description of problem: "Pod Error" shows during VM restart when there is another VM in "Pod Error", however, the vm status becomes "running" finally. If there isn't another VM in "pod error", can't see this status while restarting the VM. By clicking the "pod error" and clicking "view pod overview" then it leads to a "404 not found" pod. Version-Release number of selected component (if applicable): hco-bundle-registry:v2.1.0-13 OpenShift Version 4.2.0-0.nightly-2019-08-15-073735 How reproducible: 100% Steps to Reproduce: 1. With a VM in "pod error". 2. Create a simple VM which can be running 3. Restart the new VM Actual results: "Pod Error" shows during VM restart when there is another VM in "Pod Error" Expected results: No "Pod Error" shows during VM restart. Additional info: