Disabling restrict-ceph-pools option has no effect

Bug #1696071 reported by Ante Karamatić
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph RADOS Gateway Charm
Triaged
Low
Unassigned
OpenStack Cinder-Ceph charm
Triaged
Low
Unassigned
OpenStack Glance Charm
Triaged
Low
Unassigned
OpenStack Nova Compute Charm
Triaged
Low
Unassigned

Bug Description

Switching restrict-ceph-pools from True to False, after the environment has been deployed and pools have been created, has no effect on Ceph pool permissions.

Expectation is that setting this option to True will result in restricted pools and setting it to False (at any moment) would disable pool restrictions.

Tags: adrastea
Ante Karamatić (ivoks)
tags: added: adrastea
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

There is no expectation in the charms at the moment that pool restrictions can be disabled, either for a specific relation or in general. We can discuss if that's a change we'd like to enable but the current expectation is that it is a one way change.

Revision history for this message
Ante Karamatić (ivoks) wrote :

Right, and that makes sense. I've reported this one because we needed a way out of bug 1696073 and 'pending bug' with the same problem for radosgw.

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

Other bug subscribers

Remote bug watches

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