Bug 1791379

Summary:	Show controller logs has occasional 404 error.
Product:	OpenShift Container Platform	Reporter:	Jeff Ortel <jortel>
Component:	Migration Tooling	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	ernelson, jmatthew, sregidor
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-02-06 20:21:05 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:

Description Jeff Ortel 2020-01-15 16:56:12 UTC

Description of problem:

The plan report provided by the /namespaces/<name>/plans/<plan>/pods endpoint occasionally contains an incorrect pod Name after the controller pod itself has been restarted. But instead, displays the previous pod name. As a result, the log URI is also incorrect. When this happens the UI gets a 404 when trying to display the controller logs.


Version-Release number of selected component (if applicable):

4.2


How reproducible:

Random.  Timing based.


Steps to Reproduce:
1. Select a pla (detail) n in the UI.
2. Choose "Logs" in the kebob.
3. Choose "controller"

Actual results:

Reports a 404.


Expected results:

Shows the logs.


Additional info:

Comment 4 Sergio 2020-01-22 11:19:12 UTC

Verified in CAM 1.1 stage

Controller:
    image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-controller-rhel8@sha256:ec015e65da93e800a25e522473793c277cd0d86436ab4637d73e2673a5f0083d
UI:
    image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-ui-rhel8@sha256:ecd81e11af0a17bfdd4e6afce1bf60f422115ed3545ad2b0d055f0fded87e422

After deleting controller pod several times and accessing the controller logs before and after deletion, no 404 error was shown (unless controller pod does not exist at  all, which is expected).

Comment 6 errata-xmlrpc 2020-02-06 20:21:05 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/RHEA-2020:0440