Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications
Bug #1936253 reported by
Ryan Barry
This bug report is a duplicate of:
Bug #1936262: Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju (Ubuntu) |
In Progress
|
Undecided
|
Yang Kelvin Liu |
Bug Description
I did a little digging on this, and it's definitely the UID on the RBAC role.
I'd blame this commit: https:/
Juju calls a factory with a name only:
https:/
Then gets a bare struct where UID is definitely empty, and immediately try to delete it with an empty precondition:
affects: | v4l2loopback (Ubuntu) → juju (Ubuntu) |
Changed in juju (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
To post a comment you must log in.
https:/ /github. com/juju/ juju/pull/ 13166 will be landed to 2.9 to fix this issue.