Comment 21 for bug 1858201

I'm out of station until Feb 3rd. I'll check when I arrive

On Thu, Jan 23, 2020, 4:20 AM Newell Jensen <email address hidden>
wrote:

> Luis,
>
> If you still have your zfs setup, could you please test the linked
> branch? You would only need to update /usr/lib/python3/dist-
> packages/provisioningserver/drivers/pod/virsh.py on your MAAS host with
> the changes and then restart your rack controller with:
>
> $ sudo systemctl restart maas-rackd
>
> This branch lines up the zfs vol-create-as call to MiB, which is what
> seems that libvirt wants.
>
>
> Thanks.
>
> ** Changed in: maas
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1858201
>
> Title:
> volume size pod zfs
>
> Status in MAAS:
> In Progress
> Status in libvirt package in Ubuntu:
> Invalid
>
> Bug description:
> I am trying to create a pod on a MAAS node that has virsh installed,
> I added a specific ZFS storage pool
>
> And when trying to create the pod I see the following error on
> /var/log/syslog
>
> Jan 03 18:13:00 node34 libvirtd[3340]: 2020-01-03 12:43:00.310+0000:
> 3341: error : virCommandWait:2601 : internal error: Child process
> (/sbin/zfs create -s -V 8789063K
> zpool/52a7cb41-4241-4336-b624-1f930ff398ed) unexpected exit status 1:
> cannot create 'zpool/52a7cb41-4241-4336-b624-1f930ff398ed': volume
> size must be a multiple of volume block size
>
>
> Any setting for the volume size in GB doesn't match the 8K volume block
> that ZS requires
>
>
> On MAAS while executing the "Create Pod" button I get the following
> error:
>
> Add another device
> Pod unable to compose machine: Unable to compose machine because:
> Failed talking to pod: Start tag expected, '<' not found, line 1, column 1
> (<string>, line 1)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1858201/+subscriptions
>