wily-liberty: 3 units cluster OK but workload status not updated
Bug #1508295 reported by
Ryan Beisner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rabbitmq-server (Juju Charms Collection) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
On Wily-Liberty (next), rabbitmq-server forms a cluster successfully, but the extended workload status isn't updated accordingly.
This causes an eternal wait (fail) in testing, as the workload status is how readiness is determined.
More details @ http://
Also see attached logs.
Related branches
lp:~james-page/charms/trusty/rabbitmq-server/status-reeval
- Liam Young (community): Approve
-
Diff: 24 lines (+4/-1)1 file modifiedhooks/rabbitmq_server_relations.py (+4/-1)
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #1 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #2 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #3 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #4 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #5 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #6 |
Revision history for this message
| Ryan Beisner (1chb1n) wrote | #7 |
| Changed in rabbitmq-server (Juju Charms Collection): | |
| status: | New → Fix Committed |
| status: | Fix Committed → Fix Released |
| importance: | Undecided → Medium |
To post a comment you must log in.
FYI, I waited an extra 20 min after this manual test to confirm. No notable activity in juju debug-log, and workload status messages remained as pasted.