Bug 1365657
| Summary: | Can not delete project after shutdown the nodes | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Weibin Liang <weliang> |
| Component: | Node | Assignee: | Andy Goldstein <agoldste> |
| Status: | CLOSED DUPLICATE | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-12 15:07:12 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: | |||
|
Description
Weibin Liang
2016-08-09 18:53:16 UTC
"oc delete project pro-ipfailover, but pro-ipfailover in Terminating forever" @decarr, this looks like some finalizer is waiting for the node to gracefully clean something? Pod deletion is in phases. If a project is terminated, the pod is marked for deletion. Either of the following must then happen: 1. the kubelet affirms the deletion (but requires node running) 2. the node controller observes an unhealthy node, and destroys the pod. If we depend on the node controller to perform the deletion, it will take >5 minutes for the pod to be terminated, so a sleep is insufficient. There is a separate bug related to the node controller: https://bugzilla.redhat.com/show_bug.cgi?id=1364243 I am marking this defect as a duplicate, but note that the test scenario of waiting 30 seconds is insufficient. If you wait >5 minutes with no action, this bug is the same as the referenced bug. *** This bug has been marked as a duplicate of bug 1364243 *** |