Bug 1835092
| Summary: | Use "View pod logs" instead of "View pod overview" in VM status popup window | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> | ||||||||
| Component: | Console Kubevirt Plugin | Assignee: | Yaacov Zamir <yzamir> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Nelly Credi <ncredi> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 4.5 | CC: | aos-bugs, gouyang, rhrazdil, yzamir | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 4.5.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: |
Cause:
error popup link to pod overview
Consequence:
users need to change tab to events, to view pod events.
Fix:
link directly to pod events.
Result:
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2020-07-13 17:38:07 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: |
|
||||||||||
|
Description
Guohua Ouyang
2020-05-13 05:42:49 UTC
Note: After offline discussion with Guohua we agreed to implement "View pod events" instead of "View pod logs" Main reason was that logs may be empty on some error cases ( e.g. pod container never come up ) while the evnets will hold debug helpful information. Shouldn't we use "Pod" instead of "pod"? Created attachment 1690269 [details]
pod events link
Created attachment 1690467 [details]
pod events
Created attachment 1690468 [details]
vm events
Pod events and VM events looks the same pretty much, so "View Pod logs" should be better for it. @Guahua, hi, We discussed that and agreed to use events: https://bugzilla.redhat.com/show_bug.cgi?id=1835092#c1 Will implement logs than :-) verified on upstream 4.5 branch, commit 88b7689b0fb3dfc557d9e06dc509952b9233661e. 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:2409 |