Hide Forgot
+++ This bug was initially created as a clone of Bug #2063326 +++ +++ This bug was initially created as a clone of Bug #2063324 +++ Description of problem: While integrating with HyperShift which executes MCO binaries in unprivileged containers, I discovered the MCO template execution is creating a parent output directory with mode 0655, which causes rendering to fail because subdirectories and files can't be created within that parent due to the missing executable bit for the owner. Version-Release number of MCO (Machine Config Operator) (if applicable): 4.11 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): Yes Steps to Reproduce: Run `machine-config-operator bootstrap ... --dest-dir=/output`. Actual results: Resulting destination directory has mode `drw-r-xr-x`. Expected results: Destination directory should have mode `drwxr-xr-x`.
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 (Moderate: OpenShift Container Platform 4.9.29 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:1363