Public bug reported: I did a little digging on this, and it's definitely the UID on the RBAC role.
I'd blame this commit: https://github.com/juju/juju/commit/35e712ef6bf485aaeb8b718e6e6aa10683e381bc#diff-1bb294296419d47846f2432fb32f22cd9f42745a4c0aa8568f140bf499799b9fR85 Juju calls a factory with a name only: https://github.com/juju/juju/blob/develop/caas/kubernetes/provider/application/application.go#L934 Then gets a bare struct where UID is definitely empty, and immediately try to delete it with an empty precondition: https://github.com/juju/juju/blob/dcc82d771253673354f5cd96cc87b528bd81e7b2/caas/kubernetes/provider/resources/clusterrolebinding.go#L31 ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Package changed: v4l2loopback (Ubuntu) => juju (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936253 Title: Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1936253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
