Bug 1801752
| Summary: | Knative services sidebar doesn't show associated pod list | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | ||||||
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.4 | CC: | aos-bugs, cvogt, nmukherj, spathak | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.5.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: There isn't any way to navigate to the pods resource from selecting the knative service in topology.
Consequence: User have to go through multiple clicks to find associated pods for service
Fix: Show sidebar for selected service with list of pods along with link to view logs
Result: Knative service sidebar has list of pods along with link to view logs
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1806090 (view as bug list) | Environment: | |||||||
| Last Closed: | 2020-05-04 11:35:29 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: | 1806090 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jaivardhan Kumar
2020-02-11 15:13:08 UTC
Created attachment 1665344 [details]
Knative services sidebar does show associated pod list [?] N
Verified on build : 4.4.0-0.ci-2020-02-23-124819 Chrome browser: 76.0.3809.132 Created attachment 1665616 [details]
Knative services sidebar show associated pod list
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:0581 |