Description of problem:
when entering the vSphere network name, we can't enter any spaces. We can however, paste it in. Additionally, any change we make to the YAML editor for the vSphere network name is not reflected in the UI.
Keeping this as one defect instead of two since it affects the same field.
Version-Release number of selected component (if applicable):
This is also in the latest 2.5
Steps to Reproduce:
1. Click Create Cluster and select vSphere VMware. Go to Networks.
2. Try typing in "Test Network" observe that space is not entered
3. Make change to platform.vsphere.network. Observe that the UI is not updated with this change.
- Can't enter space in network name
- Any change in yaml editor isn't reflected in UI
G2Bsync 1098391937 comment
dtthuynh Wed, 13 Apr 2022 19:11:51 UTC
> @KevinFCormier will do. @dtthuynh @KevinFCormier So the implication is that spaces in the network names are okay for vSphere?
I'm not 100% on any hard requirement, but we've been using network name with spaces for a while for our internal vSphere instances. This was missed because we would always paste it in.
G2Bsync 1154176122 comment
dtthuynh Mon, 13 Jun 2022 17:13:11 UTC
G2Bsync Tested on 2.4.5-FC1, spaces are now allowed to be entered in the Network name field, but any changes to the YAML does not get reflected onto the UI.
G2Bsync 1178933339 comment
KevinFCormier Fri, 08 Jul 2022 12:29:16 UTC
G2Bsync An additional fix for the syncing of the network type has been delivered for 2.4.6.
Verified fix in 2.4.6
Can enter space in network name
Change in yaml editor is reflected in UI
(In reply to Napoco Agbetra from comment #6)
> Verified fix in quay.io:443/acm-d/acm-custom-registry:2.4.6-DOWNSTREAM-2022-07-07-20-04-16
> Can enter space in network name
> Change in yaml editor is reflected in UI
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 (Critical: Red Hat Advanced Cluster Management 2.4.6 security update and bug fixes), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.