OpenStack Neutron Open vSwitch Charm

  1. Bug #1839300
  2. Comment #15

Comment 15 for bug 1839300

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-openvswitch (master)

Reviewed: https://review.opendev.org/701929
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=ee709a5ab30f285ecc1dd3ddb998af970f22e17e
Submitter: Zuul
Branch: master

commit ee709a5ab30f285ecc1dd3ddb998af970f22e17e
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
    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.

    Use of a specific interface was chosen due to ``socket.getfqdn()``
    not giving reliable results (https://bugs.python.org/issue5004).

    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: I82db81937e5a46dc6bd222b7160ca1fa5b190c10
    Change-Id: Ic8f8742261b773484687985aa0a366391cd2737a
    Closes-Bug: #1839300