Bug 1827197
| Summary: | Pod log pages do not have a query parameter for selected container | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Robb Hamilton <rhamilto> |
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5 | CC: | aos-bugs, bpeterse, dtaylor, jokerman, sberens, yanpzhan, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Pod log pages did not include a query string parameter indicating the selected container.
Consequence: In the case where more than one container exists in a pod, refreshing the page or visiting the page's URL could result in the incorrect container logs displaying.
Fix: Add a query string parameter so the URL indicates which container's logs should display.
Result: The correct container logs display.
|
Story Points: | --- |
| Clone Of: | 1826060 | Environment: | |
| Last Closed: | 2020-06-17 22:26:03 UTC | Type: | --- |
| 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: | 1826060 | ||
| Bug Blocks: | |||
|
Comment 1
Robb Hamilton
2020-05-08 17:23:40 UTC
PR opened, awaiting cherry pick approval. Checked on ocp 4.4 cluster with payload: 4.4.0-0.nightly-2020-06-07-075345 Create pod with two containers in project, go to pod log page, the url has container selected, switch to the second container, copy the url and open it in another tab, will open pod log page with the second container selected. The bug is fixed. 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:2445 thank you team. is there a way that we can check to see if this will make it into a 4.4.z ? |