Zesty deployments failing sporadically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
curtin |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm encountering the following deployment failure (as reported in the web UI's "installation output") on about 1 in 4 deployments on two systems, one running MAAS 2.1.4 and the other MAAS 2.1.5:
curtin: Installation started. (0.1.0~
Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/
fd = os.open(path, os.O_RDWR | os.O_EXCL)
OSError: [Errno 16] Device or resource busy: '/dev/sda1'
Device holders with exclusive access: []
Device mounts: []
[Errno 16] Device or resource busy: '/dev/sda1'
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/
fd = os.open(path, os.O_RDWR | os.O_EXCL)
OSError: [Errno 16] Device or resource busy: '/dev/sda1'
Device holders with exclusive access: []
Device mounts: []
[Errno 16] Device or resource busy: '/dev/sda1'
Stderr: ''
I'm attaching the /var/log/maas directory tree from the 2.1.5 system. Here's the version information from the 2.1.5 installation:
dpkg -s maas | grep Version
Version: 2.1.5+bzr5596-
root@gil:/# dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.1.5+bzr5596-
ii maas-cert-server 0.2.30-
ii maas-cli 2.1.5+bzr5596-
un maas-cluster-
ii maas-common 2.1.5+bzr5596-
ii maas-dhcp 2.1.5+bzr5596-
ii maas-dns 2.1.5+bzr5596-
ii maas-proxy 2.1.5+bzr5596-
ii maas-rack-
ii maas-region-api 2.1.5+bzr5596-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.1.5+bzr5596-
ii python3-maas-client 2.1.5+bzr5596-
ii python3-
Related bugs:
* bug 1666573: transient systemd ordering cycle in boot with overlayroot ver read-only open-iscsi root
* bug 1723183: transient systemd ordering issue when using overlayroot
tags: | added: hwcert-server |
This seems like a curtin bug (and may even be an issue with zesty itself).