/srv/irclogs.ubuntu.com/2021/12/14/#cloud-init.txt

=== gschanuel218 is now known as gschanuel21
cpaelzerthemachine: I'm not sure if I got all of the backscroll on the topic, but you could force a defined serial to those disks in your qemu/libvirt setup. And then in the guest use them as /dev/disk/by-id/... independent to the (Filesystem-)UUID that it gets after formatting06:05
themachinecpaelzer: Thank you. I will look into that.06:08
eggbeanDoes anybody know what is wrong with this? It makes the server unreachable.06:14
eggbeanbootcmd:06:14
eggbean       - [ printf, 'prepend domain-search "${domain}";', >>, /etc/dhcp/dhclient.conf ]06:14
eggbean       - [ systemctl, restart, systemd-resolved.service ]Y06:14
eggbean^ should be two spaces06:15
eggbeanbootcmd:06:16
eggbean  - [ cloud-init-per, once, edit-file, printf, 'prepend domain-search "${domain}";', >>, /etc/dhcp/dhclient.conf ]06:16
eggbean  - [ cloud-init-per, once, restart-service, systemctl, restart, systemd-resolved.service ]06:16
eggbeanY06:16
eggbeanDo I need to escape the single quotes or something like that?06:16
eggbeanOkay, I needed to enclose the >> in quotes06:28
cpaelzerglad you found that eggbean, but wouldn't that be more naturally go through v2 network https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html being netplan that allows dhcp overrides https://netplan.io/reference/#dhcp-overrides ?06:29
eggbeancpaelzer: This is Debian. When I read the AWS docs on doing this it mentioned netplan on Ubuntu, but there it doesn't appear to be present on Debian06:31
eggbeanYeah, netplan seems to be a ubuntu thing06:33
eggbeanI suppose cloud-init is canonical as well06:33
eggbeanThanks for the tip though06:34
cpaelzerNetwork config v1 allows to set those without netplan, let me fetch some links for you to consider06:37
eggbeancheers06:37
cpaelzerlike: https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v1.html?highlight=nameserver#nameserver maybe?06:37
cpaelzerI did not see/try to combine dhcp+search domain via that, so no guarantees06:38
cpaelzerbut worth a try, OTOH if you are just happy with your cconfig that now works I have no reason to stop you from using it :-)06:38
eggbeanThat seems to be for changing the dns servers06:38
eggbeanI am just adding a dns search domain here. But I can see that line in that code, so it is probably elsewhere on that page06:39
cpaelzeryou are right, I was just quickly looking for the keywords in the docs ...06:39
eggbeanWould I be able to just add that line, leaving the rest out (apart from parents)?06:40
cpaelzerI have not seen such a combination in the examples, but often found that cloud-init config variations are easy to try06:41
cpaelzermost of the cloud-init people that know what they talk about (=not me) will be up in ~8-9h - they might be able to help further :-)06:41
eggbeanok thanks. I find that the logs don't give much to go on with failures06:41
themachinecpaelzer: Thanks again. That was the final piece of my puzzle and one that I'm sure I'll reuse in the future.07:19
cpaelzerhappy to hear that themachine07:34
=== meena2 is now known as meena
=== Orpheus[m] is now known as O[m]
jchittumlooks like `httpretty==0.9.5` breaks on python==3.9.7` due to changes in `Threading`. I bumped to `1.1.4` for local testing and `xenial-dev` ran fine. This will cause some issues for folks running impish+ and developing `cloud-init`22:32
jchittumthis is due to `threading.Thread().isAlive()` no longer existing: AttributeError: 'Thread' object has no attribute 'isAlive'22:34
jchittumalso whopps. that's an amazing badly matched tick marks. good job me22:34
jchittumshould i be using something like `pyenv` to do a python 3.5 environment to run the xenial tests?22:39
falcojrjchittum: we only specify `httpretty>=0.7.1` in the requirements file so we can use different versions depending on whats in the repos22:44
falcojron travis it's grabbing 0.8.6 for 3.5 and 1.1.4 for 3.922:45
blackboxswjchittum: so `tox -e xenial-dev` will not work on hirsute ++ I think.  23:25
blackboxswfalcojr: It's probably not something we even want anymore in tox default targets. Cloud-init is no longer publishing releases to Xenial for cloud-init. Our CI also only runs `tox -e xenial` in Travis from a compatibility check standpoint  (note: not the xenial-dev target). 23:25
blackboxswultimately tox default test environements should probably only be py3,  flake8, pylint (and eventually "black" and "isort" too per your PR )23:28
blackboxswthat said: if we want to keep xenial-dev as a tox env in our local test rotation, I think we can bump it specifically to 1.1.4 in tox.ini at the moment. It'll at least then pass on hirsute++ which is probably where most of our dev envs are running anyway.23:34
jchittumok. so with my pr for LP: 1954842 I'll leave the env untouched, and know that CI will pick a more correct matching version.23:55
ubottuLaunchpad bug 1954842 in cloud-init "ubuntu-advantage enable fips will fail due to missing --assume-yes" [Medium, Triaged] https://launchpad.net/bugs/195484223:55
jchittumblackboxsw: I'm just community on this, but i'd agree with just dropping it. and giant +1s to black and isort (do you want me to go ahead and run those manually now? I'll happily do so :) )23:56

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