deployer failed to detect a hook error

Bug #1578389 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-deployer
New
Undecided
Unassigned

Bug Description

I have a hook error in my deploy, seen by juju status:
$ juju status --format=tabular
[Services]
NAME STATUS EXPOSED CHARM
haproxy unknown false cs:trusty/haproxy-19
landscape-server error false local:xenial/landscape-server-0
postgresql active false cs:trusty/postgresql-41
rabbitmq-server active false cs:xenial/rabbitmq-server-0

[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
haproxy/0 unknown idle 1.25.5 1 54.157.185.1
landscape-server/0 error idle 1.25.5 2 54.80.142.236 hook failed: "install"
postgresql/0 active idle 1.25.5 3 5432/tcp 54.157.228.249 Live master
rabbitmq-server/0 active idle 1.25.5 4 5672/tcp 107.20.88.38 Unit is ready

[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.5 54.163.40.4 i-02fa8a85 xenial arch=amd64 cpu-cores=1 cpu-power=300 mem=3840M root-disk=8192M availability-zone=us-east-1a
1 started 1.25.5 54.157.185.1 i-14699cec trusty arch=amd64 cpu-cores=1 cpu-power=300 mem=3840M root-disk=8192M availability-zone=us-east-1c
2 started 1.25.5 54.80.142.236 i-e497627e xenial arch=amd64 cpu-cores=1 cpu-power=300 mem=3840M root-disk=8192M availability-zone=us-east-1d
3 started 1.25.5 54.157.228.249 i-d3c4be4e trusty arch=amd64 cpu-cores=1 cpu-power=300 mem=3840M root-disk=8192M availability-zone=us-east-1e
4 started 1.25.5 107.20.88.38 i-c8e3934f xenial arch=amd64 cpu-cores=1 cpu-power=300 mem=3840M root-disk=8192M availability-zone=us-east-1a

juju-deployer is still trying to deploy it, though, and happily waiting for "stuff" to happen:
$ grep landscape-server deployer-output.txt
2016-05-04 17:37:39 [DEBUG] deployer.charm: Branching charm lp:landscape-charm/trunk @ xenial/landscape-server
2016-05-04 17:38:17 [INFO] deployer.import: Deploying service landscape-server using local:xenial/landscape-server
2016-05-04 17:39:47 [DEBUG] deployer.import: Service 'landscape-server' does not need any more units added.
2016-05-04 17:41:45 [DEBUG] deployer.env: Delta unit: landscape-server/0 change:pending
2016-05-04 17:41:50 [DEBUG] deployer.env: Delta service: landscape-server change:{u'Err': None, u'Since': u'2016-05-04T20:41:46.354133363Z', u'Current': u'error', u'Version': u'', u'Message': u'hook failed: "install"', u'Data': {u'hook': u'install'}}
2016-05-04 17:41:50 [DEBUG] deployer.env: Delta unit: landscape-server/0 change:pending
2016-05-04 17:41:50 [DEBUG] deployer.env: Delta unit: landscape-server/0 change:pending

Note that it did receive the error, but it didn't stop the deployment. It used to stop.

This is my deployer commnd line:
juju-deployer -Wdv -c xenial-landscape-scalable.yaml -w 120 -u

Full output (so far) attached.

Tags: landscape
Revision history for this message
Andreas Hasenack (ahasenack) wrote :
tags: added: landscape
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

Which version of deployer?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

0.6.4-0ubuntu1 from xenial (yes, I'm also surprised I'm not using my own daily builds).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.