broken authentication when using multiple ceph backends on a single cinder application

I think this is side-effect of the history of this deployment - the ceph support directly in the cinder charm also writes this override, but I'm pretty sure that for any recent openstack release its simply not required so we could drop it from the charm and tidy up in a commit.

However that probably does not help the 'how do I move to cinder-ceph' use case that you have here.

Confirmed:

        return {
            "cinder": {
                "/etc/cinder/cinder.conf": {
                    "sections": {
                        service: [
                            ('volume_backend_name', service),
                            ('volume_driver', volume_driver),
                            ('rbd_pool', service),
                            ('rbd_user', service),
                            ('rbd_secret_uuid', leader_get('secret-uuid')),
                        ]
                    }
                }
            }
        }

rbd_user is set.

We should probably also be writing out rbd_ceph_conf to allow multiple ceph clusters to be used from the same cinder-volume service.

That option is supported since mitaka at least.

Infact all the way back to icehouse; this needs a refresh across both charms to avoid this conflict and to allow migration to a cinder-ceph configured backend.

Fix proposed to branch: master
Review: https://review.openstack.org/567554

Fix proposed to branch: master
Review: https://review.openstack.org/567556

Reviewed: https://review.openstack.org/567554
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=3451c1c4985359a9a1c4c1c7527808fd84a380e6
Submitter: Zuul
Branch: master

commit 3451c1c4985359a9a1c4c1c7527808fd84a380e6
Author: James Page <email address hidden>
Date: Thu May 10 11:38:59 2018 +0100

    Tidy ceph backend configuration

    Drop generation of upstart override file and /etc/environment and
    scrub any existing charm configuration in these locations from
    an existing install.

    These where required way back in the dawn of time when ceph support
    was alpha/beta in cinder.

    Provide backend specific configuration file path, allowing multiple
    ceph clusters to be used with a single cinder application.

    Change-Id: I7adba0d35fb7406afa40f047b79a9ab51a6a333d
    Closes-Bug: 1769196

Reviewed: https://review.openstack.org/567556
Committed: https://git.openstack.org/cgit/openstack/charm-cinder-ceph/commit/?id=b1829e983ae3b56e016cf9de437fde35b1f6a83f
Submitter: Zuul
Branch: master

commit b1829e983ae3b56e016cf9de437fde35b1f6a83f
Author: James Page <email address hidden>
Date: Thu May 10 11:48:38 2018 +0100

    Tidy ceph backend configuration

    Drop generation of upstart override file and /etc/environment
    and scrub any existing charm configuration in these locations
    from an existing install.

    These where required way back in the dawn of time when ceph
    support was alpha/beta in cinder.

    Provide backend specific configuration file path, allowing
    multiple ceph clusters to be used with a single cinder
    application.

    Change-Id: I8a097e4de1c5c980f118a587a1a64792fad2fa05
    Closes-Bug: 1769196