Canonical Juju

  1. Bug #1769806
  2. Comment #0

Comment 0 for bug 1769806

Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

## current resources of the caas model ->
kubectl get all -n testcaas
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/juju-mysql 1 1 1 0 42s

NAME DESIRED CURRENT READY AGE
rs/juju-mysql-6fc5f55fbf 1 1 0 42s

NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/juju-mysql 1 1 1 0 42s

NAME DESIRED CURRENT READY AGE
rs/juju-mysql-6fc5f55fbf 1 1 0 42s

NAME READY STATUS RESTARTS AGE
po/juju-mysql-6fc5f55fbf-n2gbz 0/1 ContainerCreating 0 42s
po/juju-operator-mysql 1/1 Running 0 2m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/juju-mysql ClusterIP 10.152.183.23 <none> 3306/TCP 42s

## ran `juju upgrade-model --build-agent -m controller`

## operator/agent lost, and juju ran into infinitely scale up new unites
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-mysql-6fc5f55fbf 242 242 8 12m

NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/juju-mysql 242 242 242 8 12m

NAME DESIRED CURRENT READY AGE
rs/juju-mysql-6fc5f55fbf 242 242 8 12m