[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
Frode Nordahl
1915829 at bugs.launchpad.net
Fri Mar 5 16:33:56 UTC 2021
** Changed in: openvswitch (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: openvswitch (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openvswitch (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: openvswitch (Ubuntu Hirsute)
Importance: High
Assignee: Frode Nordahl (fnordahl)
Status: Fix Committed
** Changed in: openvswitch (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: openvswitch (Ubuntu Focal)
Importance: Undecided => High
** Changed in: openvswitch (Ubuntu Groovy)
Status: New => Triaged
** Changed in: openvswitch (Ubuntu Focal)
Status: New => Triaged
** Changed in: openvswitch (Ubuntu Groovy)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: openvswitch (Ubuntu Focal)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
--
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 openvswitch package in Ubuntu:
Fix Committed
Status in openvswitch source package in Focal:
Triaged
Status in openvswitch source package in Groovy:
Triaged
Status in openvswitch source package in Hirsute:
Fix Committed
Bug description:
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`.
An example of downstream issues can be viewed in bug 1896630.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1915829/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list