Deployment Failed -- Failed to get installation results
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Raphaël Badin |
Bug Description
While deploying OpenStack, we had 3 failures this past couple of days caused by servers that failed to deploy as result of failing to get the installation results.
From console.txt:
2015-02-18 06:49:03,108 [DEBUG] deployer.env: Delta unit: ceph/2 change:installed
2015-02-18 06:49:08,108 [DEBUG] deployer.env: Delta unit: ceph/2 change:started
2015-02-18 06:49:28,113 [DEBUG] deployer.env: Delta unit: rabbitmq-server/0 change:installed
2015-02-18 06:49:43,115 [DEBUG] deployer.env: Delta unit: mongodb/0 change:installed
2015-02-18 06:50:08,119 [DEBUG] deployer.env: Delta unit: mongodb/0 change:started
2015-02-18 06:53:18,146 [DEBUG] deployer.env: Delta unit: keystone/0 change:installed
2015-02-18 06:53:53,151 [DEBUG] deployer.env: Delta unit: heat/0 change:installed
2015-02-18 06:53:58,152 [DEBUG] deployer.env: Delta unit: heat/0 change:started
2015-02-18 06:54:03,171 [DEBUG] deployer.env: Delta unit: keystone/0 change:started
2015-02-18 06:55:48,169 [DEBUG] deployer.env: Delta unit: ceilometer/0 change:installed
2015-02-18 06:56:08,172 [DEBUG] deployer.env: Delta unit: ceilometer/0 change:started
2015-02-18 06:56:13,175 [DEBUG] deployer.env: Delta unit: rabbitmq-server/0 change:started
2015-02-18 07:52:40,339 [DEBUG] deployer.env: Connecting to environment...
2015-02-18 07:52:41,771 [DEBUG] deployer.env: Connected to environment
2015-02-18 07:52:41,773 [ERROR] deployer.import: Reached deployment timeout.. exiting
2015-02-18 07:52:41,774 [ERROR] oil_ci.
Traceback (most recent call last):
File "/usr/lib/
debug=True, verbose=True)
File "/usr/lib/
importer.
File "/usr/lib/
self.
File "/usr/lib/
raise ErrorExit()
ErrorExit
2015-02-18 07:52:41,793 [INFO] oil_ci.
+ rc=1
+ echo 'Deployment returned: 1'
Deployment returned: 1
From juju_status.yaml:
'2':
agent-state: pending
containers:
2/lxc/0:
series: trusty
2/lxc/1:
series: trusty
dns-name: hayward-63.oil
hardware: arch=amd64 cpu-cores=8 mem=65536M tags=hw-
instance-id: /MAAS/api/
series: trusty
From maas logs:
ubuntu@
.....
Feb 18 06:27:29 maas-trusty-
Feb 18 06:27:35 maas-trusty-
Feb 18 06:27:36 maas-trusty-
Feb 18 06:28:02 maas-trusty-
Feb 18 06:31:44 maas-trusty-
Feb 18 06:31:44 maas-trusty-
Feb 18 06:36:31 maas-trusty-
Related branches
- Blake Rouse (community): Approve
-
Diff: 14 lines (+3/-1)1 file modifiedsrc/metadataserver/api.py (+3/-1)
Changed in maas: | |
status: | Triaged → Incomplete |
Changed in maas: | |
status: | Incomplete → Fix Committed |
milestone: | next → 1.8.0 |
assignee: | nobody → Raphaël Badin (rvb) |
Changed in maas: | |
status: | Fix Committed → Fix Released |
This means the installation failed. This looks to be doing the incorrect behavior as it should mark the node as failed deployment not marking it broken.
This actually means the installation of curtin failed on the node. Can you check the installation results output for that node to get the actual error for why the node failed to install.