thank you for that. i am tempted to close out the multipath package task; and open an lvm package task.
i'm not sure if we allow reusing existing lvms, if we do, that would be also an intersting datapoint test case. normally lvm commands do create udev cookies, and trigger udev to settle with a timeout. I do wonder, if curtin should be doing something more clever here. Like lookaside at all the prober data and try to disable that behaviour and instead do udev triggers / waiting by itself possibly with larger timeouts. or if we can somehow "speed things up" by deactivating all the multipaths and all the "unused" drives not selected for the installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878041 Title: installation fails creating user on large multipath system - multipathd show command times out in curtin log with 163 paths To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1878041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
