-
Bug
-
Resolution: Done
-
Major
-
None
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
OCP Node Sprint 278 (green)
-
1
-
In Progress
-
Known Issue
-
-
None
-
None
-
None
-
None
Description of problem:
In a scenario where the client wants to completely uninstall Kueue (for example 1.0.1) so a new version can be installed, some Kueue CRs are getting stuck and never been completely deleted.
Version-Release number of selected component (if applicable):
Any version of Kueue (OCP 4.18 and 4.19)
How reproducible:
We should install Kueue Operator and Operand, create some configuration such as resourceflavor, clusterqueue and localqueue. After this, execute a job to get the worlkoad created and then, try to completely uninstall Kueue.
Steps to Reproduce:
1. Install Kueue Operator and Operand 2. Create a resource flavor and cluster queue 3. Create a namespace and local queue 4. Run a job, to create a workload 5. Go to Operators > Installed Operators > Click on the 3 dots > Uninstall Operator > Check the option "Delete all operand instances for this operator"
Actual results:
On Installed Operators page, seems that Kueue was completely uninstalled. However, if we go to CustomResourceDefinitions and check Kueue CRs, some are showing "Resource is being deleted". This state is kept until some user interference, for example, finalizers deletion (picture attached).
Expected results:
Kueue uninstall should handle all Kueue CRs and uninstall them properly.
Additional info:
A way to get the CRs deleted, is to manually delete the finalizers.
- relates to
-
OCPKUEUE-292 General release testing
-
- Closed
-
- links to