Charm stuck in Maintenance("Evaluating Manifests")
Bug #2009965 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
|
Low
|
Adam Dyess | ||
Bug Description
Only a config change or install/upgrade hook can set the deploy state
Under normal circumstances only setting this in those hooks is reasonable, if manifests are missing due to API reach-ability, then the actions sync-resources can also reapply the missing manifests. Once none are missing, the deployed flag within the charm can be set.
Without this, a completely working charm will look like this in juju status
vsphere-
Workaround:
apply a config-change, and then reset it back to the original
| Changed in charm-vsphere-cloud-provider: | |
| importance: | Undecided → Low |
| Changed in charm-vsphere-cloud-provider: | |
| milestone: | none → 1.27 |
| Changed in charm-vsphere-cloud-provider: | |
| milestone: | 1.27 → 1.26+ck3 |
| Changed in charm-vsphere-cloud-provider: | |
| assignee: | nobody → Adam Dyess (addyess) |
| status: | New → In Progress |
| Changed in charm-vsphere-cloud-provider: | |
| status: | In Progress → Fix Committed |
| 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:/