Created attachment 1748241 [details] screenshot Description of problem: Any provided common template: as the disk contains a parameter, this is also shown in the UI with an error: ${NAME} Disk name must start/end with alphanumberic character Version-Release number of selected component (if applicable): OCP 4.7.0-fc.2, CNV 2.6 How reproducible: 100% Steps to Reproduce: 1. Virtualization -> Templates 2. Select a provided template (e.g RHEL 8) 3. Browse to the "Disks" tab Actual results: As the boot disk contains a parameter in the template, it is also show in the UI with an error: ${NAME} Disk name must start/end with alphanumberic character Expected results: Mark it as placeholder (?) or any indication to the user that this is a parametrized value In any case, an error should not be displayed Additional info: See attached screenshot
*** Bug 1917208 has been marked as a duplicate of this bug. ***
Same applies to template Details screen -> Boot Order -> "Show default boot disks" Boot Order No resource selected VM will attempt to boot from disks by order of apearance in YAML file ${NAME} (Disk) cloudinitdisk (Disk) default (NIC)
Created attachment 1749601 [details] template disk tab It shows like below now: "${NAME} template parameter"
On boot disk order, it is: ${NAME} (Disk), template parameter cloudinitdisk (Disk) default (NIC)
> Expected results: > Mark it as placeholder (?) or any indication to the user that this is a parametrized value > In any case, an error should not be displayed it is now say "template parameter" to fix - "indication to the user that this is a parametrized value" and it is not an error to fix - "an error should not be displayed" @Guohua hi, looks fixed to me, what am i missing here ?
Looks I have misunderstand here, then it's fixed.
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.7.0 security, bug fix, and enhancement 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-2020:5633