Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2005321

Summary: Web Terminal is not opened on Stage of DevSandbox when terminal instance is not created yet
Product: OpenShift Container Platform Reporter: sleshche
Component: Dev ConsoleAssignee: Abhinandan Das <abhindas>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: abhindas, cjerolim, nmukherj, sbudhwar
Target Milestone: ---   
Target Release: 4.11.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: 2022-07-25 14:11:37 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
closed websocket none

Description sleshche 2021-09-17 12:41:56 UTC 
Created attachment 1823902 [details]
closed websocket

Description of problem:
on DevSanbox (OS 4.8.11) Web Terminal loader is shown forever when there is no terminal instance created yet.


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

Prereq:
Account on DevSandbox Stage.

Instance is https://console-openshift-console.apps.sandbox-stage.gb17.p1.openshiftapps.com/ 

How to get account there https://docs.google.com/document/d/1xpV-N5Ij2h-YmBpN0mdUf1na6JxVdpJCd3lNX-Y3NMA/edit#heading=h.issbi33157r5 

How reproducible:
stable with cluster's console

Steps to Reproduce:
1. Click terminal button.

Actual results:
Web terminal button is shown forever


Expected results:
User is proposed to choose project where instance will be created.


Additional info:
Browser's console does not have any clue what's wrong, the only unusual stuff - websocket connection to watch devworkspaces is closed just after opening.

The weird thing that if you run local console (master or 4.8.11) instance will be created, and next try with cluster's console will work.
Comment 1 sleshche 2021-09-20 08:56:35 UTC 
Really, it can't be reproduced stable. As it figured out: it can be reproduced stable only on one cluster with one (my) user.
The plan is to add verbose logs for console backend and check for failure causes there.
Comment 2 Christoph Jerolimov 2022-04-26 14:11:07 UTC 
@sbudhwar can you take a look if this is reproducable?
Comment 4 Abhinandan Das 2022-06-08 13:43:24 UTC 
Unable to reproduce the issue
Comment 7 Christoph Jerolimov 2022-07-25 14:12:27 UTC 
Mark this as works for me as we can not reproduce it. https://bugzilla.redhat.com/show_bug.cgi?id=2005321#c4

Please reopen the issue if it still exists.