Bug 1899147 - IPv6 square brackets is marked invalid format in bare metal asset screen
Summary: IPv6 square brackets is marked invalid format in bare metal asset screen
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Design
Version: rhacm-2.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Jeff Brent
QA Contact:
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-18 15:51 UTC by Chad Crum
Modified: 2021-03-04 13:51 UTC (History)
2 users (show)

Fixed In Version: rhacm-2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-04 13:51:12 UTC
Target Upstream Version:
Embargoed:
gghezzo: rhacm-2.2+


Attachments (Terms of Use)
Screen shot of error (59.88 KB, image/png)
2020-11-18 15:51 UTC, Chad Crum
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 7187 0 None None None 2021-02-22 14:12:28 UTC

Description Chad Crum 2020-11-18 15:51:11 UTC
Created attachment 1730597 [details]
Screen shot of error

Description of problem:
In the create bare metal asset page, when adding a "Baseboard Management Controller Adddress" that is IPv6, the field is marked "Invalid format of BMC address" when using square brackets around the IPv6 address. The square brackets are valid to separate IP address from port - See  RFC 3986, section 3.2.2

Version-Release number of selected component (if applicable):
2.1 production (redhat-operators)

How reproducible:
100%


Steps to Reproduce:
1. Create "Bare metal asset"
2. Add "redfish://[fd2e:6f44:5dd8::1]:8000/redfish/v1/Systems/adf9ece1-0b81-411e-b102-ea77951a7563" to Baseboard Management Controller address

Actual results:
Receive "Invalid format of BMC address" and unable to Create asset


Expected results:
Allows entry and create asset

Additional info:
If I remove the square bracket the error goes away

Comment 6 errata-xmlrpc 2021-03-04 13:51:12 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 (Red Hat Advanced Cluster Management for Kubernetes version 2.2 images), 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/RHEA-2021:0729


Note You need to log in before you can comment on or make changes to this bug.