Skip to content

Update checking-mco-node-status.adoc #91666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

s-dharma
Copy link
Contributor

@s-dharma s-dharma commented Apr 4, 2025

In the Red Hat official documentation, the "oc describe" command has "-o yaml" in the end. This "-o yaml" should not be there in the "oc describe" command.

Currently the command in the document is : oc describe machineconfignode/<machine_config_node_name> -o yaml

The correct Command is : oc describe machineconfignode/<machine_config_node_name>

The "oc describe" command should not have "-o yaml" in the end.

Version(s):

RHOCP 4

Issue:

https://issues.redhat.com/browse/OSDOCS-13905

Link to docs preview:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/machine_configuration/machine-config-index#checking-mco-node-status_machine-config-overview

QE review:

  • QE has approved this change.

Additional information:

In the Red Hat official documentation, the "oc describe" command has "-o yaml" in the end. This "-o yaml" should not be there in the "oc describe" command.

Currently the command in the document is : oc describe machineconfignode/<machine_config_node_name> -o yaml

The correct Command is : oc describe machineconfignode/<machine_config_node_name>
@openshift-ci openshift-ci bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 4, 2025
Copy link

openshift-ci bot commented Apr 4, 2025

Hi @s-dharma. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant