Bug 1840135

Summary: Multi Stream logs component logged out 400 for first step of task logs
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, cvogt, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:41:38 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
Multi Stream logs component does not logged out 400 for first step of task logs none

Description Sahil Budhwar 2020-05-26 12:54:57 UTC 
Sometimes, On the first step of each task, it logs out an 400 error

WebSocket connection to 'ws://localhost:9000/api/kubernetes/api/v1/namespaces/t0s/pods/nodejs-ex-git-a01t7k-build-7d64p-pod-6t9j2/log?container=step-create-dir-image-p8tlw&follow=true' failed: Error during WebSocket handshake: Unexpected response code: 400
but once the logs are completed and user comes back to this same task .. All the logs are printed properly

Pods log do not have this issue If user goes to the Pod fast enough, User can see it log out without an issue and then close the WebSocket.
Comment 5 spathak@redhat.com 2020-06-01 20:34:52 UTC 
Created attachment 1694176 [details]
Multi Stream logs component does not logged out 400 for first step of task logs
Comment 6 spathak@redhat.com 2020-06-01 20:36:37 UTC 
Verified on build version: 4.5.0-0.nightly-2020-05-31-230932
Browser version: Firefox 73
Comment 7 errata-xmlrpc 2020-07-13 17:41:38 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