/srv/irclogs.ubuntu.com/2022/01/30/#cloud-init.txt

raidandfadehowdy, me again! can't for the life of me get centos8 to learn network settings from cloud-init - i can see it reading network settings from openstack and it even has the sysconfig/ifcfg configs (apart from accept_ra which is false despite being set to true) - but the interface is still just dhcp.. additionally, there's ens3 interfaces lying around00:02
raidandfadethat dont seem to be doing anything?00:02
minimalraidandfade: have you tried enabling debugging for cloud-init so it will log more detail of what it is doing?01:07
raidandfadeI haven't, admittedly. I had the same sort of behavior on centos7 as well but i worked around it by adding a bootcmd to restart the network service after cloud-init completed01:07
raidandfadesame thing doesnt seem to work here01:08
minimalif you edit /etc/cloud/cloud.cfg.d/05)logging.conf there are several "level=INFO" entries that you can change to "level=DEBUG" and then reboot01:12
raidandfadeStderr: Error: Nexthop has invalid gateway. - fun01:14
raidandfadelooks like its not adding static routes with link scope?01:14
raidandfadei can't find any explanation of why ipv6 isn't being added though, or why it converts accept_ra to IPV6_FORCE_ACCEPT_RA=no01:16
raidandfadeanything specific you want out of the log? im doing a search for "network" and it looks pretty similar to what i get out of debian with debugging01:17
raidandfadeall the net configs look like what i expect them to be, and there's no errors when writing them either: util.py[DEBUG]: Writing to /etc/sysconfig/network-scripts/ifcfg-eth0 - wb: [644] 272 bytes01:19
minimalraidandface: I've only used static IPv6 so far myself01:19
minimalare you using v1 or v2 network YAML format? I tend to use v201:20
raidandfadethe ip address is static, it's just accept_ra that is anomalous in our setup01:20
raidandfadecentos8 only supports sysconfig as far as i can tell, so v1?01:21
raidandfadethe datasource is openstack01:21
minimalI'm using eni with NoCloud01:21
raidandfadeill give it a shot with eni01:21
minimalthink only Debian and Alpine (and possibly Ubuntu) support eni01:30
raidandfadeyeah thats what i was thinking as well01:30
raidandfadeeni is effectively ifupdown, which is replaced by networkmanager (nmcli) on centos801:30
raidandfadeoddly enough... rebooting the system fixed all the network issues?01:31
raidandfadeit's accepting RA and has all ips01:31
raidandfadeand the non-scoped routes from before have scopes now01:32
minimalperhaps the issue was only on 1st boot? typically during that it will have created the sysconfig stuff and then subsequent boots will use that file directly01:35
raidandfadeodd01:39
=== EugenMayer5 is now known as EugenMayer
hffgbbbffdAnyone possibly know why all my sudo commands timeout from cloud init but not other services? I googled around and saw some bugs in systemd and selinux, but I'm on all those updates versions.16:14
holmanbhffgbbbffd: what's your cloud-config?16:35
hffgbbbffdholmanb https://pastebin.com/EZy91zrV17:13
hffgbbbffdcontents of /etc/cloud/cloud.cfg17:13
henkhttps://cloudinit.readthedocs.io/en/latest/topics/format.html AFAICT »make-mime subcommand takes pairs of (filename, “text/” mime subtype) separated by a colon« is phrased incorrectly. it should be something like »The make-mime subcommand’s option "-a" can be given multiple times and takes a pair of 'filename' and '“text/” mime subtype' separated by a colon«23:25
henkbecause the subcommand itself does not take pairs, it seems from the following example23:25
minimalhenk: open an PR in the cloud-init github repo or raise bug on launchpad?23:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!