Bug 1839080

Summary: Pipeline Multistream log shows error message while retrireving logs.
Product: OpenShift Container Platform Reporter: Karthik Jeeyar <kjeeyar>
Component: Dev ConsoleAssignee: Karthik Jeeyar <kjeeyar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:41: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 Flags
pipeilne run error
none
Pipeline Multistream log does not show error message while retrireving logs. none

Description Karthik Jeeyar 2020-05-22 12:51:06 UTC
Created attachment 1691054 [details]
pipeilne run error

Description of problem:

The MultiStreamLog component does not check if it got a string before attempting to use a string method on it... thus causing an error to appear in logs.


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

How reproducible:
Always

steps to Reproduce:
1. Visit any existing pipelinerun logs page.



Actual results:
At the beginining of the log it shows a message `An error occurred while retreiving the logs`

Expected results:

It should not show the error msg while retrieving the logs.

Comment 3 spathak@redhat.com 2020-06-01 19:23:38 UTC
Created attachment 1694170 [details]
Pipeline Multistream log does not show error message while retrireving logs.

Comment 4 spathak@redhat.com 2020-06-01 19:37:05 UTC
Verified on build version: 4.5.0-0.ci-2020-05-29-203954
Browser version: Firefox 73

Comment 5 errata-xmlrpc 2020-07-13 17:41:07 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