Bug 1343157
Summary: | Project delete leads to unexpected items in namespace | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Vikas Laad <vlaad> |
Component: | Node | Assignee: | Derek Carr <decarr> |
Status: | CLOSED DUPLICATE | QA Contact: | DeShuai Ma <dma> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-15 17:23:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Vikas Laad
2016-06-06 16:02:54 UTC
Created attachment 1165274 [details]
journalctl_atomic-openshift-node
Created attachment 1165276 [details]
grep for project eap64-mysql-s2i-user-402-171-469-216 in /var/log/messages
Created attachment 1165278 [details]
different pods stuck on the cluster
The logs showed a single pod stuck in Terminating status: eap-app-5-s05at The master logs showd the namespace controller repeatedly observing that the pod was not yet deleted (it was stuck pending deletion from the kubelet or node controller in the case that the node was no longer healthy). There was no specific log action from the kubelet for pod: eap-app-5-s05at. It's not possible to know given the current logs if this was the only pod stuck terminating on this node. If so, its possible the symptom for this bug is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1364243 - where pods in terminating status would not get deleted by node controller if they were the only pod on the node. I am closing this issue as duplicate of 1364243. If the symptom repeats itself, please include the YAML output for `oc get pods --all-namespaces`, and the YAML output for `oc get nodes` so we can check heartbeats and pod->node assignment. *** This bug has been marked as a duplicate of bug 1364243 *** |