-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Moderate
-
None
-
1
-
MCO Sprint 267, MCO Sprint 268
-
2
-
False
-
-
Set proper ownership for build objects created during OCL so that they are cleaned out on success and failure.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-44602. The following is the description of the original issue:
—
Description of problem:
Intermittently, when the MOSC resource is deleted, MOSBS resources aren't removed.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-11-14-090045
How reproducible:
Intermittent
Steps to Reproduce:
1.Enable techpreview 2.Create a MOSC resource to enable OCL in a pool 3.Wait until the build pod finishes and the first node starts updating 4.Remove the MOSC resource
Actual results:
The MOSB resource is not removed when the the MOSC is deleted. It is leaked.
Expected results:
When a MOSC resource is removed, all its MOSBs should be removed too.
Additional info:
- clones
-
OCPBUGS-44602 In OCL MOSBs are leaked
-
- Verified
-
- is blocked by
-
OCPBUGS-44602 In OCL MOSBs are leaked
-
- Verified
-
- links to