It appears that the services aren't automatically restarted after rendering the config files to have the swift/ceph-radosgw service added in all scenarios. In some scenarios, i.e. if the relation is added after a cloud is deployed, the service restart is missing.
A manual work around is to restart the glance services via systemctl. Alternative options would be: a) pause/resume action to each of the units, b) toggling debug (juju config glance debug=True, juju config glance debug=False), etc
It appears that the services aren't automatically restarted after rendering the config files to have the swift/ceph-radosgw service added in all scenarios. In some scenarios, i.e. if the relation is added after a cloud is deployed, the service restart is missing.
A manual work around is to restart the glance services via systemctl. Alternative options would be: a) pause/resume action to each of the units, b) toggling debug (juju config glance debug=True, juju config glance debug=False), etc