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
