Comment 13 for bug 1896630
Revision history for this message
| Frode Nordahl (fnordahl) wrote Re: ovn-chassis subordinate to octavia registered with shortname shows down | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
Hum, this may be a catch-22 in the service ordering, looking closer at console while a affected container boots:
[ OK ] Reached target Network (Pre).
Starting Open vSwitch Database Unit...
Starting Network Service...
[ OK ] Started Open vSwitch Database Unit.
Starting OpenVSwitch configuration for cleanup...
Starting Open vSwitch Forwarding Unit...
[ OK ] Started Open vSwitch Forwarding Unit.
[ OK ] Finished OpenVSwitch configuration for cleanup.
[ OK ] Started Network Service.
Starting Wait for Network to be Configured...
Starting Network Name Resolution...
[ OK ] Finished Wait for Network to be Configured.
Starting Initial cloud-init job (metadata service crawler)...
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Host and Network Name Lookups.
Looking at output from journalctl -u:
Feb 01 15:16:59 juju-b10aeb-6-lxd-7 ovs-ctl[419]: hostname: Temporary failure in name resolution
root@juju-
File: /run/systemd/
Size: 73 Blocks: 8 IO Block: 4096 regular file
Device: c0h/192d Inode: 34 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2021-02-01 15:26:34.294834047 +0000
Modify: 2021-02-01 15:22:29.621531946 +0000
Change: 2021-02-01 15:22:29.621531946 +0000
Birth: -
File: /run/systemd/
Size: 191 Blocks: 8 IO Block: 4096 regular file
Device: c0h/192d Inode: 35 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2021-02-01 15:26:39.582862189 +0000
Modify: 2021-02-01 15:22:29.621531946 +0000
Change: 2021-02-01 15:22:29.621531946 +0000
Birth: -
With the addition of support for OVS in netplan I assume we also need OVS to run prior to netplan running, which kind of creates a cyclic dependency wrt. Open vSwitch's init script updating its database with FQDN from call to `hostname -f` each boot.
This is hidden on the physical host as MAAS / cloud-init manages /etc/hosts