UI issue on VM Instantiation when Memory or CPU modification is set to 'range' within a VM template

[jimfreeman]

/!\ To report a security issue please follow this procedure:
[https://github.com/OpenNebula/one/wiki/Vulnerability-Management-Process]

Description
UI issue when Memory or CPU modification is set to 'range' within a VM template

To Reproduce

• Download App from marketplace and edit the VM template
• Change Virtual CPU Modification to 'range' and create some options
• Go to build a VM from said template

Expected behavior
Being able to see clearly what the result is, rather than seeing the placeholder of the input box label. You can only see expected behaviour when the input field is active, otherwise it defaults to the input field placeholder text taking over.

In my attached example, I think also Virtual CPU should be whole numbers as well, without decimal places

Details

• Affected Component: Sunstone
• Hypervisor: KVM
• Version: 6.10.2

Additional context
See attached images of when the value input field is not highlighted and when its highlighted. Note, that when the slider is being moved (as per the range option), it deselects the input field.

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)