Bug 1512579 - The UI rejects FQDNs as input to IPMI address if their depth is > 3
Summary: The UI rejects FQDNs as input to IPMI address if their depth is > 3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Jason E. Rist
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks: 1627870 1713381
TreeView+ depends on / blocked
 
Reported: 2017-11-13 15:08 UTC by Udi Kalifon
Modified: 2019-07-02 20:08 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-ui-9.3.1-0.20190506152409.f3ba58f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1627870 1713381 (view as bug list)
Environment:
Last Closed: 2019-07-02 20:08:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 595847 0 None None None 2018-08-23 18:51:21 UTC
Red Hat Product Errata RHBA-2019:1672 0 None None None 2019-07-02 20:08:44 UTC

Description Udi Kalifon 2017-11-13 15:08:30 UTC 
Description of problem:
If your server's IPMI has a FQDN with more than 2 dots in the name, the UI rejects the input as invalid.

For example:
aaa.bbb.com is accepted
aaa.bbb.ccc.ddd.com is not accepted

FQDNs may be quite long in enterprizes' networks and we shouldn't limit the depth of the url.


Version-Release number of selected component (if applicable):
openstack-tripleo-validations-7.4.1-2.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Go to the Nodes page.
2. Click on Register Nodes.
3. Click "Add New".
4. Write "aaa.bbb.ccc.ddd.com" in the IPMI address field.


Actual results:
The form validation rejects the input.


Expected results:
FQDNs of any length should be accepted.
Comment 5 Jason E. Rist 2018-09-11 18:00:32 UTC 
Merged upstream.
Comment 10 Udi Kalifon 2019-06-25 10:32:05 UTC 
Verified in: openstack-tripleo-ui-9.3.1-0.20190506152409.f3ba58f.el7ost.noarch
Comment 13 errata-xmlrpc 2019-07-02 20:08:26 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, 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/RHBA-2019:1672
Note You need to log in before you can comment on or make changes to this bug.