juju rc1 loses agents during a lxd deploy
Bug #1572237 reported by
Adam Stokes
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Eric Snow |
Bug Description
Using juju commit http://
Here is my juju status output: https:/
And log output from one of the failed services 'rabbitmq' http://
I also enabled DEBUG for logging and capture this log from ceph-osd that is failing:
description: | updated |
description: | updated |
tags: | added: lxd-provider |
Changed in juju-core: | |
importance: | Undecided → Critical |
milestone: | none → 2.0-rc1 |
status: | New → Triaged |
Changed in juju-core: | |
milestone: | 2.0-beta5 → 2.0-rc1 |
Changed in juju-core: | |
assignee: | nobody → William Reade (fwereade) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta6 → none |
milestone: | none → 2.0-beta6 |
To post a comment you must log in.
This is the rabbitq machine log with TRACE debugging enabled:
http:// paste.ubuntu. com/15935428/
This is the same unit's log with TRACE enabled:
http:// paste.ubuntu. com/15935446/