Bug 2101501
| Summary: | NAME parameter in VM template has no effect. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Leon Kladnitsky <lkladnit> | ||||
| Component: | User Experience | Assignee: | Hilda Stastna <hstastna> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Leon Kladnitsky <lkladnit> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.11.0 | CC: | gouyang, hstastna | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.12.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: | 2023-01-24 13:37:24 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
Leon Kladnitsky
2022-06-27 15:54:15 UTC
Created attachment 1893553 [details]
remove value from template name parameter
The fix of this bug is removing option "value" from template name parameter
(In reply to Hilda Stastna from comment #2) > Hi Guohua, > > are you sure that the fix is to remove option "Value" from template name > parameter? > I think this option makes sense to be there to set the specific name for the > VM > that will be created from that template, and removing that option solves > nothing, > as I've found that none of the options work as expected. Did you try to > choose > also the "Generated" or "None" option? Did you try to put there some > expression? > Did it work for you as expected? Thank you! It does not make sense to set the VM name in the template, the result is user can create only one VM from this template. I think the best solution is disabling or removing the value option here, options "Generated" and "None" are fine as the catalog generate vm name. But if you can come up with a better solution, I have no problem at all. Comment #1 is my suggestion. Options "Generated" and "None" do the same thing (or better said, choosing any of those options has no any effect on the VM name), so I think this feature won't work correctly even without the "Value" option. And so this "Value" option to set the specific VM name in the template still makes sense to me to be there. There must be a reason why it is there, in the new UI. I think it was a part of the new UI design, so probably we don't want to remove it (but I'll check that to make sure). And if the user set the same VM name as the name of some other already existing VM, they could be warned and forced to set some different name. I don't see any problem here. But I will reconsider this all. Thank you for your notes and suggestions, Guohua. The bug is fixed, you need to manually move this bug to ON_QA, so it can be verified. Verified on v4.12.0-147 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 |