I think that the bug here is that cloud-init is running the 'hostname_bounce' on every boot, rather than just the first of the instance.
It would seem to be suitable, and much simpler if we just make it do that only on a new instance id. Can we just make the datasource check if its found instance-id is the same as a previous one (stored in /var/lib/cloud/data/previous-instance-id ) and do the hostname bounce only if different ? it looks like it might need some re-ordering, as we're currently setting the hostname before we know our instance-id, but i think it should be doable. generally speaking we want to avoid modifying config files as the user will then see a prompt on an upgrade of dhcp that included a change to that file. -- https://code.launchpad.net/~utlemming/cloud-init/lp1375252/+merge/247494 Your team cloud init development team is requested to review the proposed merge of lp:~utlemming/cloud-init/lp1375252 into lp:cloud-init. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : cloud-init-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp
