| 2017-04-05 18:26:16 |
Rod Smith |
bug |
|
|
added bug |
| 2017-04-05 18:26:16 |
Rod Smith |
attachment added |
|
/var/log/maas directory tree from the server https://bugs.launchpad.net/bugs/1680197/+attachment/4855576/+files/var-log-maas.tgz |
|
| 2017-04-05 18:32:00 |
Andres Rodriguez |
bug task added |
|
curtin |
|
| 2017-04-05 18:32:10 |
Andres Rodriguez |
maas: status |
New |
Incomplete |
|
| 2017-04-05 18:32:14 |
Andres Rodriguez |
maas: status |
Incomplete |
Invalid |
|
| 2017-04-05 18:54:04 |
Ryan Harper |
curtin: status |
New |
Incomplete |
|
| 2017-04-06 13:32:55 |
Rod Smith |
attachment added |
|
/var/log from ephemeral failed deployment https://bugs.launchpad.net/maas/+bug/1680197/+attachment/4856243/+files/var-log.tgz |
|
| 2017-05-11 14:56:10 |
Andres Rodriguez |
curtin: status |
Incomplete |
Confirmed |
|
| 2017-05-11 15:02:45 |
Scott Moser |
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~bzr470-0ubuntu1~16.04.1)
Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/curtin/block/__init__.py", line 773, in exclusive_open
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/curtin/block/__init__.py", line 773, in exclusive_open
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-0ubuntu1~16.04.1
root@gil:/# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-==================================================
ii maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cert-server 0.2.30-0~74~ubuntu16.04.1 all Ubuntu certification support files for MAAS server
ii maas-cli 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3) |
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~bzr470-0ubuntu1~16.04.1)
Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/curtin/block/__init__.py", line 773, in exclusive_open
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/curtin/block/__init__.py", line 773, in exclusive_open
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-0ubuntu1~16.04.1
root@gil:/# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-==================================================
ii maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cert-server 0.2.30-0~74~ubuntu16.04.1 all Ubuntu certification support files for MAAS server
ii maas-cli 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
Related bugs:
* bug 1666573: transient systemd ordering cycle in boot with overlayroot ver read-only open-iscsi root |
|
| 2017-06-21 12:59:21 |
Jeff Lane |
tags |
|
hwcert-server |
|
| 2017-12-08 18:36:18 |
Scott Moser |
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~bzr470-0ubuntu1~16.04.1)
Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/curtin/block/__init__.py", line 773, in exclusive_open
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/curtin/block/__init__.py", line 773, in exclusive_open
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-0ubuntu1~16.04.1
root@gil:/# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-==================================================
ii maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cert-server 0.2.30-0~74~ubuntu16.04.1 all Ubuntu certification support files for MAAS server
ii maas-cli 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
Related bugs:
* bug 1666573: transient systemd ordering cycle in boot with overlayroot ver read-only open-iscsi root |
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~bzr470-0ubuntu1~16.04.1)
Failed to exclusively open path: /dev/sda1
Traceback (most recent call last):
File "/curtin/curtin/block/__init__.py", line 773, in exclusive_open
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/curtin/block/__init__.py", line 773, in exclusive_open
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-0ubuntu1~16.04.1
root@gil:/# dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-==================================================
ii maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cert-server 0.2.30-0~74~ubuntu16.04.1 all Ubuntu certification support files for MAAS server
ii maas-cli 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.5+bzr5596-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.5+bzr5596-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
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 |
|
| 2020-01-13 20:59:54 |
Jeff Lane |
curtin: status |
Confirmed |
Fix Released |
|
