Comment 28 for bug 2056193

Sure, thx.

- the recorded "provider id" value on httprequest-lego-provider/0, available by running juju status --format yaml (if it'snot there, will be on the unit doc in mongo)

The unit has `provider-id: httprequest-lego-provider-0` but the application has `provider-id: 4d8dbb8e-41f2-483c-b31d-fe09ac238084`.

- model logging config updated to also include "juju.worker.caasoperator=DEBUG"

This has been done

- kubectl get -o yaml pods/httprequest-lego-provider-0
- kubectl describe pods/httprequest-lego-provider-0

Here's the info for the two items above https://pastebin.canonical.com/p/6vtBBj8YKX/. And here's `kubectl get pods` for the namespace:

```
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
httprequest-lego-provider-0 2/2 Running 1 (22h ago) 7d23h
modeloperator-5cf8598576-d6k4r 1/1 Running 0 34d
nginx-ingress-integrator-0 1/1 Running 1 (18d ago) 27d
```

The restart on httprequest-lego-provider-0 is from when I ran `kill -9 15` as part of troubleshooting above.