Cluster upgrade Master node Machine Config Daemon `could not stat file: "/etc/kubernetes/manifests/etcd-member.yaml"`

Solution Verified - Updated -

Issue

  • After upgrading from Red Hat OpenShift Container Platform 4.3.z to 4.4.z the master nodes are marking Degradeddue to unexpected on-disk state validating against rendered-master-26b2ef2cf1c3ddd7cc0ad00c89xxxxxx
  • Upgrading from Red Hat OpenShift Container Platform 4.3.z to 4.4.z the master nodes are Degradedand errors are visible in the Machine Config Daemon log:

    2020-11-16T08:33:34.234896602Z I1116 08:33:34.234255 1767787 daemon.go:759] Current+desired config: rendered-master-26b2ef2cf1c3ddd7cc0ad00c89xxxxxx
    2020-11-16T08:33:34.251342366Z I1116 08:33:34.251290 1767787 daemon.go:1016] Validating against current config rendered-master-26b2ef2cf1c3ddd7cc0ad00c89xxxxxx
    2020-11-16T08:33:35.115126311Z E1116 08:33:35.115050 1767787 daemon.go:1399] could not stat file: "/etc/kubernetes/manifests/etcd-member.yaml", error: lstat /etc/kubernetes/manifests/etcd-member.yaml: no such file or directory 
    2020-11-16T08:33:35.115126311Z E1116 08:33:35.115111 1767787 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-26b2ef2cf1c3ddd7cc0ad00c89xxxxxx
    

Environment

  • Red Hat OpenShift Container Platform 4.3
  • Red Hat OpenShift Container Platform 4.4

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