| Cookies | Hello, I'm having trouble with the puppet module. It does set my config correctly, but no run is triggered even though I set 'exec' to 'true'. It sets the config and then continues with the next module which in my case is power_state_change and reboots the server. Does the power_state_change have a higher priority than the puppet exec? Here is my | 10:17 |
|---|---|---|
| Cookies | config for reference: https://privatebin.net/?f9c14ac91864ece4#H7y2HF3wkxbKYsMXafjPzyek2PHAqgK1qiCcxR3gSzRV | 10:17 |
| StyXman | my setup is complicated, so please be patient | 11:46 |
| StyXman | we have these test systems that use terraform, terraform-lxc, lxc to boot up containers that run centos7 (yes, old, I know) with cloud-init to set the IPv4 via DHCP for one particular interface | 11:47 |
| StyXman | this stopped working since yesterday, when I upgraded the host (wrong move) from ubuntu 21.04 to 21.10 | 11:47 |
| StyXman | the fact is, it's completely weird because the whole setup is mostly OS independent: | 11:48 |
| StyXman | lxd is installed via snap, and hasn't ben updated in a year or so, terraform and the provider are also installed by hand in the project's dir and didn't change (altho I tried by upgrading to the provider's 1.6 version) and the OS image didn't change at all | 11:49 |
| StyXman | so my question is: how can I debug why cloud-init is deciding not to do _anything_ at boot? | 11:49 |
| StyXman | there's not even a cloudi-init.log file; see https://bugs.launchpad.net/cloud-init/+bug/1948450 | 11:50 |
| ubottu | Launchpad bug 1948450 in cloud-init "cloud-init analize fails miserably if there is no log file" [Undecided, New] | 11:50 |
| StyXman | I just checked this https://cloudinit.readthedocs.io/en/latest/topics/boot.html#generator and all seems fine | 11:50 |
| StyXman | https://dpaste.org/n3DD | 11:51 |
| StyXman | oh | 11:54 |
| StyXman | [root@demo3-node1 ~]# systemctl status cloud-init-local.service | 11:54 |
| StyXman | Failed to get D-Bus connection: No such file or directory | 11:54 |
| StyXman | this is so fsckedup | 11:54 |
| falcojr | Cookies: I'm assuming puppet is already installed (asking because of the install: false)? What version of cloud-init are you running? Can you also post what's in /var/log/cloud-init? cloud-init doesn't capture the output from the puppet agent, so you're not going to see the agent output in the cloud-init logs. | 14:04 |
| Cookies | falcojr yes puppet is already installed in the image. The cloud-init version is 20.4.1-2+deb11u1. The log is here: https://privatebin.net/?3d4cf4e196d47d51#98VVo14YPyLcUWHET5rVh9zD2X3a1bCaebpHjHSD124b It not capturing the output of the puppet agent is annoying :/ is there any way to log this for debugging? | 14:11 |
| falcojr | ahhh, so puppet module got an overhaul in 21.3 | 14:18 |
| falcojr | 20.4 documentation looks like this https://cloudinit.readthedocs.io/en/20.4/topics/modules.html#puppet | 14:18 |
| falcojr | in 20.4 the service automatically gets set to start on boot and the end of the module triggers a "service puppet start" | 14:19 |
| falcojr | I don't think there's a way to foreground the run in 20.4 | 14:20 |
| falcojr | Cookies: ^ | 14:21 |
| Cookies | falcojr oh ok, that explains it :D then I'll have to wait for debian to adapt >=21.3 for bullseye. Will try to find a workaround in the meantime. Thank you very much for your time and helpful information! | 14:23 |
| === tris is now known as empty_string | ||
| === empty_string is now known as tris | ||
| asparagus | hi there | 19:28 |
| asparagus | am trying to configure cloud-config to install puppet agent for ubuntu 20.04.3..does anyone have experience with this? | 19:29 |
| === aaii__ is now known as aaii | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!