Description of problem: Machine config operator logs itself as version v4.4.0-202002262131-dirty, while deployment/replicaset/pod show its version as 4.4.0-0.nightly-2020-02-27-020932 Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-02-27-020932 Steps to Reproduce: 1.Check deployment of MCO. $ oc get -o yaml deployment.apps/machine-config-operator | grep '4.4' -B1 -A1 - name: RELEASE_VERSION value: 4.4.0-0.nightly-2020-02-27-020932 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9f1a6e989f943c7a15bfa07b66ed9d1228407e572f3fa79ea7ec3227d8bbfa1 2. Check replicaset of MCO. $ oc get -o yaml replicaset.apps/machine-config-operator-7df667ccd | grep '4.4' -B1 -A1 - name: RELEASE_VERSION value: 4.4.0-0.nightly-2020-02-27-020932 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9f1a6e989f943c7a15bfa07b66ed9d1228407e572f3fa79ea7ec3227d8bbfa1 3.Check pod of MCO. $ oc get -o yaml pod/machine-config-operator-7df667ccd-qnvhw | grep '4.4' -B1 -A1 - name: RELEASE_VERSION value: 4.4.0-0.nightly-2020-02-27-020932 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a9f1a6e989f943c7a15bfa07b66ed9d1228407e572f3fa79ea7ec3227d8bbfa1 4. Check logs of the pod. $ oc logs pod/machine-config-operator-7df667ccd-qnvhw I0310 04:23:54.542759 1 start.go:45] Version: v4.4.0-202002262131-dirty (7db7c579fcbb583e737e52eec67f83c1ac91d011) I0310 04:23:54.570400 1 leaderelection.go:242] attempting to acquire leader lease openshift-machine-config-operator/machine-config... Actual results: The version in the log is different than version in deployment/replicaset/pod. Expected results: The version should be consistent/same. Additional info:
Verified on 4.5.0-0.nightly-2020-04-06-083820. Log shows release version now. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-04-06-083820 True False 41m Cluster version is 4.5.0-0.nightly-2020-04-06-083820 $ oc project openshift-machine-config-operator Now using project "openshift-machine-config-operator" on server "https://api.mnguyen45.devcluster.openshift.com:6443". $ oc get -o yaml deployment.apps/machine-config-operator | grep '4.5' -B1 -A1 - name: RELEASE_VERSION value: 4.5.0-0.nightly-2020-04-06-083820 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8a2d6a7381478450c9011a1d8489e952d33ba26e04e67e5ba5ce2c7d381195bc $ oc get rs NAME DESIRED CURRENT READY AGE etcd-quorum-guard-6d866cb8d9 3 3 3 49m machine-config-controller-759d8bc96 1 1 1 52m machine-config-operator-78577c5fc4 1 1 1 61m $ oc get -o yaml replicaset.apps/machine-config-operator-78577c5fc4 | grep '4.5' -B1 -A1 - name: RELEASE_VERSION value: 4.5.0-0.nightly-2020-04-06-083820 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8a2d6a7381478450c9011a1d8489e952d33ba26e04e67e5ba5ce2c7d381195bc $ oc get pods NAME READY STATUS RESTARTS AGE etcd-quorum-guard-6d866cb8d9-d8tpq 1/1 Running 0 50m etcd-quorum-guard-6d866cb8d9-kv5rl 1/1 Running 0 50m etcd-quorum-guard-6d866cb8d9-rxrlg 1/1 Running 0 50m machine-config-controller-759d8bc96-8pz4h 1/1 Running 0 53m machine-config-daemon-4lq6p 2/2 Running 0 43m machine-config-daemon-5dfqb 2/2 Running 0 42m machine-config-daemon-8tzlz 2/2 Running 0 53m machine-config-daemon-bjpf9 2/2 Running 0 52m machine-config-daemon-j6zts 2/2 Running 0 43m machine-config-daemon-p6frj 2/2 Running 0 53m machine-config-operator-78577c5fc4-9zvqn 1/1 Running 0 62m machine-config-server-5mbn8 1/1 Running 0 53m machine-config-server-8f6m6 1/1 Running 0 53m machine-config-server-9tqh4 1/1 Running 0 52m $ oc get -o yaml pod/machine-config-operator-78577c5fc4-9zvqn | grep '4.5' -B1 -A1 - name: RELEASE_VERSION value: 4.5.0-0.nightly-2020-04-06-083820 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8a2d6a7381478450c9011a1d8489e952d33ba26e04e67e5ba5ce2c7d381195bc $ oc logs pod/machine-config-operator-78577c5fc4-9zvqn | grep start.go I0407 17:27:33.080238 1 start.go:46] Version: 4.5.0-0.nightly-2020-04-06-083820 (Raw: v4.5.0-202004051501-dirty, Hash: a195251a12c0e8f9d9994c2662d3eb31c0a50eb1)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409