Ussuri glance config fails : missing policy.json
Bug #1872996 reported by
loonatic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Glance Charm |
Fix Released
|
High
|
Alex Kavanagh | ||
Bug Description
Upstream OpenStack Ussuri and Canonical Ussuri glance package have both removed policy.json :
https:/
https:/
https:/
Deploying Ussuri glance fails as the charm still expects a policy.json file.
| Changed in charm-glance: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Alex Kavanagh (ajkavanagh) |
| Changed in charm-glance: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-glance (master) | #1 |
| Changed in charm-glance: | |
| status: | In Progress → Fix Committed |
| Changed in charm-glance: | |
| milestone: | none → 20.05 |
| Changed in charm-glance: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 848eb535a43b16a
Author: Alex Kavanagh <email address hidden>
Date: Tue Mar 31 21:47:04 2020 +0100
Remove policy.json from charm for ussuri
Glance (in ussuri) uses policy-in-code, and so that policy.json file
doesn't ship with the package. This means that the charm can't rely on
the file existing ussuri onwards. This patchset changes the way the
charm uses policy.json by switching it to a charm determined policy.yaml
file (preferred format) with the only 3 options that the charm
determines to enforce.
Also add yaml vars to focal-ussuri bundle
This brings it into line with the other charms that are part of the the
enable-focal topic. This makes it easier to add a new bundle just by
changing a couple of variables.
Closes-Bug: #1872996
Change-Id: I47f19272a4e0af