On 10/06/15 13:31, Dan Watkins wrote: > Hi Joe, > > On 10/06/15 10:52, Joe Clifford wrote: >> Apologies for the tardy feedback. Many thanks to all involved, >> gratefully and much appreciated. From my perspective, this issue is now >> resolved. > > Thanks for the feedback. Great to hear that we've resolved this for you! > >> I've just tried this on a freshly deployed Trusty VM in Azure - a >> change to the hostname with 'hostnamectl' is now preserved when the VM >> is rebooted. >> >> I would like to point out though that, if not editing the /etc/hostname >> file directly, the 'hostnamectl' command must be used to set the >> hostname; using the 'hostname' command doesn't work (presumably because >> the hostname command doesn't change /etc/hostname). > > As per the 'hostname' manpage: > > When called with one argument ..., the commands set the host name ... > Note, that this is effective only until the next reboot. Edit > /etc/hostname for permanent change. > > So that sounds like expected behaviour. :) Indeed! It's been a long time since I read that manpage.
Thanks again. > > > Thanks, > > Dan > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1375252 Title: [SRU] Hostname change is not preserved across reboot on Azure Ubuntu VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1375252/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
