** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: maas
Milestone: next => 2.8.0b1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volume size pod zfs
Luis,
This did not make it into 2.7 but will be part of 2.8. If you want to
work around the issue yourself of test, you can patch the Virsh Pod
driver with the diff from the linked branch.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry for the late response..
Is this included in 2.7 ? I wasn't able to test the files on my current
installation
thanks
Luis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volum
** Changed in: maas
Status: In Progress => Fix Committed
** Changed in: maas
Milestone: None => next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volume size pod zfs
To
I'm out of station until Feb 3rd. I'll check when I arrive
On Thu, Jan 23, 2020, 4:20 AM Newell Jensen
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/
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-rack
** Merge proposal linked:
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/377967
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volume size pod zfs
To manage notifi
Libvirt does 1k alignment, that was what added th 512, Maas seems to request
just 90. This value isn't ok, as the alignment is missing there.
The interface in libvirt is dumb, as it doesn't know the shifts - that would be
whoever created the zpool (or needs a lot of extra probing). Unfort
FYI: I'm assuming this example data was from a 9G test that became
900512 bytes requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volume size pod zfs
To manage notificatio
Thanks for your steps to create your pool in your case.
With that I recreated the issue:
$ sudo zpool create zpool -m /data/zpool mirror /dev/nvme0n1p3 /dev/nvme0n1p4
$ virsh pool-define-as --name zpool --source-name zpool --type zfs
$ virsh pool-start zpool
$ virsh pool-autostart zpool
Yours is
On Sat, Jan 18, 2020 at 12:37 AM Newell Jensen
wrote:
> $ virsh dumpxml
>
root@node35:~# virsh dumpxml testers
testers
ad6b59c9-76b5-4481-a0bb-dc896782f27e
1048576
1048576
1
hvm
destroy
restart
restart
Maybe one last thing, is that after I tried to create the machine in MAAS
and gave the error, it is not shown in MAAS composed machines, but it is
shown in virsh list --all, so I have to manually delete it
On Sat, Jan 18, 2020 at 9:15 AM Luis Alfonso Rodríguez Aragonés <
larago...@gmail.com> wrote
$ virsh dumpxml
$ virsh pool-dumpxml
$ /sbin/zfs create -s -V 8789063K zpool/52a7cb41-4241-4336-b624-1f930ff398ed
Christian, if there are any other specific commands that you know that
Luis should execute since he has his setup still, please let him know.
--
You received this bug notification
Yes.. what should I do?
On Fri, Jan 17, 2020 at 2:50 AM Newell Jensen
wrote:
> Luis,
>
> Do you still happen to have your zfs setup to get the requested
> information from (XMLs etc)? My setup was deleted and I have been busy
> with other higher priority items. Might take me a bit to get to th
Luis,
Do you still happen to have your zfs setup to get the requested
information from (XMLs etc)? My setup was deleted and I have been busy
with other higher priority items. Might take me a bit to get to this if
you don't have it.
Cheers
--
You received this bug notification because you are
Note we can derive that allocation was not set as we see "-s" (capacity
!= allocation), but we don't see -o so allocation is "0" (likely unset).
330 if (vol->target.capacity != vol->target.allocation) {
331 virCommandAddArg(cmd, "-s");
Please note that from MAAS you can't specify the size in KB, only in GB.
the command being executed is having the argument in KB.. And that
translation from 8GB to 8789063K is not a multiple of the block size of
8. THis is the command that is being executed from libvirt I suppose
(taken from the l
Ack to bryce question for details, and in addition a list of commands to
create (if any) and dumpxml of the XML that defines the zfsstorage pool
/ volumes would be great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Newell, what are the args / steps you're using to repro the issue in
libvirt?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Ti
I was able to reproduce this. As MAAS only talks to libvirt via ssh,
giving it the parameters to create a VM, and the fact that this is not
an issue with other storage backends, I believe this is a libvirt bug as
libvirt is ultimately calling the command to create the volume storage.
--
You rece
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858201
Title:
volume size pod zfs
To manage notifications about this bug
21 matches
Mail list logo
