Service does not register new backend automatically
Bug #1914819 reported by
Peter Matulis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Glance Charm |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When joining Glance to Ceph RADOS Gateway the Glance service does not automatically register the new storage backend.
$ juju deploy --to lxd:0 ceph-radosgw
$ juju add-relation ceph-radosgw:mon ceph-mon:radosgw
$ juju add-relation ceph-radosgw:
$ juju add-relation ceph-radosgw:
$ glance stores-info
The output to the last command does not include the 'swift' backend name.
Apparently a manual restart of the service is required.
Revision history for this message
| Billy Olsen (billy-olsen) wrote | #1 |
| Changed in charm-glance: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
To post a comment you must log in.
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