charm can be stuck in waiting state if pebble-ready fires after config-changed

[mthaddon]

Currently the charm can end up stuck in a waiting state if pebble-ready fires after config-changed. See below for details.

mthaddon@finistere:~/repos/k8s-charms/hello-kubecon/hello-kubecon$ juju debug-log --no-tail --replay| grep ' ran '
unit-hello-kubecon-0: 11:22:24 INFO juju.worker.uniter.operation ran "install" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:24 INFO juju.worker.uniter.operation ran "ingress-relation-created" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:25 INFO juju.worker.uniter.operation ran "leader-elected" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:25 INFO juju.worker.uniter.operation ran "webroot-storage-attached" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:25 INFO juju.worker.uniter.operation ran "config-changed" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:26 INFO juju.worker.uniter.operation ran "start" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:26 INFO juju.worker.uniter.operation ran "install" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:26 INFO juju.worker.uniter.operation ran "ingress-relation-joined" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:26 INFO juju.worker.uniter.operation ran "ingress-relation-created" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:27 INFO juju.worker.uniter.operation ran "ingress-relation-changed" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:27 INFO juju.worker.uniter.operation ran "leader-elected" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:27 INFO juju.worker.uniter.operation ran "config-changed" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:28 INFO juju.worker.uniter.operation ran "gosherve-pebble-ready" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:28 INFO juju.worker.uniter.operation ran "start" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:29 INFO juju.worker.uniter.operation ran "ingress-relation-changed" hook (via hook dispatching script: dispatch)
unit-hello-kubecon-0: 11:22:29 INFO juju.worker.uniter.operation ran "ingress-relation-changed" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:29 INFO juju.worker.uniter.operation ran "ingress-relation-joined" hook (via hook dispatching script: dispatch)
unit-nginx-ingress-integrator-0: 11:22:30 INFO juju.worker.uniter.operation ran "ingress-relation-changed" hook (via hook dispatching script: dispatch)
mthaddon@finistere:~/repos/k8s-charms/hello-kubecon/hello-kubecon$ juju status
Model     Controller          Cloud/Region        Version  SLA          Timestamp
ing-test  microk8s-localhost  microk8s/localhost  3.0.0    unsupported  11:27:14+01:00

App                       Version  Status   Scale  Charm                     Channel  Rev  Address         Exposed  Message
hello-kubecon                      waiting      1  hello-kubecon             stable    14  10.152.183.132  no       installing agent
nginx-ingress-integrator           active       1  nginx-ingress-integrator  stable    37  10.152.183.25   no       Ingress with service IP(s): 10.152.183.59

Unit                         Workload  Agent  Address       Ports  Message
hello-kubecon/0*             waiting   idle   10.1.129.141         waiting for Pebble in workload container
nginx-ingress-integrator/0*  active    idle   10.1.129.139         Ingress with service IP(s): 10.152.183.59

[Jon Seager]

This should now be fixed in latest/stable :)