Node degraded due to mode mismatch for file in Openshift 4

Solution Verified - Updated -

Issue

  • How to edit the machineconfiguration file to set mode parameter when creating or editing machineconfig object ?
  • Which data type is supported for setting mode?
$ oc describe mcp worker

 Reason:

 Message:               Node worker-0.abc.example.com is reporting: "unexpected on-disk state validating against rendered-worker-d0747f04f0eb7d6eba9ffb1ea7e765c2"
    Reason:                1 nodes are reporting degraded status on sync
    Status:                True
    Type:                  NodeDegraded
    Last Transition Time:  2020-02-03T06:25:15Z
    Message:               
    Reason:                
    Status:                True
    Type:                  Degraded
  • Logs from machine-config-daemon pods show:
$ oc logs machine-config-daemon-XXXXX     // pod running on degraded node
I0203 06:25:01.780861    2611 daemon.go:889] Validating against pending config rendered-worker-d0747f04f0eb7d6eba9ffb1ea7e765c2
E0203 06:25:01.793256    2611 daemon.go:1263] mode mismatch for file: "/etc/chrony.conf"; expected: -r-----rwx; received: -r-----rwx
E0203 06:25:01.793586    2611 writer.go:127] Marking Degraded due to: unexpected on-disk state validating against rendered-worker-d0747f04f0eb7d6eba9ffb1ea7e765c2

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content