[RFE] Allow both RFC3986 and FQDNs in Node Registration 'Name' field
Bug #1609917 reported by
Dan Trainor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiri Tomasek |
Bug Description
When "Upload From File" is used to Register nodes in the UI, the dialogue provides post-import configuration options. One of these options is for the value of 'Name'
This is likely a limitation of how Ironic stores and maintains node names. According to the Ironic WebAPI V1 spec[1], version 1.10 incorporated the usage of RFC3986 unreserved characters. This was in addition to valid FQDNs. The form field validation is only looking for valid RFC3986 unreserved characters, not both RFC3986 unreserved characters AND valid FQDNs.
The form field validation should support both RFC3986 unreserved characters and valid FQDNs.
[1] http://
Changed in tripleo-ui: | |
importance: | Undecided → Low |
status: | New → Triaged |
summary: |
- Allow both RFC3986 and FQDNs in Node Registration 'Name' field + [RFE] Allow both RFC3986 and FQDNs in Node Registration 'Name' field |
tags: | added: ui |
affects: | tripleo-ui → tripleo |
Changed in tripleo: | |
assignee: | nobody → Jiri Tomasek (jtomasek) |
milestone: | none → ocata-1 |
importance: | Low → High |
tags: | added: newton-backport-potential |
To post a comment you must log in.
I wonder if that name validation is appropriate at all, looking at http:// developer. openstack. org/api- ref/baremetal/ ?expanded= create- node-detail it sounds like the 'name' can be pretty-much free-form since 1.5? The URL mentioned in the bug is no longer valid so I'm not sure where to double-check the reference. See also bug 1632631.