Bug 2038034 - non-privileged user cannot see auto-update boot source
Summary: non-privileged user cannot see auto-update boot source
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Aviv Turgeman
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-07 06:57 UTC by Guohua Ouyang
Modified: 2022-03-10 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10803 0 None open Bug 2038034: non-privileged user cannot see auto-update boot source 2022-01-11 01:04:03 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:45 UTC

Description Guohua Ouyang 2022-01-07 06:57:54 UTC
Description of problem:
After auto-update boot source feature is enabled, cluster-admin can see the template boot source is "Red Hat", but non-privileged user cannot see these boot source.

Version-Release number of selected component (if applicable):
OCP 4.10.0-0.nightly-2022-01-04-214702

How reproducible:

Steps to Reproduce:
1. enable auto-update feature
2. login with non-privileged user

Actual results:

Expected results:

Additional info:

Comment 3 Guohua Ouyang 2022-01-18 02:25:27 UTC
verified on 4.10.0-0.nightly-2022-01-17-182202, non-priv user can use auto-update boot source templates to create vm.

Comment 6 errata-xmlrpc 2022-03-10 16:37:33 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.10.3 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.