-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
premerge, 4.16
-
Important
-
Yes
-
Rejected
-
False
-
Description of problem:
When OCB functionality is enabled, when we create a MC and then we delete it no build is triggered and MCO is stuck.
Version-Release number of selected component (if applicable):
pre-merge https://github.com/openshift/machine-config-operator/pull/4327
How reproducible:
Always
Steps to Reproduce:
1. Opt-in the OCB functionality (worker pool)
2. Create a MC and wait for the image to be built and the pool to be updated
3. Remove the MC that we created in step2.
Actual results:
No build is triggered and MCO is stuck. No config is applied.
Expected results:
MCO should apply the right image to the MCP.
Additional info:
- is incorporated by
-
MCO-1231 Use Kubernetes Job objects for image builds
-
- In Progress
-
- is related to
-
-
- New
-
- relates to
-
MCO-665 On-Cluster Layering Tech Preview
-
- Closed
-
