Bug 2132682 - Default YAML entity name convention.
Summary: Default YAML entity name convention.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.12.0
Assignee: Aviv Turgeman
QA Contact: Leon Kladnitsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-06 11:33 UTC by Leon Kladnitsky
Modified: 2023-01-24 13:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 13:41:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 915 0 None open Bug 2132682: Default YAML entity name convention. 2022-10-18 09:21:24 UTC
Red Hat Issue Tracker CNV-21696 0 None None None 2022-10-26 20:30:04 UTC
Red Hat Product Errata RHSA-2023:0408 0 None None None 2023-01-24 13:41:29 UTC

Description Leon Kladnitsky 2022-10-06 11:33:20 UTC 
Description of problem: Some entities, when created from YAML, have names with prefix, while others do not. 

Prefixed YAML names: "vm-example" for VM, "vm-template-example" for Template


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


How reproducible: always


Steps to Reproduce:
1. Create new VM or new Template from YAML
2.
3.

Actual results: When new VM is created from YAML, name is "vm-example"


Expected results: When new VM is created from YAML, name is "example"


Additional info: Same for new Template
Comment 1 Leon Kladnitsky 2022-10-26 20:16:56 UTC 
The bug is fixed, you need to manually move this bug to ON_QA, so it can be verified.
Comment 2 Leon Kladnitsky 2022-10-27 07:06:10 UTC 
Verified on v4.12.0-145
Comment 6 errata-xmlrpc 2023-01-24 13:41:21 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.12.0 Images 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-2023:0408
Note You need to log in before you can comment on or make changes to this bug.