OCPBUGS-41485: Update MCD Log Output to Clarify No Configuration Change

[dkhater-redhat]

- What I did
Update MCD Log Output to Clarify No Configuration Change
- How to verify it
when rendered MC stays the same, observe the log
- Description for the changelog

[openshift-ci-robot]

@dkhater-redhat: This pull request references Jira Issue OCPBUGS-41485, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

- What I did
Update MCD Log Output to Clarify No Configuration Change
- How to verify it
when rendered MC stays the same, observe the log
- Description for the changelog

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.

[dkhater-redhat]

/jira refresh

[openshift-ci-robot]

@dkhater-redhat: This pull request references Jira Issue OCPBUGS-41485, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[dkhater-redhat]

/jira refresh

[openshift-ci-robot]

@dkhater-redhat: This pull request references Jira Issue OCPBUGS-41485, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[dkhater-redhat]

/jira refresh

[openshift-ci-robot]

@dkhater-redhat: This pull request references Jira Issue OCPBUGS-41485, 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

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.

[isabella-janssen]

/lgtm

/hold
Holding for QE if you think it is needed @dkhater-redhat.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkhater-redhat, isabella-janssen

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 [dkhater-redhat,isabella-janssen]

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

[dkhater-redhat]

/retest-required

[openshift-ci]

@dkhater-redhat: 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/okd-scos-e2e-aws-ovn	5eb8694	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade-out-of-change	5eb8694	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-gcp-op-ocl	5eb8694	link	false	/test e2e-gcp-op-ocl

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

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

[openshift-ci-robot]

@openshift-bot: This pull request references Jira Issue OCPBUGS-41485, which is invalid:

• expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.19" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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 verification steps:
Verified using IPI based cluster 4.18 cluster with fix

launch 4.19,openshift/machine-config-operator#5019 aws

Able to see below logs in MCD pod

$ oc logs machine-config-daemon-8chjm -f
I0502 05:16:16.503158    2565 daemon.go:2341] System state unchanged: MachineConfig: rendered-worker-ab5dc4b32fa84e250d0a3a17ee9b7b02
I0502 05:16:26.521613    2565 update.go:2786] "Update completed for config rendered-worker-ab5dc4b32fa84e250d0a3a17ee9b7b02 and node has been successfully uncordoned"
I0502 05:16:26.540517    2565 daemon.go:2369] In desired state MachineConfig: rendered-worker-ab5dc4b32fa84e250d0a3a17ee9b7b02

Apply any MachineConfig
During upgrade of node

I0502 07:43:09.144560    2565 update.go:1135] Checking Reconcilable for config rendered-worker-ab5dc4b32fa84e250d0a3a17ee9b7b02 to rendered-worker-2d39813659e3bb76b91b793eda4ef043
I0502 07:43:09.179152    2565 update.go:2786] "Starting update from rendered-worker-ab5dc4b32fa84e250d0a3a17ee9b7b02 to rendered-worker-2d39813659e3bb76b91b793eda4ef043: &{osUpdate:false kargs:false fips:false passwd:false files:true units:false kernelType:false extensions:false oclEnabled:false revertFromOCL:false}"
I0502 07:43:09.187825    2565 update.go:787] Calculating node disruption actions

After Upgrade of node is complete

I0502 07:47:00.485610    2502 update.go:2786] "Validated on-disk state"
I0502 07:47:00.489650    2502 daemon.go:2341] System state unchanged: MachineConfig: rendered-worker-2d39813659e3bb76b91b793eda4ef043
I0502 07:47:10.505786    2502 update.go:2786] "Update completed for config rendered-worker-2d39813659e3bb76b91b793eda4ef043 and node has been successfully uncordoned"

/label qe-approved

[djoshy]

/jira refresh

[openshift-ci-robot]

@djoshy: This pull request references Jira Issue OCPBUGS-41485, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.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:

/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.

[isabella-janssen]

/unhold

Removing hold since @ptalgulk01 QE approved.

[dkhater-redhat]

/label acknowledge-critical-fixes-only

[openshift-ci-robot]

@dkhater-redhat: Jira Issue OCPBUGS-41485: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#5019

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

In response to this:

- What I did
Update MCD Log Output to Clarify No Configuration Change
- How to verify it
when rendered MC stays the same, observe the log
- Description for the changelog

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.20.0-202505021646.p0.g7ff2e85.assembly.stream.el9.
All builds following this will include this PR.