MAAS deployments of Eoan (pre-release) failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
New
|
Undecided
|
Unassigned |
Bug Description
MAAS deployments of 19.10 (pre-release) used to work, but are now failing, with the following errors logged (as shown in the MAAS web UI's logs tab):
Running command ['umount', '/tmp/tmptn44is
finish: cmd-install/
Traceback (most recent call last):
File "/curtin/
ret = args.func(args)
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
stdout, _ = in_chroot.
File "/curtin/
return subp(*args, **kwargs)
File "/curtin/
return _subp(*args, **kwargs)
File "/curtin/
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmptn44is
Exit code: 18
Reason: -
Stdout: BootCurrent: 0005
Stderr: Could not parse device path: Invalid argument
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmptn44is
Exit code: 18
Reason: -
Stdout: BootCurrent: 0005
Stderr: Could not parse device path: Invalid argument
Stderr: ''
This happens on several nodes on at least two MAAS servers (both running MAAS 2.6.0-7802-
Deployment of earlier versions of Ubuntu is fine; it's only recent Eoan releases that have this problem.