In terms of understanding when this was fixed for what users/versions. Assuming that MAAS is copying the curtin version from the server, to the deployed client, which I think is the case, you need to get an updated Curtin to the MAAS server.
The bug was fix released into curtin 20.1-20-g1304d3ea-0ubuntu1 in August 2020. Curtin has not been updated in bionic itself since May 2020 (20.1-2-g42a9667f-0ubuntu1~18.04.1). So no fix there. MAAS 2.7 PPA (https://launchpad.net/~maas/+archive/ubuntu/2.7) - No fix MAAS 2.8 PPA (https://launchpad.net/~maas/+archive/ubuntu/2.8) - Fixed in 21.2-0ubuntu1~18.04.1 uploaded 1st March 2021 - first and only curtin upload MAAS 2.9 PPA (https://launchpad.net/~maas/+archive/ubuntu/2.9) - FIxed in 21.2-0ubuntu1~20.04.1 uploaded 16th February 2021 - first and only curtin upload MAAS 2.8 was released 24 June 2020 MAAS 2.9 was released December 2020 MAAS 3.0 was released 6 July 2021 [Note: only supports 20.04] So seems like there was a gap from August 2020 to December 2020 where the fix possibly wasn't available to MAAS users at all? And then until March 2021 it wasn't available to MAAS 2.8 users. However I don't know what version of MAAS, if any, is consuming curtin as a snap. And whether that applies to both DEB and SNAP installations of those given versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892242 Title: Curtin doesn't handle type:mount entries without 'path' element To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1892242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
