Incorrect command provided for adding SCC to a serviceaccount while deploying KMM in custom namespace.

[smiglani-r]

In below documentation:
https://docs.openshift.com/container-platform/4.18/hardware_enablement/kmm-kernel-module-management.html the command provided for adding SCC to a serviceaccount while deploying KMM in custom namespace is incorrect.

$ oc adm policy add-scc-to-user privileged -z "${serviceAccountName}" [ -n "${namespace}" ]

Above command is giving an error because of incorrect brackets, ideally it should be:

Right Command:
"$ oc adm policy add-scc-to-user privileged -z serviceAccountName -n namespace" We can add note below the right command: Replace the 'namespace' argument with the 'operator namespace'.

Version(s):
OCP 4.18

Issue:
https://issues.redhat.com/browse/OCPBUGS-52586

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[smiglani-r]

/label peer-review-needed

[openshift-ci]

Hi @smiglani-r. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[opayne1]

I don't know why prow didn't give a preview, I removed the needs-ok-to-test label because I thought that might fix. But everything looks good to me pending a preview link and approval from qe.

[opayne1]

I don't know why prow didn't give a preview, I removed the needs-ok-to-test label because I thought that might fix. But everything looks good to me pending a preview link and approval from qe.

I think it might have something to do with the merge freeze today. Disregard.

[kalexand-rh]

/retest

[ocpdocs-previewbot]

🤖 Thu Apr 10 14:33:15 - Prow CI generated the docs preview:

https://90077--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_enablement/kmm-kernel-module-management.html

[openshift-ci]

@smiglani-r: 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.

[bergerhoffer]

The branch/enterprise-4.20 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.19. And any PR going into main must also target the latest version branch (enterprise-4.20).

If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[bergerhoffer]

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.