On Tue, Jun 18, 2013 at 9:31 AM, Sandro "red" Mathys <red@xxxxxxxxxxxxxxxxx> wrote: > I just gave the F19 TC5 cloud image [1] a spin and the first impression is > very good (great job, Matthew!) except for one thing. Can anyone reproduce > the following? > > [root@f19t2 ~]# journalctl -u cloud-init.service | grep hostname > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]: Failed > to set the hostname to f19t2.novalocal (f19t2) > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Failed to > set the hostname to f19t2.novalocal (f19t2) > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]: Running > set_hostname (<module 'cloudinit.config.cc_set_hostname' from > '/usr/lib/python2.7/site-packages/cloudinit/config/cc_set_hostname.pyc'>) > failed > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running > set_hostname (<module 'cloudinit.config.cc_set_hostname' from > '/usr/lib/python2.7/site-packages/cloudinit/config/cc_set_hostname.pyc'>) > failed > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] helpers.py[DEBUG]: > Running config-update_hostname using lock (<cloudinit.helpers.DummyLock > object at 0x32dbb10>) > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] > cc_update_hostname.py[DEBUG]: Updating hostname to f19t2.novalocal (f19t2) > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running > command ['hostname'] with allowed return codes [0] (shell=False, > capture=True) > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] __init__.py[DEBUG]: > Attempting to update hostname to f19t2.novalocal in 1 files > Jun 18 07:02:47 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Running > command ['hostnamectl', 'set-hostname', 'f19t2.novalocal'] with allowed > return codes [0] (shell=False, capture=True) > Jun 18 07:03:12 f19t2 cloud-init[447]: [CLOUDINIT] util.py[WARNING]: Failed > to write hostname f19t2.novalocal to /var/lib/cloud/data/previous-hostname > Jun 18 07:03:12 f19t2 cloud-init[447]: [CLOUDINIT] util.py[DEBUG]: Failed to > write hostname f19t2.novalocal to /var/lib/cloud/data/previous-hostname > [root@f19t2 ~]# hostname > f19t2 > > So the hostname is set to f19t2 (the name I gave the instance) somehow but > setting it to f19t2.novalocal fails...not even sure why it's set in two > different ways and to two different values. > > Let me know if more information is required or if it's worth opening a bug > report for this issue. See https://bugzilla.redhat.com/show_bug.cgi?id=964006 ...Juerg > -- Sandro > > [1] https://dl.fedoraproject.org/pub/alt/stage/19-TC5/Images/ > > > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
