Hide Forgot
Description of problem: According to: https://github.com/ManageIQ/manageiq/issues/5678 it could be possible that a refresh takes place before a node communicated its capacity (or if it's a stale invalid entry: a node never actually used). As far as I know this should never happen with nodes self-registration (but it should be checked). Steps to Reproduce: 1. create a new node (without capacity) 2. refresh inventory from ManageIQ before it's reporting its capacity Actual results: Refresh inventory crashes Expected results: Refresh should succeed.
bug fix: https://github.com/ManageIQ/manageiq/pull/5726
*** Bug 1289747 has been marked as a duplicate of this bug. ***
Steps to reproduce: # oc create -f - <<EOF {"kind": "Node", "apiVersion": "v1", "metadata": { "name": "mydummynode", "labels": { "name": "my-first-k8s-node" } } } EOF node "mydummynode" created # oc get nodes NAME LABELS STATUS AGE 10.240.79.157 name=my-first-k8s-node NotReady 5m mydummynode name=my-first-k8s-node Unknown 5s ose-master.qa.lab.tlv.redhat.com kubernetes.io/hostname=ose-master.qa.lab.tlv.redhat.com,region=infra,zone=default Ready 26d ose-node1.qa.lab.tlv.redhat.com kubernetes.io/hostname=ose-node1.qa.lab.tlv.redhat.com,region=infra,zone=default Ready 26d ose-node2.qa.lab.tlv.redhat.com kubernetes.io/hostname=ose-node2.qa.lab.tlv.redhat.com,region=primary,zone=east Ready 26d In CFME - to go providers - Select a provider - select Configuration:Refresh Items and relationships. Expected: # of nodes should reflect additional new node. In CFME go to Containers - Container Nodes Expected: All new nodes are visible (including newly added node).
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-2016:1348