Bug 2080503 - vSphere network name doesn't allow entering spaces and doesn't reflect YAML changes
Summary: vSphere network name doesn't allow entering spaces and doesn't reflect YAML c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.4.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: rhacm-2.5
Assignee: John Swanke
QA Contact: kurwang
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-29 20:27 UTC by Kevin Cormier
Modified: 2022-06-09 02:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2074766
Environment:
Last Closed: 2022-06-09 02:11:57 UTC
Target Upstream Version:
Embargoed:
kcormier: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 22118 0 None None None 2022-04-29 22:52:35 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:12:08 UTC

Comment 1 kurwang 2022-05-09 18:04:56 UTC 
For ACM 2.5 (Build 2.5.0-DOWNSTREAM-2022-05-04-22-48-12)
I am allowed to enter spaces for the network name, however the yaml editor bug still persists, when I enter something, it isnt reflected in the ui.
Comment 2 bot-tracker-sync 2022-05-12 18:46:06 UTC 
G2Bsync 1125040402 comment 
 jeswanke Thu, 12 May 2022 14:07:18 UTC 
 G2Bsync  What's the impact if the bug is deferred?
 "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."
Risk of fix to destabilize your code (H, M, L)?
L
Any viable workarounds that could be documented?
paste in the name
Comment 3 Kevin Cormier 2022-05-12 20:53:04 UTC 
Fix delivered May 12.
Comment 4 kurwang 2022-05-16 17:57:01 UTC 
Verified issue on 2.5.0-DOWNSTREAM-2022-05-13-16-47-16
Comment 8 errata-xmlrpc 2022-06-09 02:11:57 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: Red Hat Advanced Cluster Management 2.5 security updates, images, 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.

https://access.redhat.com/errata/RHSA-2022:4956
Note You need to log in before you can comment on or make changes to this bug.