Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove machine config render check for bundle generation
It looks like if nothing other than the secret changes, the MCO will just re-use the past rendered config (because it's already there and it's what it would have rendered anyway) instead of rendering a new one. The desired end state (the proper secret ending up on the node) seems to always be reached regardless of what I do. What does happen, and what appears to result in it not rendering a new config is: - If the only thing you've changed is the secret (there are no other machine config changes in the pool) - That exact secret has already been patched in and rendered at least once before Then the mco will: - notice the secret changed (and log "Re-syncing ControllerConfig due to secret pull-secret change") - notice that there is already a matching rendered machineconfig - roll out that previously rendered machineconfig - https://bugzilla.redhat.com/show_bug.cgi?id=1999575#c1
- Loading branch information