infinitely scale up k8s managed units after upgraded controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu |
Bug Description
## current resources of the caas model ->
kubectl get all -n testcaas1
NAME READY STATUS RESTARTS AGE
po/juju-
po/juju-
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/juju-mysql ClusterIP 10.152.183.245 <none> 3306/TCP 2s
## ran `juju upgrade-model --build-agent -m controller`
## operator/agent lost, and juju ran into infinitely scale up new units
kubectl get all -n testcaas1
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/juju-mysql 242 242 242 8 12m
NAME DESIRED CURRENT READY AGE
rs/juju-
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/juju-mysql 242 242 242 8 12m
NAME DESIRED CURRENT READY AGE
rs/juju-
Changed in juju: | |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
importance: | Undecided → Medium |
Changed in juju: | |
importance: | Medium → Undecided |
description: | updated |
Changed in juju: | |
milestone: | none → 2.4-rc1 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
How to reproduce:
1. deploy charm with `juju-managed- units` enabled; 571e28a4d0eeb93 e89c4915e13` build.
2. updated controller to `d516a4aa7ac454