| smoser | interesting network config openstack change | 00:43 |
|---|---|---|
| smoser | https://review.openstack.org/#/c/312626/ | 00:43 |
| blackboxsw | nice refernce smoser | 02:06 |
| blackboxsw | reference even | 02:06 |
| === Savicq is now known as Saviq | ||
| blackboxsw | some interesting cases in Azure IMDS, the metadata service provides no way to distringuish between static IPs and dynamic IPs. so cloud-init can't really know what to set as dhcp versus static. | 17:21 |
| blackboxsw | examples in my hackmd doc from earlier | 17:21 |
| blackboxsw | and running dhcp on eth1 gets only one private addr. | 17:21 |
| smoser | hm.. | 17:23 |
| dgautam | I am facing util.py[DEBUG]: failed stage init-local" error. it is failing for bond-master keywork. any pointers ? | 18:33 |
| dgautam | File "/usr/lib/python2.7/site-packages/cloudinit/net/sysconfig.py", line 455, in _render_bond_interfaces iface_master_name = iface['bond-master'] | 18:33 |
| dgautam | File "/usr/lib/python2.7/site-packages/cloudinit/net/sysconfig.py", line 455, in _render_bond_interfaces | 18:33 |
| dgautam | iface_master_name = iface['bond-master'] | 18:33 |
| dgautam | KeyError: 'bond-master' | 18:33 |
| smoser | dgautam, where is this ? | 18:37 |
| smoser | i'm guessing this is centos based on 2.7 | 18:38 |
| smoser | and likely fixed in upstream | 18:38 |
| smoser | you check with a copr repo | 18:38 |
| dgautam | cloudinit.log , I launched a centos 7.5 baremetal image | 18:38 |
| dgautam | I am using cloud-init 0.7.9 | 18:39 |
| smoser | https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/ | 18:39 |
| dgautam | smoser: Thanks . I'll try the patch or upgrade cloud-init package to latest | 18:46 |
| smoser | dgautam, that is a daily build... so it will move. | 18:49 |
| smoser | i suspect https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-stable/ will be good enouh for you. | 18:50 |
| smoser | and wont move without us doing some reasonable level of testing (which... means that it is quite old) | 18:50 |
| blkadder | Hi all... May have nothing to do with cloud-init but thought I'd ask: I am calling hostnamectl set-hostname which works when instantiating hosts and it survives a single reboot (Ubuntu 16.04/AWS). I've noticed though that it often loses the hostname on subsequent reboots and reverts to ip-whatever as the host name. Any suggestions on where to look? | 18:56 |
| === r-daneel_ is now known as r-daneel | ||
| rharper | blkadder: what does /etc/hostname say ? | 19:28 |
| rharper | before and after each step ? | 19:28 |
| blkadder | Well, when it is working the correct host name. | 19:29 |
| blkadder | When it is rebooted ip-xxx-xxx-xxx-xxx | 19:29 |
| blkadder | So the file itself is changing. | 19:29 |
| blkadder | Don't know if this is cloud-init, systemd weirdness or something else... | 19:30 |
| blkadder | Heck could be AWS for all I know... | 19:30 |
| blkadder | The weird thing is that with the vast majority of my cloud-init stuff, I do a reboot which works fine (keeps host name). It's subsequent reboots where it loses the name. | 19:31 |
| rharper | well, cloud-init will set the hostname to the hostname value in the instance metadata; | 19:31 |
| blkadder | Which it does. | 19:31 |
| blkadder | Let me dig around there for a bit. | 19:32 |
| blkadder | Thanks. | 19:32 |
| smoser1 | cloud-init is not supposed to set it if you have changed it. | 19:53 |
| blackboxsw | if cloud-init were changing hostname you | 20:01 |
| blackboxsw | if cloud-init were changing hostname you will see the following in the cloud-init.logs timestamped after your reboot: " Setting the hostname to <someamazingname>" | 20:02 |
| blackboxsw | the log I referenced is /var/log/cloud-init.log | 20:04 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!