DaemonSet does not reflect current state in OpenShift Container Platform if quota exceeded

Solution In Progress - Updated -

Issue

  • DaemonSet does not reflect current state if quota exceeded
  • We use a DaemonSet to schedule a particular pod on all compute nodes in the cluster. In case we ran into exceeded quota on the project the DaemonSet is not able to schedule pods on all desired nodes. That's reasonable and an expected behavior. But we observed that in such cases the DaemonSet does not reflect the correct state of the running pods:
$ oc get ds foo-bar
NAME         DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                          AGE
foo-bar      7         7         7         7            7           node-role.kubernetes.io/compute=true   65d

$ oc get po
NAME             READY     STATUS    RESTARTS   AGE
foo-bar-gd5tb    1/1       Running   3          48d
foo-bar-k4rhk    1/1       Running   3          48d
foo-bar-nd6jf    1/1       Running   1          30d
foo-bar-qctvf    1/1       Running   5          48d
foo-bar-vvj95    1/1       Running   1          30d
foo-bar-wvmfc    1/1       Running   1          47d

Environment

  • Red Hat OpenShift Container Platform 3.10 and 3.11

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