Red Hat Bugzilla – Bug 1500180
Too many "no observation found for eviction signal allocatableNodeFs.available" logs in node
Last modified: 2017-11-28 17:15:54 EST
Description of problem: Too many "no observation found for eviction signal allocatableNodeFs.available" logs in node. The error log itself does not mean there is disk pressure or eviction manager takes any actions such as reclaiming nodefs. Upstream issue: https://github.com/kubernetes/kubernetes/issues/48703#issuecomment-317789189 Version-Release number of selected component (if applicable): openshift v3.7.0-0.143.1 kubernetes v1.7.0+80709908fd etcd 3.2.1 How reproducible: Always Steps to Reproduce: 1.In ocp3.7, check node logs # journalctl -u atomic-openshift-node | grep "no observation found" Oct 09 08:00:07 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:07.733643 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:00:17 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:17.742208 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:00:27 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:27.754007 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:00:37 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:37.762051 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:00:47 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:47.770107 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:00:57 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:00:57.778060 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:07 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:07.786923 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:17 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:17.795019 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:27 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:27.802760 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:37 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:37.811072 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:47 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:47.819434 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:01:57 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:01:57.828784 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:02:07 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:02:07.840055 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available Oct 09 08:02:17 qe-dma-node-registry-router-3.localdomain atomic-openshift-node[17287]: W1009 08:02:17.848854 17299 helpers.go:771] eviction manager: no observation found for eviction signal allocatableNodeFs.available 2. 3. Actual results: Expected results: Additional info: This should fixed by https://github.com/kubernetes/kubernetes/pull/48636
This fix came in on the rebase to kube 1.7.6. https://github.com/openshift/origin/pull/16615 Should be included in v3.7.0-0.144.0
Verify on openshift v3.7.0-0.184.0 kubernetes v1.7.6+a08f5eeb62 etcd 3.2.8 There is no those error logs
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/RHSA-2017:3188