enforce juju3.1+ for deployment

Bug #2051857 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
High
Kevin W Monroe
Kubernetes Worker Charm
Fix Released
High
Kevin W Monroe

Bug Description

Juju upgrade-charm and subsequent config-changed hooks are causing problems when coming from juju 2.9. For the 1.29 release, enforce a juju 3 environment.

This is a follow-on to LP#2049953 where hook environments seem to use new charm metadata before the updated charm is in place. We'll also address this in our 1.29 release notes, but charm enforcement is desired just in case users miss that particular note :)

Changed in charm-kubernetes-worker:
assignee: nobody → Kevin W Monroe (kwmonroe)
importance: Undecided → High
status: New → In Progress
milestone: none → 1.29
Changed in charm-kubernetes-master:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Kevin W Monroe (kwmonroe)
milestone: none → 1.29
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

PRs for 1.29:

k-c-p:
https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/pull/329

k-w:
https://github.com/charmed-kubernetes/charm-kubernetes-worker/pull/163

Cherry-picks for the relevant bits needed in release_1.29 branches to follow.

Changed in charm-kubernetes-master:
status: In Progress → Fix Committed
Changed in charm-kubernetes-worker:
status: In Progress → Fix Committed
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
Changed in charm-kubernetes-worker:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.