jgomo3 | holmanb: Hey! That is a really handy module! Thank you very much! | 00:07 |
---|---|---|
holmanb | jgomo3: No problem, good luck :) | 01:40 |
=== jmcgnh_ is now known as jmcgnh | ||
=== raekye6 is now known as raekye | ||
=== danieli6 is now known as danieli | ||
=== falcojr3 is now known as falcojr | ||
=== EugenMayer5 is now known as EugenMayer | ||
aciba | I have created this PR https://github.com/canonical/cloud-init/pull/1461 to fix https://launchpad.net/~cloud-init-dev/+archive/ubuntu/daily/+build/23756305 | 11:29 |
ubottu | Pull 1461 in canonical/cloud-init "Fix test to pass with older pytest." [Open] | 11:29 |
blackboxsw | /mode #cloud-init +o holmanb | 14:03 |
ryland | Hi everyone. I have a weird cloud-init behaviour on RHEL8 (21.1.15.el8). I am deploying a VM in vSphere 7.0.3. I created the extraconfig guestinfo.userdata, its visible in the advanced vm config and i created guestinfo.userdata.encoding entry. Inside the vm, I can get the correct configuration via vmware-rpctool (vmware-rpctool 'info-get | 18:16 |
ryland | guestinfo.userdata' | base64 -d | gzip -d). When I put the decrypted config into /var/lib/cloud/instance/cloud-config.txt and run the module manually, it works fine. So it seems the config is correct. | 18:16 |
ryland | Is there a way that I can check if cloud-init can read the information from the guestinfo config? I am not quite sure i am interpreting the logs right | 18:17 |
ryland | I can see the following output in the cloud-init-output.log: "Cloud-init v. 21.1-15.el8 finished at Wed, 18 May 2022 17:38:09 +0000. Datasource DataSourceOVF [seed=vmware-tools]" | 18:20 |
ryland | I guess that means it reads from the right source | 18:21 |
ryland | The module that I have trouble with, is the cc_rh_subscription module. Even though i have the correct config, it seems to not execute on that | 18:23 |
blackboxsw | ryland: `sudo cloudinit query userdata` will tell you what cloud-init officially saw from the datasource | 18:24 |
blackboxsw | ryland: `sudo cloudinit devel schema --system --annotate` will till you if cloud-init thinks the userdata format provided to it is valid or not | 18:25 |
blackboxsw | those commands on your system prior to your manual replacement of /var/lib/cloud/instance/cloud-config.txt | 18:26 |
blackboxsw | `sudo cloudinit query --all` gives you and overview of all instance data (metadata, vendordata merged_cfg on disk etc) if you are poking around at what a datasource provides to cloud-init | 18:27 |
ryland | blackboxsw: thank you, that is very helpful. let me redeploy and run the commands and see what i get | 18:27 |
blackboxsw | +1 ryland and `cloud-init analyze show` should tell you whether it ran the cc_rh_subscription module. `cloud-init status --long` will tell you if tracebacks or errors were encountered during initial system config or boot | 18:29 |
ryland | blackboxsw: Thank you so much! Let me put that in my notes and run the commands, I hope i will then have a clearer picture of whats going on | 18:38 |
ryland | blackboxsw: well, that clears it up nicely. the "cloud-init query userdata" already shows nothing | 18:55 |
ryland | so i think it is save to say that it does not "see" the data that is in the extra vm config | 18:55 |
ryland | the datasource_list is OVF, VMWare, None. In that order. That seems about right | 18:57 |
blackboxsw | Thanks for going through the cloud-init upstream 22.2 release cut holmanb, aciba and falcojr. Thanks too minimal(Alpine), esposem(RHEL/CentOS) and otubo(RHEL-CentOS) for your distro work and validation prior to this release. | 20:19 |
blackboxsw | I'm going through the process of uploading 22.2 to Ubuntu Kinetic now as it looks like holmanb's upstream snapshot sync into /ubuntu/devel branch contains all we need for release. | 20:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!