Bug 2063328 - MCO template output directories created with wrong mode causing render failure in unprivileged container environments
Summary: MCO template output directories created with wrong mode causing render failur...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.8.z
Assignee: Dan Mace
QA Contact: Rio Liu
URL:
Whiteboard:
: 2063816 (view as bug list)
Depends On: 2063327
Blocks: 2063329
TreeView+ depends on / blocked
 
Reported: 2022-03-11 19:35 UTC by OpenShift BugZilla Robot
Modified: 2022-03-17 13:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-17 13:35:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description OpenShift BugZilla Robot 2022-03-11 19:35:15 UTC 
+++ This bug was initially created as a clone of Bug #2063327 +++

+++ 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`.
Comment 1 Kirsten Garrison 2022-03-14 19:58:02 UTC 
*** Bug 2063816 has been marked as a duplicate of this bug. ***
Comment 2 Dan Mace 2022-03-17 13:35:20 UTC 
We don't need a 4.8 backport after all.
Note You need to log in before you can comment on or make changes to this bug.