Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications

Bug #1936262 reported by Yang Kelvin Liu
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Yang Kelvin Liu

Bug Description

Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications

controller-0: 10:27:26 ERROR juju.worker.caasapplicationprovisioner.runner exited "grafana-k8s": Operation cannot be fulfilled on ClusterRoleBinding.rbac.authorization.k8s.io "lma-grafana-k8s": the UID in the precondition () does not match the UID in record (271d46cc-7e5e-42fa-bcbe-7f22e820d72e). The object might have been deleted and then recreated

tags: added: sidecar-charm
Changed in juju:
status: New → Triaged
status: Triaged → In Progress
importance: Undecided → Critical
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
milestone: none → 2.9.9
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.