Bug 2074635

Summary: Unable to start Web Terminal after deleting existing instance
Product: OpenShift Container Platform Reporter: Angel Misevski <amisevsk>
Component: Dev ConsoleAssignee: Abhinandan Das <abhindas>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.10CC: abhindas, aos-bugs, cjerolim, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2094418 (view as bug list) Environment:
Last Closed: 2022-08-10 11:06:30 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:
Bug Depends On:    
Bug Blocks: 2094418, 2094863    
Attachments:
Description Flags
Browser console logs
none
Expected flow when deleting terminal CR
none
Actual state with bug -- panel stuck loading none

Description Angel Misevski 2022-04-12 17:26:31 UTC 
Description of problem:

With the Web terminal Operator installed, the Dev Console allows users to create terminal instances in their cluster by clicking a button in the masthead. For regular (non-cluster-admin) users, this opens a panel that prompts the user to pick a namespace, and then creates a DevWorkspace Custom Resource that is processed by the Web Terminal Operator to start a terminal instance.

However, in OpenShift 4.10, if the user deletes the CR that defines their Web Terminal, they are no longer able to start terminals, with the namespace prompt panel being stuck in a loading state.

This issue is not present in OpenShift 4.9 and below (tested: 4.8.3, 4.9.0),
nor is it present if the user has cluster-admin privileges.


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


How reproducible: Always


Steps to Reproduce:
1. Install the Web Terminal Operator from OperatorHub
2. Login to an OpenShift 4.10 cluster as a regular user
3. Click '>_' button in masthead next to help button (may need to refresh page if operator was just installed)
4. Wait for terminal to start, type `oc delete dw terminal<tab>` to autocomplete the CR's name and delete it.


Actual results: Panel enters loading state indefinitely, which persists between opening and closing it, refreshing page, clearing browser cache.


Expected results: Panel should revert to initial state, prompting user to pick a project to start their terminal in.


Additional info:

* Nothing suspicious logged on backend console pod
* Browser logs contain references to a webhook errors, however these same errors are present in OpenShift 4.8 and 4.9. (see attachment)
Comment 1 Angel Misevski 2022-04-12 17:30:31 UTC 
Created attachment 1872005 [details]
Browser console logs

Browser console logs for

1. Clicking masthead icon to create web terminal, selecting "wto-debugging" namespace in panel and creating a web terminal
2. Waiting for terminal to start, closing and reopening panel with running terminal
3. Deleting the terminal instance from within the terminal and encountering the bug
4. Closing and reopening the terminal panel while it's in a broken state.
Comment 2 Angel Misevski 2022-04-12 17:31:01 UTC 
Created attachment 1872006 [details]
Expected flow when deleting terminal CR
Comment 3 Angel Misevski 2022-04-12 17:31:29 UTC 
Created attachment 1872007 [details]
Actual state with bug -- panel stuck loading
Comment 7 errata-xmlrpc 2022-08-10 11:06:30 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