Bug 2096166

Summary:	Template "vm-template-example" is binding with namespace "default"
Product:	Container Native Virtualization (CNV)	Reporter:	Guohua Ouyang <gouyang>
Component:	User Experience	Assignee:	Ugo Palatucci <upalatuc>
Status:	CLOSED ERRATA	QA Contact:	Guohua Ouyang <gouyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.11.0	CC:	cnv-qe-bugs, gouyang, upalatuc
Target Milestone:	---
Target Release:	4.11.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:	2022-09-14 19:35:53 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:

Description Guohua Ouyang 2022-06-13 07:31:30 UTC

Description of problem:
While creating template from the yaml, the namespace is always "default". It should use current namespace if a project is selected.

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


How reproducible:


Steps to Reproduce:
1. Select a project
2. Create template from yaml
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ugo Palatucci 2022-06-13 08:54:35 UTC

fixing also for VM 'create with yaml'

Comment 2 Guohua Ouyang 2022-06-16 03:21:43 UTC

verified on v4.11.0-55

Comment 5 errata-xmlrpc 2022-09-14 19:35: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 Virtualization 4.11.0 Images security and bug fix 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:6526