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

Bug 1792033

Summary:	Updating node-exporter failed: reconciling node-exporter DaemonSet failed
Product:	OpenShift Container Platform	Reporter:	Kirsten Garrison <kgarriso>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sunil Choudhary <schoudha>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	alegrand, anpicker, aos-bugs, erooth, jokerman, kakkoyun, lcosic, mdhanve, mloibl, pkrupa, surbania, wking, xtian
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-25 19:59:29 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 Kirsten Garrison 2020-01-16 22:01:33 UTC

MCO is seeing in CI regularly a degraded node exporter in CI runs:

Example:
                  {
                        "lastTransitionTime": "2020-01-16T18:50:16Z",
                        "message": "Failed to rollout the stack. Error: running task Updating node-exporter failed: reconciling node-exporter DaemonSet failed: updating DaemonSet object failed: waiting for DaemonSetRollout of node-exporter: daemonset node-exporter is not ready. status: (desired: 6, updated: 6, ready: 4, unavailable: 2)",
                        "reason": "UpdatingnodeExporterFailed",
                        "status": "True",
                        "type": "Degraded"
                    },

Example runs:

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1356/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/844/artifacts/e2e-gcp-op/clusteroperators.json

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1376/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/846/artifacts/e2e-gcp-op/clusteroperators.json

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1356/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/835/artifacts/e2e-gcp-op/clusteroperators.json

Comment 1 Kirsten Garrison 2020-01-16 22:04:28 UTC

Also seeing outside of MCO:

https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/441/artifacts/e2e-vsphere-upi/clusteroperators.json

https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-shared-vpc-4.3/463/artifacts/e2e-gcp/clusteroperators.json

Comment 3 Ryan Phillips 2020-02-25 19:59:29 UTC

Fixed by https://github.com/openshift/cluster-monitoring-operator/pull/645

Initcontainers should be privileged.