Description of problem: The `machine-config-controller bootstrap` subcommand uses the `--template` flag default value, but the flag is only associated with the `start` subcommand internally, so end users can't actually override the hard-coded default value when running the `bootstrap` command. Version-Release number of MCO (Machine Config Operator) (if applicable): Platform (AWS, VSphere, Metal, etc.): All Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)? (Y/N/Not sure): Y How reproducible: Run `machine-config-controller bootstrap --template`. Did you catch this issue by running a Jenkins job? If yes, please list: No Steps to Reproduce: Run `machine-config-controller bootstrap --template ...`. Actual results: Command fails because the `--template` flag is unrecognized. Expected results: Should work with the value I provided. Additional info: This was encountered performing integration work for HyperShift.
I can verify that the merged fix resolves the issues we were having in HyperShift.
To be clear, I DID verify that the merged fix resolves the issues we were having in HyperShift.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069