-
Story
-
Resolution: Unresolved
-
Major
-
None
-
4.16.0
The current naming scheme for MOSB follows: poolName-poolRenderedConfig-builder, which is designed in the way to differentiate builds for different pools and desired configs. However when there is a change in the MOSC (e.g. custom ContainerFile change), triggering MOSB will result in a failure due to lack of changing in its names. As a result, we will need to find a mechanism to structurally assign different names to different MOSBs and better differentiate them.
Accept criteria:
- We have a well-designed naming mechanism for MOSBs
- Ensure changes to pools, MOSCs and MOSBs will all trigger rebuild / new build
Proposed solution:
- Have a render func to generate a new name for it: https://github.com/openshift/machine-config-operator/blob/master/pkg/controller/render/hash.go
- Manage the observed generation of the MachineOSConfig --> use this to find the right MachineOSBuild (1:1 observed generation and config generation)
- blocks
-
MCO-756 Changes to custom Containerfile should trigger a rebuild
-
- To Do
-