Juju Charms Collection
ceph-radosgw package

stop hooks don't really do anything

Bug #1649734 reported by Jill Rouleau
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph RADOS Gateway Charm
Triaged
Low
Unassigned
ceph-radosgw (Juju Charms Collection)
Invalid
Undecided
Unassigned

Bug Description

Stop hooks are just a 'service radosgw stop' and a call to port_open. The charm does not remove any ceph packages and does not even have an identity-service-relation-departed hook. If, for example, RGW is deployed and then later destroyed in an environment, the endpoints will be left behind in the service catalog, which can cause quite some problems for a cloud. The charm ought to clean up a bit in these situations.

Revision history for this message
Chris Holcombe (xfactor973) wrote :

This is not only the radosgw charm but all the ceph-* charms.

James Page (james-page)
Changed in ceph-radosgw (Juju Charms Collection):
status: New → Invalid
Revision history for this message
Felipe Reyes (freyes) wrote :

This thread is relevant to understand the current situation of the stop hook in almost every charm.

"What are the best practices for stop hook handling?" - https://lists.ubuntu.com/archives/juju/2016-October/008040.html

James Page (james-page)
Changed in charm-ceph-radosgw:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.