Default track change cause deployment failure when using charmstore compat API
Bug #2029370 reported by
Arif Ali
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snap Store Server |
Fix Released
|
High
|
Guillermo Gonzalez |
Bug Description
We have an environment we have a fixed versioning of charms being deployed from the original charm-store.
As an example the following charms worked on 27th July at 11:34 UTC
cs:aodh-48
cs:cinder-310
cs:glance-305
cs:neutron-api-294
cs:gnocchi-46
cs:heat-283
cs:openstack-
cs:vault-46
We have since tried deployment of these charms and have unable to be able to do this, wand we get a similar message as the one below for each of them
ERROR cannot deploy bundle: cs:aodh-48 resource "policyd-override": bad metadata: resource missing filename
The default track was changed on the 28th July [1], and could potentially be the cause of this happening
Changed in snapstore-server: | |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
summary: |
- default track change fails deployment + Default track change cause deployment failure when using charmstore + compat API |
Changed in snapstore-server: | |
assignee: | nobody → Guillermo Gonzalez (verterok) |
status: | Confirmed → In Progress |
Changed in snapstore-server: | |
status: | In Progress → Fix Committed |
Changed in snapstore-server: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.