| 2015-05-11 03:47:40 |
Michael Nelson |
bug |
|
|
added bug |
| 2015-05-11 04:07:39 |
Michael Nelson |
description |
I'm repeatedly deploying a stack with 8 machines and around 50% of the time (small sample) one unit remains pending indefinitely:
$ juju status sca-dp-fe
environment: local
machines:
"5":
agent-state: pending
instance-id: michael-local-machine-5
series: trusty
hardware: arch=amd64
services:
sca-dp-fe:
charm: local:trusty/apache2-0
exposed: false
units:
sca-dp-fe/0:
agent-state: allocating
machine: "5"
I had been thinking I was running out of space, lxc reports the container as started. Checking the machine log for that machine shows that the machine is unable to connect to the api server due to the juju-generated CA being rejected, while all other machines obviously don't have this problem:
http://paste.ubuntu.com/11071952/
$ apt-cache policy juju-core
juju-core:
Installed: 1.23.2-0ubuntu1~14.04.1~juju1
Candidate: 1.23.2-0ubuntu1~14.04.1~juju1
Destroying the environment (needing --force) and rebootstraping is currently the only way I know to get around this :/ |
I'm repeatedly deploying a stack with 8 machines and around 50% of the time (small sample) one unit remains pending indefinitely:
$ juju status sca-dp-fe
environment: local
machines:
"5":
agent-state: pending
instance-id: michael-local-machine-5
series: trusty
hardware: arch=amd64
services:
sca-dp-fe:
charm: local:trusty/apache2-0
exposed: false
units:
sca-dp-fe/0:
agent-state: allocating
machine: "5"
I had been thinking I was running out of space, but checked and lxc reports the container as started. Checking the machine log for that machine shows that the machine is unable to connect to the api server due to the juju-generated CA being rejected, while all other machines obviously don't have this problem:
http://paste.ubuntu.com/11071952/
$ apt-cache policy juju-core
juju-core:
Installed: 1.23.2-0ubuntu1~14.04.1~juju1
Candidate: 1.23.2-0ubuntu1~14.04.1~juju1
Destroying the environment (needing --force) and rebootstraping is currently the only way I know to get around this :/ |
|
| 2015-05-11 13:53:17 |
Curtis Hovey |
tags |
|
lxc |
|
| 2015-05-11 13:57:43 |
Curtis Hovey |
tags |
lxc |
deploy lxc |
|
| 2015-05-11 14:01:30 |
Curtis Hovey |
tags |
deploy lxc |
deploy lxc reliability repeatability |
|
| 2015-05-11 14:41:25 |
Wayne Witzel III |
juju-core: assignee |
|
Wayne Witzel III (wwitzel3) |
|
| 2015-05-11 22:08:21 |
Wayne Witzel III |
juju-core: status |
New |
Incomplete |
|
| 2015-05-12 04:20:04 |
Michael Nelson |
summary |
One unit remains pending with local provider |
destroy-env leaves one lxc which remains pending on redeploy |
|
| 2015-05-12 13:03:19 |
Curtis Hovey |
tags |
deploy lxc reliability repeatability |
destroy-environment lxc reliability repeatability |
|
| 2015-05-12 13:03:43 |
Curtis Hovey |
tags |
destroy-environment lxc reliability repeatability |
destroy-environment local-provider lxc reliability repeatability |
|
| 2015-05-12 13:04:44 |
Curtis Hovey |
juju-core: status |
Incomplete |
Triaged |
|
| 2015-05-18 14:11:56 |
Wayne Witzel III |
juju-core: status |
Triaged |
In Progress |
|
| 2015-05-19 17:24:31 |
Wayne Witzel III |
juju-core: assignee |
Wayne Witzel III (wwitzel3) |
|
|
| 2015-05-19 17:24:40 |
Wayne Witzel III |
juju-core: status |
In Progress |
Triaged |
|
| 2015-05-19 17:24:43 |
Wayne Witzel III |
juju-core: assignee |
|
Wayne Witzel III (wwitzel3) |
|
| 2015-05-21 12:38:57 |
Wayne Witzel III |
juju-core: status |
Triaged |
In Progress |
|
| 2015-07-31 14:19:56 |
Wayne Witzel III |
juju-core: status |
In Progress |
Triaged |
|
| 2015-09-09 13:55:54 |
Aaron Bentley |
juju-core: importance |
Undecided |
Medium |
|
| 2016-04-24 18:15:16 |
Curtis Hovey |
juju-core: status |
Triaged |
Fix Released |
|
