Bug 2080503
Summary: | vSphere network name doesn't allow entering spaces and doesn't reflect YAML changes | ||
---|---|---|---|
Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Kevin Cormier <kcormier> |
Component: | Console | Assignee: | John Swanke <jswanke> |
Status: | CLOSED ERRATA | QA Contact: | kurwang |
Severity: | medium | Docs Contact: | Christopher Dawson <cdawson> |
Priority: | medium | ||
Version: | rhacm-2.4.z | CC: | cdawson, dho, dhuynh, ecai, huichen, kurwang |
Target Milestone: | --- | Flags: | kcormier:
rhacm-2.5+
|
Target Release: | rhacm-2.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 2074766 | Environment: | |
Last Closed: | 2022-06-09 02:11:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 1
kurwang
2022-05-09 18:04:56 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 Fix delivered May 12. Verified issue on 2.5.0-DOWNSTREAM-2022-05-13-16-47-16 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 |