Bug 1845242

+++ This bug was initially created as a clone of Bug #1843319 +++

Description of problem:

Upgrading from 4.4 to 4.5, monitoring failed to achieve the new level because its node-exporter daemonset failed to rollout:

https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-azure-upgrade-4.4-stable-to-4.5-ci/56


The clusteroperator reports:

"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: 0, unavailable: 6)",


David(who asked this bug be opened) referenced:
https://github.com/kubernetes/kubernetes/pull/91008

as a possible cause and then also indicated there might be a GC issue related to the pods being reaped when the damonset was deleted.

Hopefully he can provide more details about what he saw that made him point this towards workloads vs the monitoring component itself.

--- Additional comment from Maciej Szulik on 2020-06-03 10:54:58 UTC ---

Yeah, David already opened bug 1843187, so I'll close this as a duplicate.

--- Additional comment from Tomáš Nožička on 2020-06-03 12:22:32 UTC ---

fyi, I've confirmed the pods are actually ready so this is likely the expectations bug we are tracking

--- Additional comment from David Eads on 2020-06-05 13:09:03 UTC ---

This is a different bug. The GC controller is not cleaning up six pods in openshift-monitoring that do not have valid owner references.

--- Additional comment from Ben Parees on 2020-06-05 13:17:24 UTC ---

reopening based on https://bugzilla.redhat.com/show_bug.cgi?id=1843319#c3

--- Additional comment from Ben Parees on 2020-06-05 14:59:54 UTC ---

This is causing upgrade failures in 4.5, what is the basis for deferring it?

(in general comments should always be added to a bug explaining a deferral, when the bug is deferred)

--- Additional comment from Maciej Szulik on 2020-06-08 08:23:44 UTC ---

(In reply to Ben Parees from comment #5)
> This is causing upgrade failures in 4.5, what is the basis for deferring it?
> 
> (in general comments should always be added to a bug explaining a deferral,
> when the bug is deferred)

After bug 1843187 is fixed Tomas will need to dig through the logs and identify what is causing the actual problem.
The fix has to land in 4.6 first and only then be back-ported (through clone of this BZ) to 4.5. It's not that
we are deferring thos bug, we're following the process, but it takes a bit of time to nail down the root cause and
find a fix.

--- Additional comment from Tomáš Nožička on 2020-06-08 09:32:49 UTC ---

I think the DS expectations didn't get clear on re-create case, working on a fix upstream.

--- Additional comment from Ben Parees on 2020-06-08 13:55:15 UTC ---

> The fix has to land in 4.6 first and only then be back-ported (through clone of this BZ) to 4.5. It's not that
we are deferring thos bug, we're following the process, but it takes a bit of time to nail down the root cause and
find a fix.

you can still open the 4.5 clone now so we have a complete view of our blocker list for 4.5.  Otherwise 4.5 risks going out the door w/o this being addressed (because no one except you and I are aware it affects 4.5, it doesn't show up on any 4.5 lists).

So by not opening the 4.5 BZ now, you are (implicitly) saying you're ok shipping as is/deferring this bug.