require ceph or swift backend when deployed in HA configuration
Bug #1719964 reported by
David Lawson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Glance Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
It is possible to configure the charm to have both the file storage backend and multiple units, which causes each unit to get a random selection of images, which causes any instance booting to have a one in N chance of talking to a glance unit that actually has the image it's trying to boot. Obviously, this ends in hilarity. It'd be nice if the charm had some guardrails to keep you from shooting yourself in the foot in that specific way, since the failure mode is annoyingly difficult to debug.
Changed in charm-glance: | |
milestone: | 18.02 → 18.05 |
Changed in charm-glance: | |
milestone: | 18.05 → 18.08 |
Changed in charm-glance: | |
milestone: | 18.08 → 18.11 |
Changed in charm-glance: | |
milestone: | 18.11 → 19.04 |
Changed in charm-glance: | |
milestone: | 19.04 → 19.07 |
Changed in charm-glance: | |
milestone: | 19.07 → 19.10 |
Changed in charm-glance: | |
milestone: | 19.10 → 20.01 |
Changed in charm-glance: | |
milestone: | 20.01 → 20.05 |
Changed in charm-glance: | |
milestone: | 20.05 → 20.08 |
Changed in charm-glance: | |
milestone: | 20.08 → none |
To post a comment you must log in.
Agreed - the charm knows whether its in a HA deployment, so should add the requirement for either a ceph of swift backend to the required interfaces list that's used to assess status in this scenario.