[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable

[Corey Bryant]

This bug was fixed in the package openvswitch - 2.15.0-0ubuntu2~cloud0
---------------

 openvswitch (2.15.0-0ubuntu2~cloud0) focal-wallaby; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 openvswitch (2.15.0-0ubuntu2) hirsute; urgency=medium
 .
   * Fix recording of FQDN/hostname on startup (LP: #1915829):
     - d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
       pick of committed upstream fix to support skip of hostname
       configuration on ovs-vswitchd/ovsdb-server startup.
     - d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
       Open vSwitch after network-online.target using new systemd unit.
     - d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
       option to `ovs-ctl` to delegate recording of hostname to the separate
       service.
     - d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
       option to `ovs-ctl` to delegate recording of hostname to the separate
       service.
     - d/openvswitch-switch.service: Add `Also` reference to
       ovs-record-hostname.service so that the service is enabled on install.
     - d/rules: Add `ovs-record-hostname.service` to package build.
 .
 openvswitch (2.15.0-0ubuntu1) hirsute; urgency=medium
 .
   * New upstream release 2.15
 .
 openvswitch (2.15.0~git20210104.def6eb1ea-0ubuntu3) hirsute; urgency=medium
 .
   * d/openvswitch-switch.ovsdb-server.service: avoid removing the state
     dir on restart (LP: #1910209)
 .
 openvswitch (2.15.0~git20210104.def6eb1ea-0ubuntu2) hirsute; urgency=medium
 .
   * d/rules: Re-align expected test failure with test numbering on
     armhf.
 .
 openvswitch (2.15.0~git20210104.def6eb1ea-0ubuntu1) hirsute; urgency=medium
 .
   * New upstream snapshot in preparation for 2.15.0 release.
   * d/p/*: Refresh
   * d/control: Bump minimum libdpdk-dev version to 20.11.
   * d/control: Add BD on libdbus-1-dev for pcap architectures.
   * d/rules: Set DPDK build to use shared libraries.
 .
 openvswitch (2.14.0-0ubuntu2) hirsute; urgency=medium
 .
   * d/openvswitch-switch.ovs*.service: Update ovs-vswitchd and ovsdb-server
     systemd unit files to use the correct environment file and environment
     variable for ovs-ctl options, /etc/default/openvswitch-switch and
     OVS_CTL_OPTS, respectively (LP: #1906280).
 .
 openvswitch (2.14.0-0ubuntu1) hirsute; urgency=medium
 .
   * New upstream release.
   * d/p/*: Refresh.
 .
 openvswitch (2.13.1-0ubuntu1) groovy; urgency=medium
 .
   [ Chris MacNaughton ]
   * d/openvswitch-switch.ovsdb-server.service: Add local-fs.target to
     systemd service file to ensure that local filesystems are ready
     before the ovsdb service tries to start (LP: #1887177).
   * d/control: Remove Breaks/Replaces that are older than Focal (LP: #1878419).
 .
   [ James Page ]
   * New upstream point release.
   * d/p/py3-compat.patch: Refresh.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1915829

Title:
  FQDN / hostname recorded in OVSDB is unreliable

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in openvswitch package in Ubuntu:
  Fix Released
Status in openvswitch source package in Focal:
  Triaged
Status in openvswitch source package in Groovy:
  Triaged
Status in openvswitch source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  The Open vSwitch init script `ovs-ctl` determines the system hostname
  and records it in the `external-ids:hostname` field of the `Open-
  vSwitch` table in the local OVSDB.

  This value may be consumed by downstream software and having it unset
  or set to a incorrect value could lead to erratic behavior of a
  system.

  In recent Ubuntu development we have also made it possible to
  configure Open vSwitch with netplan.io, which allows for a Open
  vSwitch controlled data path to be the only external network
  connection on a system.

  As such the current startup sequence of Open vSwitch is insufficient
  to allow for reliable recording of FQDN / hostname at system boot-up
  time.

  Examples of downstream issues can be viewed in bug 1896630 and bug
  1912844 comment #26.

  [ Test Case ]

  1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy.
  2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`.
  3) Add a PPA with the updated Open vSwitch package to MAAS.
  4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS.

  [ Regression potential ]

  Minimal, the update uses the exact same methods to accomplish the end
  result of recording the hostname as before, we have only re-ordered
  when the events occur to ensure successful operation.

  [ Other Info ]

  A possible solution to this would be to extend the upstream `ovs-ctl`
  script to allow controlling when the hostname is recorded and adding a
  new Systemd service file to the package that calls the `record-
  hostname` function at a more appropriate time, i.e. after or as part
  of the `network-online.target`.

  An example of downstream issues can be viewed in bug 1896630.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1915829/+subscriptions