radosgw process is not always alive when workload-status declares the charm ready.
Bug #1508551 reported by
Ryan Beisner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ceph-radosgw (Juju Charms Collection) |
Invalid
|
Undecided
|
David Ames | ||
Bug Description
The radosgw process is not always alive when workload-status declares the charm ready.
The deploy completes, workload status reaches "ready," then there is no radosgw process on the ceph-radosgw/0 unit.
http://
I'd recommend that we wait for the underlying init script bug fix to make its way into the releases by way of the updated ceph package, then re-visit this.
This is actually:
https:/
https:/
Related branches
lp://staging/~thedac/charms/trusty/ceph-radosgw/stop-start
Ready for review
for merging
into
lp://staging/~openstack-charmers-archive/charms/trusty/ceph-radosgw/next
- Liam Young (community): Needs Fixing
- Ryan Beisner (community): Needs Information
-
Diff: 198 lines (+72/-11)4 files modifiedhooks/charmhelpers/contrib/openstack/utils.py (+3/-1)
hooks/hooks.py (+13/-7)
hooks/utils.py (+51/-1)
unit_tests/test_hooks.py (+5/-2)
| Changed in ceph-radosgw (Juju Charms Collection): | |
| assignee: | nobody → David Ames (thedac) |
| status: | New → Confirmed |
| description: | updated |
| summary: |
- Kilo (Trusty and Vivid): The radosgw process is not always alive when - workload-status declares the charm ready. + radosgw process is not always alive when workload-status declares the + charm ready. |
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in ceph-radosgw (Juju Charms Collection): | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Fixed in the packaging.