Bug 1324465
| Summary: | Can not know if the project is deleted in the delay period of deleting project after project controller delete the policy in the project | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Xiaolin <xxing> |
| Component: | Pod | Assignee: | Cesar Wong <cewong> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.x | CC: | aos-bugs, mmccomas, wjiang, wsun, xxing |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 17:11:20 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: | |||
|
Comment 1
Andy Goldstein
2016-04-06 13:41:43 UTC
The project name will not be released until the namespace is finally removed from Kubernetes, but we potentially can look to no longer charge the user for the project request limitation by not counting namespaces that are in terminating phase. https://github.com/openshift/origin/blob/master/pkg/project/admission/requestlimit/admission.go#L114 This would mean that we would still be as latent as the watch notification propagating to that admission controller so the corresponding test scripts that drive the behavior may also have to change. Add project request limit to config and Verify on AMI rhel7_3934,it should be fixed and work well for our user case, Thank you all. $openshift version openshift v1.1.6-38-g6ecbaaf kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 But there is another issue,after do delete,create a project with the same name immediately,it would fail,I wonder if we should think about this user case. Xiaolin, yes there will still be the limitation about reusing the name because the name has to be unique across the cluster. Get it,have virified this fixed,thanks |