Bug 1945103 - 'User credentials' shows even the VM is not running
Summary: 'User credentials' shows even the VM is not running
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-03-31 11:07 UTC by Guohua Ouyang
Modified: 2021-07-27 22:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:56:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
'User credentials' shows even the VM is not running (189.10 KB, image/png)
2021-03-31 11:07 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 8791 0 None open Bug 1945103: Not showing user creds if vm isnt up 2021-04-27 10:14:29 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:57:03 UTC

Description Guohua Ouyang 2021-03-31 11:07:03 UTC
Created attachment 1768037 [details]
'User credentials' shows even the VM is not running

Description of problem:
'User credentials' shows even the VM is not running, it cannot ssh to VM at this state.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Ying Cui 2021-04-14 07:54:08 UTC
The expectation in 4.8 is disable the "User credentials" first, because the complete feature will enable in 4.9 phase.

Comment 3 Guohua Ouyang 2021-05-06 02:02:57 UTC
verified on master

Comment 6 errata-xmlrpc 2021-07-27 22:56:48 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 (Moderate: OpenShift Container Platform 4.8.2 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.


Note You need to log in before you can comment on or make changes to this bug.