[Bug 1847058] Re: MAAS deployment failed with vgchange command
Disk erasure performed on bavor, and it has made bavor back to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
To answer One of Dans questions from comment #4. The maas server uses the images from maas.io. As Sam mentioned the problem originated last week. The systems were installed with "Bionic" I believe? I'll look into the maas-disk erasure feature. thanks Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
The workaround proposed by Ryan worked. Maas Disk Erase appears to have fixed the problem, i'll ensure to do that on any of the affected systems. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
** Changed in: curtin (Ubuntu) Importance: Undecided => Medium ** Changed in: curtin (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Curtin hasn't made any changes here; but I suspect the workload on the target machine which created the thin lv's has left metadata that curtin doesn't yet know how to clear. As a workaround for now, you can use the MAAS disk-erasure to clear the volumes before attempting to deploy. https://maas.io/docs/disk-erasure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
BTW from our test log on the Jenkins server, it looks like this issue first occurs in 3 days 19 hrs before. And this is blocking the kernel SRU testing to some extent. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Hi, thanks for the reply, I tried to re-sync the Eoan image today and deploy it on a node that does not work before (bavor), it's still failing, but the error message is a bit different: curtin.util.ProcessExecutionError: Unexpected error while running command. Command: ['vgscan', '--mknodes'] Exit code: 5 Reason: - Stdout: Reading all physical volumes. This may take a while... Found volume group "vg_459" using metadata type lvm2 Stderr: Command failed with status code 5. Please find the attachment for the output from maas. ** Attachment added: "bavor-eoan.log" https://bugs.launchpad.net/maas/+bug/1847058/+attachment/5295736/+files/bavor-eoan.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Thanks for the bug report! It looks to me like the problem here is that the lvm2 package only Suggests (up to disco) thin-provisioning-tools (up to disco), which is what provides the thin_check binary. I would expect this to be resolved in recent eoan images (as thin- provisioning-tools is now a Recommends of ; can you confirm how recent the eoan images being used for testing are? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Sorry, that second paragraph should be: I would expect this to be resolved in recent eoan images (as thin- provisioning-tools is now a Recommends of lvm2 and therefore pulled in during image build); can you confirm how recent the eoan images being used for testing are? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
** Changed in: maas Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Looks like this deployment failure is not happening on all the nodes, some of them still can be deployed with any issue. It's affecting: * bavor (Eoan) * rizzo (B, D) * s2lp6g001 s390x KVM (X, E) * s2lp6g003 s390x KVM (D) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
** Description changed: Issue found on our MAAS server, MAAS version: 2.6.1 (7832-g17912cdc9-0ubuntu1~18.04.1) + Trying to deploy Bionic on an AMD64 bare metal. + Deployment log shows it has failed with: - curtin.util.ProcessExecutionError: Unexpected error while running command. - Command: ['vgchange', '--activate=y'] - Exit code: 5 - Reason: - - Stdout: 0 logical volume(s) in volume group "vg_459" now active - Stderr: /usr/sbin/thin_check: execvp failed: No such file or directory - Check of pool vg_459/pool_459 failed (status:2). Manual repair required! - /usr/sbin/thin_check: execvp failed: No such file or directory + curtin.util.ProcessExecutionError: Unexpected error while running command. + Command: ['vgchange', '--activate=y'] + Exit code: 5 + Reason: - + Stdout: 0 logical volume(s) in volume group "vg_459" now active + Stderr: /usr/sbin/thin_check: execvp failed: No such file or directory + Check of pool vg_459/pool_459 failed (status:2). Manual repair required! + /usr/sbin/thin_check: execvp failed: No such file or directory Please find the attachment for the complete deployment log from MAAS UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
