-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Moderate
-
None
-
3
-
MCO Sprint 264, MCO Sprint 265, MCO Sprint 266, MCO Sprint 267
-
4
-
False
-
-
Set proper ownership for build objects created during OCL so that they are cleaned out on success and failure.
-
Bug Fix
-
In Progress
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:
- blocks
-
-
- ASSIGNED
-
- is cloned by
-
-
- ASSIGNED
-
- is duplicated by
-
-
- Closed
-
- relates to
-
MCO-828 On-Cluster Layering GA
-
- Testing
-
-
MCO-870 pre-merge testing: On-Cluster Build GA
-
- Closed
-
-
-
- Closed
-
- links to
(1 relates to, 1 links to)
