[03:37] <holman> meena: gotcha, thanks for the heads up
[08:25] <holman> didn't get to it today, and I won't have a chance to look at it until tomorrow, sorry
[08:26] <holman> I've got desert and caves to explore :D
[08:27] <holman> meena: I got as far as checking that the growpart integration test still passes
[08:28] <holman> But didn't look at the unit tests yet
[08:28] <holman> s/tomorrow/Monday/
[08:29] <holman> minimal: also haven't had a chance to get a review on your pr, but it's been on my mind
[08:36] <meena> aye. i'll go dig thru kernel code then
[08:39] <holman> happy digging o/
[20:49] <daniel_> Hello! When i run "lxc launch ubuntu:jammy experiment" I can create a container with no problem. When I add --config=user..user-data="$(cat myfile.yaml)"  the cloud-init fails due to zpool issue. Looks like the zfsutils-linux package isn't available. If I install it, I cannot run "zpool status" as I "must execute as root", despite shelling into the container as root. Any ideas as to what's going on here?
[20:49] <daniel_> here's the warning msg:
[20:49] <daniel_> Unable to get zpool status of default: Unexpected error while running command.
[20:49] <daniel_> Command: ['zpool', 'status', 'default']
[20:49] <daniel_> Exit code: -
[20:49] <daniel_> Reason: [Errno 2] No such file or directory: b'zpool'
[20:50] <daniel_> --- and ---
[20:50] <daniel_> root@WgClient:~# sudo zpool status
[20:50] <daniel_> Permission denied the ZFS utilities must be run as root.
[20:51] <falcojr> daniel_: anything in the user data that could possibly be related?
[20:54] <daniel_> @falcojr - no - If i only have the #cloud-config header, and the update/upgrade packages and reboot if required, it still occurs
[20:54] <daniel_> cloud-init version: /usr/bin/cloud-init 23.4.4-0ubuntu0~22.04.1
[20:55] <daniel_> lxd version 5.21.1 LTS
[20:55] <daniel_> current yaml file for testing:
[20:55] <daniel_> #cloud-config
[20:55] <daniel_> package_update: true
[20:55] <daniel_> package_upgrade: true
[20:55] <daniel_> package_reboot_if_required: true
[20:56] <falcojr> not sure...you may have more luck in the #lxd channel
[20:57] <daniel_> Fair enough - I am not quite sure where this issue actually lies, with lxd or cloud-init so I thought I'd start by asking here :) thanks for your time