GCP: Changing the image-registry causes charm error
Bug #1988867 reported by
Adam Dyess
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Control Plane Charm |
Fix Released
|
Medium
|
Adam Dyess | ||
Bug Description
An active/idle 1.25/stable unit with a changed image-registry errors because it fails to parse the API results appropriately in cases were NetworkUnavailable condition doesn't exist.
Revision history for this message
| Adam Dyess (addyess) wrote | #1 |
| Changed in charm-kubernetes-master: | |
| milestone: | none → 1.25+ck1 |
| assignee: | nobody → Adam Dyess (addyess) |
| status: | New → Fix Committed |
| tags: | added: backport-needed |
| Changed in charm-kubernetes-master: | |
| importance: | Undecided → Medium |
| tags: | removed: backport-needed |
| Changed in charm-kubernetes-master: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/