juju-core

  1. Bug #1450917
  2. Comment #5

Comment 5 for bug 1450917

Revision history for this message
Ian Booth (wallyworld) wrote : Re: deployer on maas 1.7 cannot complete

These lines from the landscape unit log provide the vital clue. If the start hook is not implemented by the charm, the uniter never runs the logic to update the workload status. We expect to see

INFO juju.worker.uniter.operation runhook.go:115 ran "start" hook

But because the above is not there, the vital logic is skipped.

2015-05-02 01:03:44 INFO juju.worker.uniter modes.go:124 found queued "start" hook
2015-05-02 01:03:44 INFO juju.worker.uniter.operation executor.go:66 running operation run start hook
2015-05-02 01:03:44 INFO juju.worker.uniter.operation executor.go:87 preparing operation "run start hook"
2015-05-02 01:03:44 INFO juju.worker.uniter.operation executor.go:87 executing operation "run start hook"
2015-05-02 01:03:44 DEBUG juju.worker.uniter modes.go:31 [AGENT-STATUS] executing running start hook
2015-05-02 01:03:45 INFO juju.worker.uniter.context runner.go:155 skipped "start" hook (not implemented)
2015-05-02 01:03:45 INFO juju.worker.uniter.context context.go:444 handling reboot
2015-05-02 01:03:45 INFO juju.worker.uniter.operation runhook.go:121 skipped "start" hook (missing)
2015-05-02 01:03:45 INFO juju.worker.uniter.operation executor.go:87 committing operation "run start hook"