/srv/irclogs.ubuntu.com/2023/05/18/#cloud-init.txt

bdeandoes anyone have an experience with growpart on Oracle Linux 7? when I run `growpart` myself interactively it works. but it never seems to run from cloud-init and I'm not sure how to tell what's going on. there's nothing in the logs, it goes right from write-files to resizefs and nothing from growpart14:08
minimalbdean: have you debugging enabled for cloud-init logs?14:10
minimalif so then there should be several lines written to /var/log/cloud-init.log by cc_growpart showing what is going on14:10
minimalalso are there any entries relating to growpart in your user-data or in /etc/cloud/cloud.cfg or /etc/cloud/cloud.cfg.d/* ?14:12
bdeanthere are logs that say DEBUG, but I see nothing from cc_growpart14:12
bdeanI have a file in cloud.cfg.d14:12
minimalwhat does it say about growpart?14:13
bdeannot sure how to do multiline in irc, but it's `growpart: { mode: growpart, devices: ['/'], ignore_growroot_disabled: true }`14:14
minimalalso what about:   grep "Running module growpart" /var/log/cloud-init.log ?14:14
bdeansure ...14:15
bdeanjust this:14:17
bdean2023-05-18 14:06:26,086 - util.py[DEBUG]: Reading from /etc/cloud/cloud.cfg.d/06_growpart.cfg (quiet=False)14:17
bdean2023-05-18 14:06:26,086 - util.py[DEBUG]: Read 97 bytes from /etc/cloud/cloud.cfg.d/06_growpart.cfg14:17
bdeanand that's all14:17
bdeanthat's from `grep growpart /var/log/cloud-init.log`14:18
minimalso then it doesn't seem to be running the module14:18
bdeanyeah, but why?14:18
minimaltry:   grep "Skipping modules" /var/log/cloud-init.log14:19
bdeanit's in the list in /etc/cloud/cloud.cfg too14:19
bdeancloud_init_modules:14:19
bdean - disk_setup14:19
bdean - migrator14:19
bdean - bootcmd14:19
bdean - write-files14:19
bdean - growpart14:20
bdean - resizefs14:20
bdean - set_hostname14:20
bdean - update_hostname14:20
bdean - update_etc_hosts14:20
bdean - rsyslog14:20
bdean - users-groups14:20
bdean - ssh14:20
bdeanSkipping set-hostname, Skipping module named bootcmd, Skipping module named disable-ec2-metadata14:21
minimaldoes "cloud_init_modules" appear in any other file inside /etc/cloud/ ?14:22
minimalrgrep "cloud_init_modules" /etc/cloud/*14:22
bdeansorry, one second, was in a meeting14:32
bdeanwe've got a winner! /etc/cloud/cloud.cfg.d/99_oci_cloud.cfg14:34
bdeanf-ing OCI14:35
bdean# The growpart module is disabled by default. To enable automatic boot volume resizing, uncomment14:35
bdean# the below entry for '- growpart' and reboot. All the dependent packages for the growpart14:35
bdean# module to work such as cloud-utils-growpart and gdisk are already included in the image.14:35
bdean#- growpart14:35
bdeanthat makes zero sense to me. Why would they make images where you have to do extra steps just to resize the root volume14:37
minimalbdean: and that 99_oci_cloud.cfg file has a "cloud_init_modules" section? assuming it does then that overrides the list in /etc/cloud.cfg14:37
bdeanyeah14:37
bdeanit's like a whole copy of /etc/cloud.cfg with various bits commented out14:37
bdeanI'm already making a custom image (their version of an AMI) so I can just use sed on this to uncomment it, but it's just annoying14:39
bdeanthanks for the help though14:39
minimalperhaps they want you to manually use oci-growfs?14:41
bdeanI mean .. they certainly don't seem to mind requiring manual steps to get things going14:41
minimalyeah it makes no sense14:42
bdeanI'm doing a diff to the standard cloud.cfg to see what else they changed, this one is fun:14:42
bdean#disable_vmware_customization: false14:42
bdeangotta comment out it being false14:42
bdeanoh well14:43
bdeanthanks again14:43
minimalwhy? aren't you using the Oracle datasource?14:43
bdeanit adds that, yes14:43
minimalin why case why would a VMware datasource setting be relevant?14:43
minimals/why/which/14:44
bdeanmaybe they don't know what they're doing14:44
minimalbdean: they're trying to save you from yourself ;-)14:48
bdean;_;14:48
minimalany help to figure out why a single test is failing for #4128? I can't see what the problem actually is15:25
falcojrminimal: I'll take a look19:06
minimalThanks. I found a few other places in testcases to correct modules names (though none of those affect testcase) so I'll be updating the PR shortly19:24
falcojrminimal: You can just remove this line https://github.com/canonical/cloud-init/blob/main/tests/integration_tests/modules/test_combined.py/#L22819:37
falcojrthe test itself was wrong...it was expecting apt-pipelining to have been run even though it never should have19:38
falcojrbut used the name apt_pipelining, which is why the test passed. Since you changed the name of the module, it failed as it now matched correctly19:38
minimalah, that's why I didn't spot the issue, was staring intently at the code with my changes, not the original code, lol19:40
meenahttps://github.com/canonical/cloud-init/pull/412922:34
-ubottu:#cloud-init- Pull 4129 in canonical/cloud-init "BSD: simplify finding MBR partitions" [Open]22:34
meenacan soeone re-run tests here? https://github.com/canonical/cloud-init/pull/2146 — some of them have been cancelled, no idea why22:44
-ubottu:#cloud-init- Pull 2146 in canonical/cloud-init "FreeBSD fix parsing of mount and mount options" [Open]22:44
meenawow, i just realized: Python stuff gets installed without junk like tests.22:52
meenacan somebody at NPM please cop on.22:52

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