nova metadata service breaks on hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
For more than a year, i have deployed multiple clusters using openstack-ansible.
This particular case is using FQDN for the internal and external endpoint.
[DEFAULT]
...
# Metadata
metadata_host = my-int.XXX.com
metadata_port = 8775
metadata_workers = 3
...
Recently, this breaks nova-metadata.
2017-08-25 21:19:02.928 18130 WARNING oslo_reports.
2017-08-25 21:19:02.931 18130 INFO nova.network.driver [-] Loading network driver 'nova.network.
2017-08-25 21:19:03.078 18130 CRITICAL nova [-] AddrFormatError: failed to detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova sys.exit(main())
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova server = service.
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova return manager_class()
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova self.network_
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova (CONF.metadata_
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova if ((netaddr.
2017-08-25 21:19:03.078 18130 ERROR nova File "/openstack/
2017-08-25 21:19:03.078 18130 ERROR nova 'address from %r' % addr)
2017-08-25 21:19:03.078 18130 ERROR nova AddrFormatError: failed to detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:03.078 18130 ERROR nova
2017-08-25 21:19:09.833 18137 WARNING oslo_reports.
2017-08-25 21:19:09.836 18137 INFO nova.network.driver [-] Loading network driver 'nova.network.
2017-08-25 21:19:10.040 18137 CRITICAL nova [-] AddrFormatError: failed to detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:10.040 18137 ERROR nova Traceback (most recent call last):
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova sys.exit(main())
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova server = service.
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova self.manager = self._get_manager()
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova return manager_class()
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova self.network_
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova (CONF.metadata_
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova if ((netaddr.
2017-08-25 21:19:10.040 18137 ERROR nova File "/openstack/
2017-08-25 21:19:10.040 18137 ERROR nova 'address from %r' % addr)
2017-08-25 21:19:10.040 18137 ERROR nova AddrFormatError: failed to detect a valid IP address from 'my-int.XXX.com'
2017-08-25 21:19:10.040 18137 ERROR nova
Changing hostname to IP address fixes it.
# Metadata
metadata_host = 172.16.236.2
metadata_port = 8775
metadata_workers = 3
...
Is this a bug? or a new change? or should we now should not use FQDN in host ?
Thanks,
Shashi
affects: | openstack-ansible → nova |
Which release were you using when this worked, and which release did you upgrade to where it no longer works?