manual provider: network-get --primary-address returns a hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips | ||
2.2 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.3 |
Fix Released
|
High
|
Eric Claude Jones | ||
OpenStack Nova Compute Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
Seen on nova-compute rev. 273 deploying Ocata (15.0.6).
The charm creates a nova.conf that uses a hostname for my_ip:
my_ip = bob.example.com
This looks innocent enough, but nova.compute.
2017-10-04 14:51:54.232 26850 ERROR nova.compute.
2017-10-04 14:51:54.301 26850 WARNING nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
2017-10-04 14:51:54.302 26850 ERROR nova.compute.
Since the compute host fails to do this update, it never actually becomes available to the scheduler, and thus can't receive newly booted instances. This persists until my_ip is manually fixed (to contain an actual IP address), followed by a restart of nova-compute on that node.
The reasons for the error quoted above actually rather escape me, because bob.example.com is of course perfectly resolvable via an /etc/hosts entry on that node, but that's evidently an upstream bug.
What makes me file a bug against the charm is that the template that generates this (https:/
my_ip = {{ host_ip }}
So my question is, why and under what circumstances would host_ip contain a hostname rather than an actual IP address? And how can this be fixed?
Changed in juju: | |
assignee: | nobody → Eric Claude Jones (ecjones) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | none → 2.4.1 |
Changed in juju: | |
assignee: | Eric Claude Jones (ecjones) → Joseph Phillips (manadart) |
status: | Confirmed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Could you provide the following output:
juju status # make sure it includes juju version information associated with model at the top
juju config nova-compute
# replace unit-name/number with the node you see this on
juju run --unit nova-compute/0 -- network-get --primary-address cloud-compute
juju run --unit nova-compute/0 -- unit-get private-address