grizzly uses FQDN for services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Michael Still |
Bug Description
grizzly has started using FQDN for nova services as opposed to short hostname. This means that anyone upgrading from Folsom will end up with a double list of services. e.g.:
root@api01:~# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth api01 internal enabled XXX 2013-03-07 02:04:42
nova-scheduler api01 internal enabled XXX 2013-03-07 02:04:42
nova-scheduler api01.sy3.
nova-consoleauth api01.sy3.
If the user is running a large installation this will result in a massive list of double services.
Please consider updating nova-manage db sync such that it either removes all existing services in the nova.services table or that it updates the entries in the table to match the FQDN.
Changed in nova: | |
importance: | Medium → Critical |
Changed in nova: | |
assignee: | nobody → Michael Still (mikalstill) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
This is the related change:
commit 5dd1553cca7f7e6 2eebce75e1d936f c211b239ec
Author: Luis Fernandez Alvarez <email address hidden>
Date: Tue Sep 25 17:33:59 2012 +0200
Replaced default hostname function from gethostname to getfqdn
Fixes bug 1055503
The standard behaviour of the 'gethostname' function in Python differs from
Linux to Windows. A common Linux configuration returns the FQDN, while a
Windows one returns only the host name.
To resolve inconsistent node naming in deployments that mix windows and
Linux, it is proposed to use 'getfqdn' as default function instead of
'gethostname'. This is function is more predictable in all cases.
Change-Id: I3164d9a36df2b8 484bbf9a57879c3 1fa0e342503