=== tds3 is now known as tds
Odd_BlokeOoh, OK, I had convinced myself it was only CentOS, thanks for that!14:23
Odd_Blokeblackboxsw: falcojr: Should we disable the stale bot for the break?  ~Everything will get closed out otherwise, I suspect.14:31
meenagiven the amount of crap in that pr of mine that just got closed, i might just open a fresh one14:37
Odd_Blokemeena: So long as you retain a reference to the old one, so we can find older conversations, that's a reasonable approach. :)14:44
Odd_Blokeblackboxsw: falcojr: https://github.com/canonical/cloud-init/pull/735 <-- I think that'll do it, but let's chat at stand-up to confirm I'm not missing anything14:44
Odd_Blokefalcojr: blackboxsw: I've opened up a variety of PRs for bits and pieces that have occurred to me over the past couple of weeks, but I haven't had time for; all small: https://github.com/canonical/cloud-init/pull/733 https://github.com/canonical/cloud-init/pull/736 https://github.com/canonical/cloud-init/pull/73715:26
falcojrcool, I'll jump to it15:27
falcojrI'll add a reminder to my calendar to turn the check back on ;)15:43
Odd_BlokeI've also added a snoozed card on our Trello board, so hopefully between all that we'll remember. :)15:49
Odd_BlokeHmm, looks like stale is going to error every time now, will fix that.17:36
Odd_Blokeblackboxsw: falcojr: https://github.com/canonical/cloud-init/pull/74017:42
Odd_Blokefalcojr: I see a new commit pushed to #738, but the name of the Travis job still includes "WIP".18:30
falcojrah, sorry...thought you were referring to the PR itself, not the name19:05
Odd_BlokeYep, I could have made that more obvious!19:12
blackboxswOdd_Bloke: I think I'm hitting this with latest `tox -e doc` on focal on your PR https://github.com/canonical/cloud-init/pull/739/files19:26
blackboxswon master I don't this error: https://paste.ubuntu.com/p/WjND4KXjqs/   https://github.com/sphinx-doc/sphinx/issues/840019:26
blackboxswI'm looking more closely now. just wanted to reflect that issue to see if you hit that or whether you were in another build env19:27
blackboxswahh on master looks like Running Sphinx v1.8.5 o your brach Sphinx v.3.3.119:27
Odd_Blokeblackboxsw: We're pinned at sphinx<2 in doc-requirements.txt.19:27
blackboxswd'oh PEBChadAndKeyboard19:28
blackboxswI had a local branch alias called oddbloke/doc that was conflicted with your PR19:29
blackboxswturns out if you checkout a branch from Jan 2020. it doesn't behave the same way as your current PR19:29
Odd_BlokeI did notice "19.4" and wonder.19:32
blackboxswOdd_Bloke: WDYT about renaming debugging and testing cloud-init topic in RTD to just "debugging cloud-init" as it is with your branch we now have 3 top-level topics that include "testing" in them19:40
Odd_Blokeblackboxsw: Sold.19:49
blackboxswapproved to the man in the yellow hat. awaiting CI19:51
Odd_Blokeblackboxsw: Are you logged in as the bot account? :p19:51
blackboxswummmm... no why every would you say that :)19:51
Odd_BlokeI think it's preferable that it was you and not a rogue Jenkins job. :p19:52
blackboxswtrue story. human blackboxsw just approved19:52
hggdhhi folks. customer has a NFSv3 mount in /etc/fstab. It seems cloud-init runs a 'mount -a' before the network is all set up and, as a result, VM fails to boot (gets stuck in network setup)21:10
hggdhchanging cloud-init.service to state "After=network-online.target" and "Wants=network-online.target21:10
hggdh solves the problem.21:11
hggdh(seen on RHEL 7.8 and 7.9, and OEL 7.8. Probably also affects CentOS 7.[89]21:12
Otanauthey! i am trying to dive into cloud-init and i am not sure if i get it right: is cloud-init baked into debian? so i jsut throw my configuration into /etc/cloud/cloud.cfg.d/*.cfg and on first boot the system does it magic?21:48
powersjOtanaut, cloud-init is generally used when deploying a new cloud instance. Like on AWS, GCP, Azure. However it can also be used locally when deploying VMs. To use it, cloud-init needs to be baked into the image you are using.21:58
=== powersj changed the topic of #cloud-init to: 20.4 (Nov 24) | file a bug: https://bugs.launchpad.net/cloud-init/+filebug | pull-requests: https://git.io/JeVed | meeting minutes: https://goo.gl/mrHdaj | next office hours: Jan 5 17:15 UTC
Otanautpowersj: ah ok but baked as in "installed" is enough, right?22:40
blackboxswOtanaut: yes that should be enough, most distro packaging of cloud-init installs the right startup scripts to make sure cloud-init runs properly during boot.22:49
blackboxswit's testable with lxc if you have it: `lxc launch images:debian/buster deb-10; lxc exec deb-10 apt-get install cloud-init;`22:53

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