units newly added to juju 1.25 service are failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I'm working on adding capacity to a production OpenStack cloud, which is currently running Juju 1.25.13, having been upgraded from 1.24.7 a week or so ago. I believe these may be the first newly added units since the Juju upgrade.
Here's the current tabular status for the service (Canonical-only link: https:/
The service had 56 units before I started and now has 58, both of which are behaving as follows.
Newly added units are repeatedly running hooks and logging the following message at the end:
ERROR juju.worker.
And here's a snippet of juju status-history:
TIME TYPE STATUS MESSAGE
29 Jan 2018 22:44:31Z workload unknown Waiting for agent initialization to finish
29 Jan 2018 22:44:31Z agent allocating
29 Jan 2018 22:44:49Z workload maintenance installing charm software
29 Jan 2018 22:44:49Z agent executing running install hook
29 Jan 2018 22:45:47Z agent executing running leader-
29 Jan 2018 22:45:48Z agent executing running config-changed hook
29 Jan 2018 22:45:55Z agent executing running start hook
29 Jan 2018 22:45:57Z workload unknown
29 Jan 2018 22:45:57Z workload unknown
29 Jan 2018 22:45:58Z agent executing running update-status hook
29 Jan 2018 22:46:01Z agent failed update relations [1 29 30 31 32 33 96 97 98 100 114 127 217 248 259]
29 Jan 2018 22:46:24Z agent executing running leader-
29 Jan 2018 22:46:24Z agent executing running config-changed hook
29 Jan 2018 22:46:33Z agent executing running neutron-
29 Jan 2018 22:46:36Z agent failed update relations [1 29 30 31 32 33 96 97 98 100 114 127 217 248 259]
29 Jan 2018 22:47:10Z agent executing running leader-
29 Jan 2018 22:47:10Z agent executing running config-changed hook
29 Jan 2018 22:47:17Z agent executing running amqp-relation-
29 Jan 2018 22:47:20Z agent executing running image-service-
29 Jan 2018 22:47:21Z agent failed update relations [1 29 30 31 32 33 96 97 98 100 114 127 217 248 259]
[ and on and on ]
Seemingly similar bugs:
https:/
https:/
This environment is deployed on Ubuntu 14.04 LTS.
The two units that were evincing this problem somehow recovered and completed deploying successfully. I have two units left to deploy, which I will start now and report back.