Unsetting '[DEFAULT] dhcp_domain' results in hostname corruption
Bug #1824813 reported by
Stephen Finucane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Low
|
Stephen Finucane | ||
Bug Description
Unsetting '[DEFAULT] dhcp_domain' will result in the metadata service/config drive reporting an instance hostname of '${hostname}None' instead of '${hostname}'. This is clearly incorrect behavior.
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| assignee: | nobody → Stephen Finucane (stephenfinucane) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
| Changed in nova: | |
| assignee: | Stephen Finucane (stephenfinucane) → Matt Riedemann (mriedem) |
| Changed in nova: | |
| assignee: | Matt Riedemann (mriedem) → Stephen Finucane (stephenfinucane) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/nova 20.0.0.0rc1 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/