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/701929 /git.openstack. org/cgit/ openstack/ charm-neutron- openvswitch/ commit/ ?id=ee709a5ab30 f285ecc1dd3ddb9 98af970f22e17e
Committed: https:/
Submitter: Zuul
Branch: master
commit ee709a5ab30f285 ecc1dd3ddb998af 970f22e17e
Author: Frode Nordahl <email address hidden>
Date: Fri Jan 10 10:57:44 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.
Depends-On: I82db81937e5a46 dc6bd222b7160ca 1fa5b190c10 484687985aa0a36 6391cd2737a
Change-Id: Ic8f8742261b773
Closes-Bug: #1839300