Skip to content

Conversation

@rabi
Copy link
Contributor

@rabi rabi commented Jan 21, 2026

OpenSSH requires private keys to have mode 0600 when the file owner matches the process UID. With restricted-v2 SCC (default), the process runs as a random UID different from the file owner, so OpenSSH skips the check. But when using NFS mounts for development (hostmount-anyuid SCC), ansible-ee containers run as root which matches the key file
owner, triggering the strict permission check.

Set defaultMode to 384 (0600) for SSH key volumes to ensure OpenSSH accepts the key.

@openshift-ci openshift-ci bot requested review from dprince and rebtoor January 21, 2026 03:36
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rabi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

OpenSSH requires private keys to have mode 0600 when the file owner
matches the process UID. With restricted-v2 SCC (default), the process
runs as a random UID different from the file owner, so OpenSSH skips
the check. But when using NFS mounts for development (hostmount-anyuid
SCC), ansible-ee containers run as root which matches the key file
owner, triggering the strict permission check.

Set defaultMode to 384 (0600) for SSH key volumes to ensure OpenSSH
accepts the key.

Signed-off-by: rabi <[email protected]>
@rabi
Copy link
Contributor Author

rabi commented Jan 21, 2026

/test functional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant