Bug 1387273
Summary: | OCP nodes showing as "not ready" in topology view but as "Ready" in Container Node view | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Ian Tewksbury <itewksbu> | ||||||
Component: | UI - OPS | Assignee: | Ari Zellner <azellner> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Einat Pacifici <epacific> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5.6.0 | CC: | azellner, bazulay, cpelland, dshrader, fdewaley, fsimonce, hkataria, jfrey, jhardy, mbagnara, mpovolny, obarenbo, simaishi | ||||||
Target Milestone: | GA | Keywords: | TestOnly, ZStream | ||||||
Target Release: | 5.8.0 | Flags: | epacific:
automate_bug+
|
||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 5.8.0.0 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1395857 (view as bug list) | Environment: | |||||||
Last Closed: | 2017-06-12 16:25:53 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | Container Management | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1395857 | ||||||||
Attachments: |
|
Description
Ian Tewksbury
2016-10-20 14:03:10 UTC
Created attachment 1212542 [details]
screen shot of topology with errors
Created attachment 1212543 [details]
screen shot of container node view showing no errors
I reported this once upstream but I couldn't reproduce it anymore: https://github.com/ManageIQ/manageiq/issues/7363 Ari can you look into this? *** Bug 1388971 has been marked as a duplicate of this bug. *** Upstream PR: https://github.com/ManageIQ/manageiq/pull/12236 *** Bug 1391619 has been marked as a duplicate of this bug. *** PR https://github.com/ManageIQ/manageiq/pull/12236 has been merged. Should this be moved to POST? both /container_node/show/1 and container_topology/show show nodes in status Ready. verified on cfme-5.7.1.1-1.el7cf.x86_64 just noticed this is verified for the wrong version, verified on cfme-5.8.0.1-1.el7cf.x86_64 nodes from /container_topology/show and nodes from container_node/show_list will show the same status of nodes Not sure where to report this, but nodes no longer show as "Not Ready" or "Ready" = "False" in CFME when the nodes are not ready. They now show as "Ready" = "Unknown" in the Container Nodes information page, and in the topology the node will show as grey and "Unknown" instead of Not Ready. >Not sure where to report this, but nodes no longer show as "Not Ready" or "Ready" = "False" in CFME when the nodes are not ready. They now show as "Ready" = "Unknown" in the Container Nodes information page, and in the topology the node will show as grey and "Unknown" instead of Not Ready
All nodes? Always? What is their status on the openshift side?
(In reply to Ari Zellner from comment #17) > >Not sure where to report this, but nodes no longer show as "Not Ready" or "Ready" = "False" in CFME when the nodes are not ready. They now show as "Ready" = "Unknown" in the Container Nodes information page, and in the topology the node will show as grey and "Unknown" instead of Not Ready > > All nodes? Always? What is their status on the openshift side? Hi, sorry for the delayed response! All nodes that are "Ready" on the OpenShift side are displayed correctly, but if a node changes status to "NotReady," it is not recognized properly in the topology. Also, in the node information page in CFME the "Conditions -> Ready -> Status" lists as "Unknown" rather than "False" (the expected result would be to list as "False" if the node status on the OpenShift side changes to "NotReady"). In the topology, the "Condition -> Ready -> Status" is what determines how the node is displayed, and since it is listed as "Unknown" instead of "False," the topology shows the nodes as light gray (barely noticeable), rather than red. When using mouse hover over the node, it displays the status as "Unknown" rather than "NotReady." This only happens in the condition when the node status is listed in CFME as "Unknown." OpenShift nodes listed as "NotReady" on the OpenShift side always list as "Unknown" on the CloudForms side. All nodes listed as "Ready" on the OpenShift side display correctly in CloudForms. Thanks, and Happy Holidays! (In reply to Ari Zellner from comment #17) > >Not sure where to report this, but nodes no longer show as "Not Ready" or "Ready" = "False" in CFME when the nodes are not ready. They now show as "Ready" = "Unknown" in the Container Nodes information page, and in the topology the node will show as grey and "Unknown" instead of Not Ready > > All nodes? Always? What is their status on the openshift side? Hi, sorry for the delayed response! All nodes that are "Ready" on the OpenShift side are displayed correctly, but if a node changes status to "NotReady," it is not recognized properly in the topology. Also, in the node information page in CFME the "Conditions -> Ready -> Status" lists as "Unknown" rather than "False" (the expected result would be to list as "False" if the node status on the OpenShift side changes to "NotReady"). In the topology, the "Condition -> Ready -> Status" is what determines how the node is displayed, and since it is listed as "Unknown" instead of "False," the topology shows the nodes as light gray (barely noticeable), rather than red. When using mouse hover over the node, it displays the status as "Unknown" rather than "NotReady." This only happens in the condition when the node status is listed in CFME as "Unknown." OpenShift nodes listed as "NotReady" on the OpenShift side always list as "Unknown" on the CloudForms side. All nodes listed as "Ready" on the OpenShift side display correctly in CloudForms. Thanks, and Happy Holidays! (In reply to shrader from comment #19) > .... > status as "Unknown" rather than "NotReady." > > This only happens in the condition when the node status is listed in CFME as > "Unknown." OpenShift nodes listed as "NotReady" on the OpenShift side always > list as "Unknown" on the CloudForms side. All nodes listed as "Ready" on the > OpenShift side display correctly in CloudForms. > > Thanks, and Happy Holidays! This BZ isnt a good fit for that. Please report this in a separate BZ. The info seems correct according to `oc describe` and not `oc get nodes` Not sure whats correct. Either way, different BZ. [root@vm-48-184 ~]# oc get nodes NAME STATUS AGE VERSION ocp-compute01.10.35... NotReady 30d v1.7.6+a08f5eeb62 ocp-compute02.10.35.... Ready 30d v1.7.6+a08f5eeb62 ocp-infra01.10.35... Ready 30d v1.7.6+a08f5eeb62 ocp-infra02.10.35... Ready 30d v1.7.6+a08f5eeb62 ocp-master01.10.35... Ready,SchedulingDisabled 30d v1.7.6+a08f5eeb62 [root@vm-48-184 ~]# oc describe node ocp-compute01.10.35... Name: ocp-compute01.10.35... Role: Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/hostname=ocp-compute01.10.35... region=primary zone=default Annotations: volumes.kubernetes.io/controller-managed-attach-detach=true Taints: <none> CreationTimestamp: Thu, 30 Nov 2017 17:04:53 +0200 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- OutOfDisk Unknown Sun, 31 Dec 2017 14:01:44 +0200 Sun, 31 Dec 2017 14:02:24 +0200 NodeStatusUnknown Kubelet stopped posting node status. MemoryPressure Unknown Sun, 31 Dec 2017 14:01:44 +0200 Sun, 31 Dec 2017 14:02:24 +0200 NodeStatusUnknown Kubelet stopped posting node status. DiskPressure Unknown Sun, 31 Dec 2017 14:01:44 +0200 Sun, 31 Dec 2017 14:02:24 +0200 NodeStatusUnknown Kubelet stopped posting node status. Ready Unknown Sun, 31 Dec 2017 14:01:44 +0200 Sun, 31 Dec 2017 14:02:24 +0200 NodeStatusUnknown Kubelet stopped posting node status. |