lander-jenkins/0: agent-state: error agent-state-info: 'hook failed: "install"'

Bug #1290289 reported by Vincent Ladeuil
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu CI Services
Confirmed
High
Francis Ginther

Bug Description

I can't make sense of what is happening so filing a bug first with the info I can collect before re-trying the install.

ubuntu@juju-hp-machine-5:/var/log/juju$ more machine-5.log
2014-03-10 09:17:55 INFO juju.cmd.jujud machine.go:118 machine agent machine-5 s
tart (1.17.4-precise-amd64)
2014-03-10 09:17:55 DEBUG juju.agent agent.go:253 Reading agent config, format:
format 1.16
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "api"
2014-03-10 09:17:55 INFO juju apiclient.go:113 state/api: dialing "wss://10.0.0.
214:17070/"
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "termination"
2014-03-10 09:17:55 INFO juju apiclient.go:123 state/api: connection established
2014-03-10 09:17:55 DEBUG juju.agent agent.go:394 writing configuration file
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "upgrader"
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "upgrade-steps"
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "machiner"
2014-03-10 09:17:55 INFO juju.cmd.jujud machine.go:433 Upgrade to 1.17.4-precise
-amd64 already completed.
2014-03-10 09:17:55 INFO juju.cmd.jujud machine.go:420 Upgrade to 1.17.4-precise
-amd64 completed.
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "logger"
2014-03-10 09:17:55 DEBUG juju.worker.logger logger.go:35 initial log config: "<
root>=DEBUG"
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "machineenvironmentwor
ker"
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "rsyslog"
2014-03-10 09:17:55 DEBUG juju.worker.logger logger.go:60 logger setup
2014-03-10 09:17:55 DEBUG juju.worker.machineenvironment machineenvironmentworke
r.go:70 write system files: true
2014-03-10 09:17:55 INFO juju runner.go:262 worker: start "authenticationworker"
2014-03-10 09:17:55 INFO juju.worker.machiner machiner.go:88 setting addresses f
or machine-5 to ["10.0.0.219" "fe80::f816:3eff:fe11:98e8"]
2014-03-10 09:17:55 DEBUG juju.worker.logger logger.go:45 reconfiguring logging
from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
2014-03-10 09:17:55 WARNING juju.cmd.jujud machine.go:266 determining kvm suppor
t: exit status 1
no kvm containers possible

ubuntu@juju-hp-machine-5:/var/log/juju$ more unit-lander-jenkins-0.log
2014-03-10 09:17:56 DEBUG juju.agent agent.go:253 Reading agent config, format:
format 1.16
2014-03-10 09:17:56 INFO juju.jujud unit.go:75 unit agent unit-lander-jenkins-0
start (1.17.4-precise-amd64)
2014-03-10 09:17:56 INFO juju runner.go:262 worker: start "api"
2014-03-10 09:17:56 INFO juju apiclient.go:113 state/api: dialing "wss://10.0.0.
214:17070/"
2014-03-10 09:17:56 INFO juju apiclient.go:123 state/api: connection established
2014-03-10 09:17:56 DEBUG juju.agent agent.go:394 writing configuration file
2014-03-10 09:17:57 INFO juju runner.go:262 worker: start "upgrader"
2014-03-10 09:17:57 INFO juju runner.go:262 worker: start "logger"
2014-03-10 09:17:57 DEBUG juju.worker.logger logger.go:35 initial log config: "<
root>=DEBUG"
2014-03-10 09:17:57 INFO juju runner.go:262 worker: start "uniter"
2014-03-10 09:17:57 DEBUG juju.worker.logger logger.go:60 logger setup
2014-03-10 09:17:57 INFO juju runner.go:262 worker: start "rsyslog"
2014-03-10 09:17:57 DEBUG juju.worker.logger logger.go:45 reconfiguring logging
from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
2014-03-10 09:18:05 INFO juju-log Configuring source of jenkins as lts
2014-03-10 09:19:05 INFO install gpg: no valid OpenPGP data found.
2014-03-10 09:19:05 ERROR juju.worker.uniter uniter.go:480 hook failed: exit sta
tus 2

Tags: airline
Revision history for this message
Vincent Ladeuil (vila) wrote :

$ juju terminate-machine --force 5
$ ./juju-deployer/deploy.py

Results in the same error, needs more investigation.

Revision history for this message
Vincent Ladeuil (vila) wrote :

Third install after merging trunk @ revno 345 + fix from https://code.launchpad.net/~vila/ubuntu-ci-services-itself/12897942-sha1-payload/+merge/210174 did the trick.

I see nothing relevant in the additional revisions merged from trunk so we may have some race here.

Assigning to Francis for feedback/guidance, I have no idea where to look to fix or reproduce.

Changed in ubuntu-ci-services-itself:
assignee: nobody → Francis Ginther (fginther)
milestone: none → backlog
milestone: backlog → phase-0
Revision history for this message
Francis Ginther (fginther) wrote :

Vincent,

The failure occurred at the point where the packages are retrieved via apt. This includes a fetch from jenkins-ci.org. Possibly there was an issue contacting the remote site. This is on the wishlist to resolve and we have a backup solution (the jenkins deb file can be passed as a local file when deploying): https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1285302

Revision history for this message
Andy Doan (doanac) wrote :

If this doesn't happen to anyone in the next couple of days, I think we should mark this as a dup and move on. Sound okay?

Revision history for this message
Vincent Ladeuil (vila) wrote :

> I think we should mark this as a dup and move on. Sound okay?

Yup, almost did that yesterday (can't remember why I didn't, probably got interrupted), will just do now ;)

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.