Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1762682

Summary: Update from 4.2.0-rc.5 to 4.2.0 partially failed
Product: OpenShift Container Platform Reporter: Michael Silich <michael>
Component: Machine Config OperatorAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED DEFERRED QA Contact: Michael Nguyen <mnguyen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-28 10:44:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Silich 2019-10-17 08:51:59 UTC
Description of problem:

After update from 4.2.0-rc.5 to 4.2.0 MCO failed to update Nodes.
Cluster itself reports "Cluster is healthy" and all nodes are in Ready state.
But worker machineconfigpools are in degraded status.

oc get machineconfigpools
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED
master   rendered-master-c5c4dfdb54227faa08f63d8296948c63   True      False      False
worker   rendered-worker-53911016fe4792cb16a872a67cf216f6   False     True       True


apiVersion: config.openshift.io/v1
kind: ClusterOperator
....
  extension:
    master: >-
      all 3 nodes are at latest configuration
      rendered-master-c5c4dfdb54227faa08f63d8296948c63
    worker: >-
      pool is degraded because nodes fail with "1 nodes are reporting degraded
      status on sync": "Node rhcos2 is reporting: \"failed to run pivot: failed
      to start machine-config-daemon-host.service: exit status 1\""



oc get nodes
NAME      STATUS   ROLES    AGE   VERSION
master1   Ready    master   27d   v1.14.6+c07e432da
master2   Ready    master   27d   v1.14.6+c07e432da
master3   Ready    master   27d   v1.14.6+c07e432da
rhcos1    Ready    worker   27d   v1.14.6+c07e432da
rhcos2    Ready    worker   27d   v1.14.6+c07e432da
rhcos3    Ready    worker   27d   v1.14.6+463c73f1f



Version-Release number of selected component (if applicable):
oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.16-201909100604+f7b7e4f-dirty", GitCommit:"f7b7e4f", GitTreeState:"dirty", BuildDate:"2019-09-10T15:22:42Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6+2e5ed54", GitCommit:"2e5ed54", GitTreeState:"clean", BuildDate:"2019-10-10T22:04:13Z", GoVersion:"go1.12.8", Compiler:"gc", Platform:"linux/amd64"}





Steps to Reproduce:
1. Update from 4.2.0-rc.5 to 4.2.0 


Actual results:
Cluster is not fully updated


Expected results:
Fully updated cluster


Additional info:

ClusterID
eef4abce-bcd4-4f55-beae-5ecd61e90b6e

must-gather
https://drive.google.com/file/d/1Nok3pjPeJm4LWtxTSxtKErEkt7KYHCKj/view?usp=sharing

Comment 1 Antonio Murdaca 2019-10-17 11:32:03 UTC
Can you by any chance grab the system journal for the rhcos2 node? it's not clear from must-gather as to why pivot failed to run there

Comment 2 Michael Silich 2019-10-17 11:51:37 UTC
Hello,

here are the logs and everything i found in the /tmp folder. Here are some machine-config-daemon.rhcos3.unknownuser.log.ERROR files

https://drive.google.com/file/d/1umRFquTNxyV91KveaAc4hGLzz67Y1WvI/view?usp=sharing

Comment 3 Michael Silich 2019-10-17 12:01:56 UTC
Sorry, please use this files

https://drive.google.com/file/d/1t6SkqiIqj0Oi6wG2PQ74LPWY7QEdVwV4/view?usp=sharing

Thanks,