The current implementations use of a specific interface to build
FQDN from has the undesired side effect of the ``nova-compute`` and
``neutron-openvswitch`` charms ending up with using different
hostnames in some situations. It may also lead to use of a
identifier that is mutable throughout the lifetime of a deployment.
Reviewed: https:/ /review. opendev. org/701928 /git.openstack. org/cgit/ openstack/ charm-nova- compute/ commit/ ?id=1869bfbc971 1eac157821f8a47 02409822c0842e
Committed: https:/
Submitter: Zuul
Branch: master
commit 1869bfbc9711eac 157821f8a470240 9822c0842e
Author: Frode Nordahl <email address hidden>
Date: Fri Jan 10 09:13:34 2020 +0100
Use hosts official name for FQDN
The current implementations use of a specific interface to build openvswitch` ` charms ending up with using different
FQDN from has the undesired side effect of the ``nova-compute`` and
``neutron-
hostnames in some situations. It may also lead to use of a
identifier that is mutable throughout the lifetime of a deployment.
Use of a specific interface was chosen due to ``socket. getfqdn( )`` /bugs.python. org/issue5004).
not giving reliable results (https:/
This patch gets the FQDN by mimickingthe behaviour of a call to
``hostname -f`` with fallback to shortname on failure.
Add relevant update from c-h.
Needed-By: Ic8f8742261b773 484687985aa0a36 6391cd2737a dc6bd222b7160ca 1fa5b190c10
Change-Id: I82db81937e5a46
Closes-Bug: #1839300