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.
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`.
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.
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` .