Public bug reported: If we use manage_etc_host: true in cloud.cfg , this will enable update_etc_host module which go and update /etc/hosts file.
Right now the what happen is the dns resolvable name mapped to the local host ip (127.0.0.1 / ::1) This makes sense in case of a VM deployed with private IP, where we can ping the hostname from the VM itself. But when we deploy a VM with public IP, in that case also the FQDN is mapped against localhost IP, which doesn't make much sense. Ideally it should be FQDN should be mapped the public IP. /etc/host content in Private IP [2] Public IP [3] I even raised a concern on this in the IRC channel, but was not able to resolve the query IRC chat: [1] [1] https://irclogs.ubuntu.com/2020/11/11/%23cloud-init.html [2] http://paste.openstack.org/show/799931/ [3] http://paste.openstack.org/show/799923/ ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905281 Title: /etc/hosts data is not properly mapped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
