OS-deployer job fails to complete
Bug #1494356 reported by
Martin Packman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Ian Booth |
Bug Description
The Openstack deployer bundle test is failing in CI on 1.25 and master.
Last successful run on master:
<http://
Timeout on master:
<http://
Timeout on 1.25:
<http://
The symptom seems to be we cannot create lxc containers, but there is no obvious smoking gun in the logs.
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
no longer affects: | juju-core/1.25 |
Changed in juju-core: | |
assignee: | Cheryl Jennings (cherylj) → Tim Penhey (thumper) |
status: | Triaged → In Progress |
Changed in juju-core: | |
assignee: | Tim Penhey (thumper) → Ian Booth (wallyworld) |
Changed in juju-core: | |
milestone: | none → 1.26-alpha1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Looked at the logs for machine-0, and saw that the containers were started, but then never connected to the API. Can you get the container logs from machine-0 in /var/lib/ juju/containers /juju-machine- 0-lxc-0/ *? (or tell me how to access this environment?)
Also, is there a /var/log/ juju/machine- 0-lxc-0. log on machine-0?