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/702172 /git.openstack. org/cgit/ openstack/ charm-nova- compute/ commit/ ?id=66405e2092d 8739a66e40ea054 827d842fa97924
Committed: https:/
Submitter: Zuul
Branch: stable/19.10
commit 66405e2092d8739 a66e40ea054827d 842fa97924
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 mimicking the behaviour of a call to
``hostname -f`` with fallback to shortname on failure.
Add relevant update from c-h.
Change-Id: I82db81937e5a46 dc6bd222b7160ca 1fa5b190c10 157821f8a470240 9822c0842e)
Closes-Bug: #1839300
(cherry-picked from 1869bfbc9711eac