Thanks for the info, Eddy! Based on those logs, I've confirmed that this isn't an error condition. Examining the code, it looks like we intentionally set the hostname differently on RHEL-based systems vs all other distros: compare the default behaviour in https://github.com/canonical/cloud- init/blob/baf11418c196ca72e6d570b64051d8ed35065abb/cloudinit/distros/__init__.py#L237-L242 with the RHEL behaviour in https://github.com/canonical/cloud- init/blob/baf11418c196ca72e6d570b64051d8ed35065abb/cloudinit/distros/rhel.py#L94-L99.
I'm not 100% sure why this is the case, I'll ask around. I will note that this may mean that "Red Hat says that this is not an issue with the ansible ovirt_vm package which is calling the cloud-init library." isn't accurate: they may be incorrectly relying on Red Hat-specific default behaviour even when deploying non-Red Hat distros. In the meantime, if you are able to influence the cloud-config that is passed to the VMs, then passing both `fqdn` and `hostname` would probably address the issue: https://cloudinit.readthedocs.io/en/latest/topics/modules.html#set- hostname -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883649 Title: cloud-init on Ubuntu 18.04 does not set FQDN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1883649/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
