Comment 22 for bug 1946382

that was in the 'machine-0.log' looking in the models logs we find:
2022-02-24 16:40:16 INFO juju.worker.caasapplicationprovisioner.runner runner.go:546 restarting "harbor-registry-three" in 3s
2022-02-24 16:40:19 INFO juju.worker.caasapplicationprovisioner.runner runner.go:556 start "harbor-registry-three"
2022-02-24 16:40:22 INFO juju.worker.caasapplicationprovisioner.runner runner.go:587 stopped "harbor-registry-three", err: getting OCI image resources: unable to fetch OCI image resources for harbor-registry-three: while getting resource from the charm store: resource "registry-image" not found
2022-02-24 16:40:22 ERROR juju.worker.caasapplicationprovisioner.runner runner.go:470 exited "harbor-registry-three": getting OCI image resources: unable to fetch OCI image resources for harbor-registry-three: while getting resource from the charm store: resource "registry-image" not found
2022-02-24 16:40:22 INFO juju.worker.caasapplicationprovisioner.runner runner.go:546 restarting "harbor-registry-three" in 3s

So at the very least the code reports "installing agent" for the application should *definitely* be reporting "could not find the resource" as a hard failure for provisioning, and not bouncing around it.