Running the sync-manifest applys the wrong container images
Bug #2010233 reported by
Adam Dyess
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Charm AWS Kubernetes Storage |
Fix Released
|
High
|
Adam Dyess | ||
| vSphere Cloud Provider Charm |
Fix Released
|
High
|
Adam Dyess | ||
Bug Description
When running the sync-manifest action on a charm, the manifest manipulations are being applied multiple times applying drastically incorrect registry images.
| Changed in charm-vsphere-cloud-provider: | |
| importance: | Undecided → High |
| milestone: | none → 1.27 |
Revision history for this message
| Adam Dyess (addyess) wrote | #1 |
| Changed in charm-vsphere-cloud-provider: | |
| status: | New → In Progress |
| assignee: | nobody → Adam Dyess (addyess) |
| Changed in charm-vsphere-cloud-provider: | |
| status: | In Progress → Fix Committed |
| Changed in charm-vsphere-cloud-provider: | |
| milestone: | 1.27 → 1.26+ck3 |
| tags: | added: backport-needed |
| Changed in charm-vsphere-cloud-provider: | |
| status: | Fix Committed → Fix Released |
| Changed in charm-aws-k8s-storage: | |
| milestone: | none → 1.27 |
Revision history for this message
| Adam Dyess (addyess) wrote | #3 |
| Changed in charm-aws-k8s-storage: | |
| status: | New → In Progress |
| assignee: | nobody → Adam Dyess (addyess) |
| importance: | Undecided → High |
| Changed in charm-aws-k8s-storage: | |
| status: | In Progress → Fix Committed |
| Changed in charm-aws-k8s-storage: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Addressed with
https:/