-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.17
-
Moderate
-
Yes
-
False
-
Description of problem:
When we have several MSOB resources and we delete the MOSC resource, not all MOSB resources are garbage colledted. After deleting the MOSC resource we can see that there are MOSB resource that were not deleted.
Version-Release number of selected component (if applicable):
4.17
How reproducible:
Always
Steps to Reproduce:
1. Enable techpreview 2. Create a MOSC resource 3. Wait for the image to be built and applied 3. Create a new MC (any MC) so that we build a new image and a new MOSB resource is created 4. Wait for the image to be built and applied 5. Remove the MOSC resource
Actual results:
We have this initial scenario $ oc get machineosconfig NAME AGE worker 79m $ oc get machineosbuild NAME PREPARED BUILDING SUCCEEDED INTERRUPTED FAILED worker-rendered-worker-269adf05864ad9d63d7954781af64f0b-builder False False True False False worker-rendered-worker-85efffa30bf41b4071acea2242099603-builder False False True False False When we remove the the MOSC resource we get this final scenario $ oc get machineosconfig No resources found $ oc get machineosbuild NAME PREPARED BUILDING SUCCEEDED INTERRUPTED FAILED worker-rendered-worker-269adf05864ad9d63d7954781af64f0b-builder False False True False False Only one MOSB resource was garbage collected.
Expected results:
All machineosbuild resources should be garbage collected when we remove a machineosconfig resource
Additional info:
- relates to
-
OCPBUGS-32809 When OCB is enabled, MCO is stuck if a MC is deleted
- New