OCPBUGS-52827: Fixing typos for MachineConfigNode

[NoahArrowood]

Closes : OCPBUGS-52827

- What I did
Fixed typos for MachineConfigNode.

- How to verify it
N/A

- Description for the changelog
OCPBUGS-52827: Fixes typos for MachienConfigNode

[openshift-ci]

Hi @NoahArrowood. 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.

[isabella-janssen]

/label ok-to-test

[openshift-ci]

@isabella-janssen: The label(s) /label ok-to-test cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label ok-to-test

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.

[isabella-janssen]

/ok-to-test

[isabella-janssen]

/retest-required

[isabella-janssen]

/jira refresh

[openshift-ci-robot]

@isabella-janssen: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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-robot]

@NoahArrowood: This pull request references Jira Issue OCPBUGS-52827, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Closes : OCPBUGS-52827

- What I did
Fixed typos for MachineConfigNode.

- How to verify it
N/A

- Description for the changelog
OCPBUGS-52827: Fixes typos for MachienConfigNode

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.

[ptalgulk01]

Pre-merge verified:
Using IPI based AWS cluster

Applied CRC config

cat update/containerRuntime_worker.yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: ContainerRuntimeConfig
metadata:
 name: crt-worker
 labels:
   machineconfiguration.openshift.io/role: worker 
spec:
 machineConfigPoolSelector:
   matchLabels:
     pools.operator.machineconfiguration.openshift.io/worker: ''
 containerRuntimeConfig:
   pidsLimit: 2048
   logLevel: debug
   overlaySize: 8G
   logSizeMax: "-1"

- Check the edits in MCN

$ oc describe machineconfignode ip-10-0-14-62.us-east-2.compute.internal
   Last Transition Time:  2025-03-18T07:51:18Z
    Message:               Action during update to rendered-worker-21da712b4486addace6cf29db5f4e537: Upgrade required a reboot. Completed this as the post update action.
    Reason:                UpdatePostActionCompleteRebootedNode
    Status:                False
    Type:                  RebootedNode
    Last Transition Time:  2025-03-18T05:16:15Z

/label qe-approved

[openshift-ci-robot]

@NoahArrowood: This pull request references Jira Issue OCPBUGS-52827, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

Closes : OCPBUGS-52827

- What I did
Fixed typos for MachineConfigNode.

- How to verify it
N/A

- Description for the changelog
OCPBUGS-52827: Fixes typos for MachienConfigNode

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.

[isabella-janssen]

/approved

[djoshy]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, NoahArrowood

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 [djoshy]

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

[isabella-janssen]

/retest-required

[openshift-ci]

@NoahArrowood: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-op-ocl	feb8d94	link	false	/test e2e-gcp-op-ocl
ci/prow/okd-scos-e2e-aws-ovn	feb8d94	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade-out-of-change	feb8d94	link	false	/test e2e-azure-ovn-upgrade-out-of-change

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d96d261 and 2 for PR HEAD feb8d94 in total

[openshift-ci-robot]

@NoahArrowood: Jira Issue OCPBUGS-52827: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#4914

Jira Issue OCPBUGS-52827 has been moved to the MODIFIED state.

In response to this:

Closes : OCPBUGS-52827

- What I did
Fixed typos for MachineConfigNode.

- How to verify it
N/A

- Description for the changelog
OCPBUGS-52827: Fixes typos for MachienConfigNode

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.19.0-202503191139.p0.gfe8353e.assembly.stream.el9.
All builds following this will include this PR.

[isabella-janssen]

/cherry-pick release-4.18 release-4.17 release-4.16

[openshift-cherrypick-robot]

@isabella-janssen: new pull request created: #4927

In response to this:

/cherry-pick release-4.18 release-4.17 release-4.16

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.