Comment 4 for bug 1896630
Revision history for this message
| Frode Nordahl (fnordahl) wrote Re: ovn-chassis subordinate to octavia registered with shortname shows down | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Looking a bit at how this behaves on different providers:
- OpenStack: we do not see the issue
- OpenStack+LXD (fan networking): unknown
- MAAS: we do not see the issue
- MAAS+LXD: we consistently see the issue
When deploying on metal with MAAS, MAAS will add the FQDN to the localhost record in /etc/hosts so that issuing the `hostname -f` command will always succeed regardless of availability of the network.
When deploying on the other provider combinations it is Juju that does the host initialization and Juju does not add the FQDN to the localhost record in /etc/hosts.
Possible causes for the change of behaviour:
A change in LXD and/or Linux bridge configuration pertaining availability of network in the early boot cycle of the instance?
A change in MAAS pertaining how/when the DNS records for the LXD container are populated?
Possible long term solutions:
Should Juju populate /etc/hosts with a FQDN for the localhost record the same way MAAS does for on-metal deployments?