error fetching OCI image resources does not propogate to end user status
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Seen when deploying k8s charms on microk8s. If an OCI image resource isn't found (in my case it was because I'd missed defining the resources for a locally built charm in a bundle), then the status will appear to be stuck in agent allocating forever. Inspecting the debug log shows the errors.
Example:
```
❯ juju status glance
Model Controller Cloud/Region Version SLA Timestamp
zaza-c10f1e7b71e2 microk8s microk8s/localhost 2.9.33 unsupported 08:09:57+09:30
App Version Status Scale Charm Channel Rev Address Exposed Message
glance waiting 0/1 glance-k8s 0 no installing agent
Unit Workload Agent Address Ports Message
glance/0 waiting allocating installing agent
❯ juju debug-log | grep glance
controller-0: 08:10:13 ERROR juju.worker.
controller-0: 08:10:13 INFO juju.worker.
controller-0: 08:10:16 INFO juju.worker.
controller-0: 08:10:17 INFO juju.worker.
controller-0: 08:10:17 ERROR juju.worker.
controller-0: 08:10:17 INFO juju.worker.
controller-0: 08:10:20 INFO juju.worker.
controller-0: 08:10:20 INFO juju.worker.
controller-0: 08:10:20 ERROR juju.worker.
controller-0: 08:10:20 INFO juju.worker.
```
It would be nice if this error was propagated up to the juju status, to avoid wasting time waiting while it's actually in error.
| Vitaly Antonenko (anvial) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| milestone: | none → 2.9-next |
| Changed in juju: | |
| milestone: | 2.9-next → none |
Hi Samuel,
Thx for the feedback