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

Bug 1913565

Summary: "Error" shows in template boot source when logged with normal user
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED DUPLICATE QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, rawagner, yzamir
Target Milestone: ---   
Target Release: 4.7.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: 2021-01-07 13:49:14 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
Error in boot source none

Description Guohua Ouyang 2021-01-07 06:20:29 UTC
Created attachment 1745186 [details]
Error in boot source

Description of problem:
"Error" shows in template boot source when logged with normal user

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaacov Zamir 2021-01-07 13:21:47 UTC
Note:
This error happen because normal user can't read DVs on the "golden image namespace", I've opened a bug on the backend for that:
https://bugzilla.redhat.com/show_bug.cgi?id=1913717

Comment 2 Rastislav Wagner 2021-01-07 13:49:14 UTC
Marking this as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1913560 since underlying issue is the same - user does not have permissions to read DVs from base image ns. The correct permissions should be set by SSP operator but in the meantime we can make DVs optional - we wont have progress reporting in case image is being uploaded/downloaded/cloned but thats still better than not allowing user to continue.

*** This bug has been marked as a duplicate of bug 1913560 ***