new k8s unit status are not updated currently

Bug #1875838 reported by Yang Kelvin Liu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
High
Yang Kelvin Liu

Bug Description

New units created are all under `maintenance` status even pods are in running status.

$ juju scale-application mariadb-k8s 3 -m t1
mariadb-k8s scaled to 3 units

$ juju status
Model Controller Cloud/Region Version SLA Timestamp
t1 k1 microk8s/localhost 2.8-rc1 unsupported 02:14:03-07:00

App Version Status Scale Charm Store Rev OS Address Notes
mariadb-k8s active 3 mariadb-k8s local 0 kubernetes None

Unit Workload Agent Address Ports Message
mariadb-k8s/0* active idle 10.1.81.165 3306/TCP
mariadb-k8s/1 maintenance idle 10.1.81.166 3306/TCP fetching resource: mysql_image
mariadb-k8s/2 maintenance idle 10.1.81.167 3306/TCP fetching resource: mysql_image

$ mkubectl get all,ing,replicasets,pv,pvc -n t1 -o wide ubuntu: Wed Apr 29 02:14:43 2020

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod/mariadb-k8s-0 1/1 Running 0 3m45s 10.1.81.165 ubuntu <none> <none>
pod/mariadb-k8s-1 1/1 Running 0 3m22s 10.1.81.166 ubuntu <none> <none>
pod/mariadb-k8s-2 1/1 Running 0 2m49s 10.1.81.167 ubuntu <none> <none>
pod/mariadb-k8s-operator-0 1/1 Running 0 3m49s 10.1.81.164 ubuntu <none> <none>

Changed in juju:
milestone: none → 2.8-rc1
description: updated
Ian Booth (wallyworld)
Changed in juju:
importance: Undecided → High
status: New → Triaged
Changed in juju:
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
status: Triaged → In Progress
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

This is an issue on the testing charm.

Changed in juju:
status: In Progress → Invalid
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.