| === blackboxsw changed the topic of #cloud-init to: Expected upstream 24.2 release 06/05| 24.1 Released 02/29 | File bug: https://github.com/canonical/cloud-init/issues/new/choose | PRs: https://git.io/JeVed | release schedule: https://discourse.ubuntu.com/t/2024-cloud-init-release-schedule/41679 | ||
| === cpaelzer_ is now known as cpaelzer | ||
| blackboxsw | falcojr: focal/jammy/mantic daily builds are not building. I was going to clean those up to get some updated test runs done. | 16:16 |
|---|---|---|
| blackboxsw | minor PR for growpart integration test fixes due to changed logging. (fixes lxd_vm test issues). | 20:42 |
| blackboxsw | https://github.com/canonical/cloud-init/pull/5357 | 20:42 |
| -ubottu:#cloud-init- Pull 5357 in canonical/cloud-init "daily build recipe fix (mantic): new-upstream-snapshot to resolve merge conflicts with tip of main" [Open] | 20:42 | |
| blackboxsw | https://github.com/canonical/cloud-init/pull/5360 rather | 20:42 |
| -ubottu:#cloud-init- Pull 5360 in canonical/cloud-init "tests: fix expect logging from growpart on devent with partition" [Open] | 20:42 | |
| blackboxsw | I haven't dug into the 27 errors on lxd_containers yet | 20:44 |
| blackboxsw | I haven't dug into the 27 errors on lxd_containers yet but also looks growpart related | 20:44 |
| blackboxsw | both diskdev and partition in growpart failure modes are set to None, breaking the growpart --dry-run command | 20:48 |
| blackboxsw | the issue seems to be an assumption that zpool cmd exists in the image. which it doesn't and we get a command failure and an unset disk or partition | 20:53 |
| blackboxsw | so by default, our zfs-filesystem in containers won't have permissions to exec zpool from inside the LXC container. This'll prevent us from introspecting the zfs volume with zpool. We need a better fallback here, even if we also perform a subp.which("zpool") first there is still a default on containers that the zpool cmd will get a perms error | 21:21 |
| blackboxsw | hrm also the commit e520c944e9792d04ac5881f660c61d9ad27a1989 exits early with a quick return on the first zfs-based partition it tries to resize. This could mean we also skip other partitions which may need a resize on the sytsem | 22:50 |
| minimal | blackboxsw: doesn't cc_growpart only grow the rootfs partition? | 23:49 |
| minimal | and it expects the partition holding the rootfs to be the last partition, is it only grows (i.e. extends the end of it) it | 23:50 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!