Bug 2094857 - CloudShellTerminal loops indefinitely if DevWorkspace CR goes into failed state
Summary: CloudShellTerminal loops indefinitely if DevWorkspace CR goes into failed state
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.11
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Abhinandan Das
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-08 13:02 UTC by Abhinandan Das
Modified: 2022-08-10 11:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:16:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11650 0 None open Bug 2091603: move terminal tick & add phase handlers 2022-06-08 13:03:50 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:17:06 UTC

Description Abhinandan Das 2022-06-08 13:02:50 UTC 
Description of problem:
CloudShellTerminal loops indefinitely if DevWorkspace CR goes into failed state

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

How reproducible:
Always

Steps to Reproduce:
1.Install WTO operator
2. Start WT by clicking on masthead button
3. Fail the DevWorkspace CR associated with the WebTerminal

Actual results:
WT shows loading screen indefinitely

Expected results:
Some error should be shown in WT

Additional info:
Comment 3 spathak@redhat.com 2022-07-12 06:26:23 UTC 
Verified on build version: 4.11.0-0.nightly-2022-06-30-005428
Browser version: Chrome 101
Comment 4 errata-xmlrpc 2022-08-10 11:16:53 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.