caasapplication provisioner running for removed application

Bug #1966220 reported by Joseph Phillips
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Committed
High
Ben Hoyt

Bug Description

I removed an application with --force, but the application provisioner worker can remain running, stuck in an error loop.

This is the repeating log output:

controller-0: 15:24:31 INFO juju.worker.caasapplicationprovisioner.runner restarting "grafana-k8s" in 3s
controller-0: 15:24:34 INFO juju.worker.caasapplicationprovisioner.runner start "grafana-k8s"
controller-0: 15:24:34 INFO juju.worker.caasapplicationprovisioner.runner stopped "grafana-k8s", err: failed to watch for changes to application "grafana-k8s": application "grafana-k8s" not found
controller-0: 15:24:34 ERROR juju.worker.caasapplicationprovisioner.runner exited "grafana-k8s": failed to watch for changes to application "grafana-k8s": application "grafana-k8s" not found

Changed in juju:
status: New → Triaged
importance: Undecided → High
Harry Pidcock (hpidcock)
summary: - caasapplication providisioner running for removed application
+ caasapplication provisioner running for removed application
Harry Pidcock (hpidcock)
Changed in juju:
assignee: nobody → Ben Hoyt (benhoyt)
Revision history for this message
Ben Hoyt (benhoyt) wrote :

I've repro'd this locally using microk8s and my snappass-test charm, and it happens with and without --force. Just noting that it's not a force-specific issue.

Revision history for this message
Ben Hoyt (benhoyt) wrote :
Changed in juju:
status: Triaged → Fix Committed
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.