Bug 1826060 - Pod log pages do not have a query parameter for selected container
Summary: Pod log pages do not have a query parameter for selected container
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1827197
TreeView+ depends on / blocked
 
Reported: 2020-04-20 19:19 UTC by bpeterse
Modified: 2020-07-13 17:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1827197 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:29:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5147 0 None closed Bug 1826060: Add query parameter for selected container to pod logs 2020-07-13 18:19:13 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:29:31 UTC

Description bpeterse 2020-04-20 19:19:56 UTC
Description of problem:

We should add a query parameter for a specific container on the pod logs page. This will preserve the selected container if the page is refreshed and lets users share links to a specific container log.

This is needed by ACM, which links to a specific container log.

Originally in JIRA: https://issues.redhat.com/browse/CONSOLE-2169

Comment 3 Yanping Zhang 2020-04-23 09:12:16 UTC
Checked on 4.5 cluster with payload 4.5.0-0.ci-2020-04-22-212726. Create pod with two containers, go to pod log tab, the url contains the first container: pods/dctest-1-x4jqr/logs?container=dctest-1, change to the second container log, the url becomes to /pods/dctest-1-x4jqr/logs?container=dctest-2, copy it to another tab, will show the second container log.

Comment 4 errata-xmlrpc 2020-07-13 17:29:11 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, 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


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