NO-ISSUE: okd: Add read permission to /etc/shadow

[praveenkumar]

During the github runner on arm64, found out that running configure-vm script fails with following error. After debugging it in the runner looks like in the container after creating the microshift user the /etc/shadow file permission is not updated. This is only happening with github ubuntu-arm runner. This PR fixes it.

 STEP 15/16: RUN echo '{"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}}' > /tmp/.pull-secret &&    /src/scripts/devenv-builder/configure-vm.sh --no-build --no-set-release-version --skip-dnf-update /tmp/.pull-secret &&    /src/okd/sr
c/use_okd_assets.sh --replace ${OKD_REPO} ${OKD_VERSION_TAG}
sudo: PAM account management error: Authentication service cannot retrieve authentication info

• https://github.com/praveenkumar/minp/actions/runs/13047611605/job/36400806209

[openshift-ci-robot]

@praveenkumar: This pull request explicitly references no jira issue.

In response to this:

During the github runner on arm64, found out that running configure-vm script fails with following error. After debugging it in the runner looks like in the container after creating the microshift user the /etc/shadow file permission is not updated. This is only happening with github ubuntu-arm runner. This PR fixes it.

STEP 15/16: RUN echo '{"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}}' > /tmp/.pull-secret &&    /src/scripts/devenv-builder/configure-vm.sh --no-build --no-set-release-version --skip-dnf-update /tmp/.pull-secret &&    /src/okd/sr
c/use_okd_assets.sh --replace ${OKD_REPO} ${OKD_VERSION_TAG}
sudo: PAM account management error: Authentication service cannot retrieve authentication info

• https://github.com/praveenkumar/minp/actions/runs/13047611605/job/36400806209

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pmtk, praveenkumar

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pmtk]

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

[openshift-ci]

@praveenkumar: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[praveenkumar]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@praveenkumar: new pull request created: #4727

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.