Fix is_hostname_safe for RFC compliance
Bug #1433832 reported by
Michael Davies
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Michael Davies |
Bug Description
In review https:/
Unfortunately the implementation missed a couple of other changes that would allow a hostname to be used as the Node's logical name. Specifically:
1) Change to a maximum of 255 chars
2) Allowing each hostname or domain name in the FQDN to be up to 63 chars
3) Differentiating between hostname, and domain name (different regexs required)
4) Allowing _ in the domain names
5) Allowing . at the end of a FQDN
Also added tests for the above rules.
Changed in ironic: | |
assignee: | nobody → Michael Davies (mrda) |
Changed in ironic: | |
milestone: | none → kilo-3 |
Changed in ironic: | |
milestone: | kilo-3 → kilo-rc1 |
Changed in ironic: | |
importance: | Undecided → Medium |
Changed in ironic: | |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/165666
Review: https:/