Bug 1363659
Summary: | [networking_public_244] The egressnetworkpolicy can not be delete after delete project | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yan Du <yadu> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.3.0 | CC: | aos-bugs, eparis, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-27 09:42: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: |
Description
Yan Du
2016-08-03 10:01:01 UTC
Additional info: step3: Even delete the project by cluster-admin, egressnetworkpolicy still can not be deleted. The following output are getting from the ocp build 3.3.0.14. [root@qe-networking-master-1 ~]# oc get egressnetworkpolicy --all-namespaces NAMESPACE NAME bmengp1 policy-1 [root@qe-networking-master-1 ~]# oc delete egressnetworkpolicy --all -n bmengp1 [root@qe-networking-master-1 ~]# echo $? 0 [root@qe-networking-master-1 ~]# oc get egressnetworkpolicy --all-namespaces NAMESPACE NAME bmengp1 policy-1 [root@qe-networking-master-1 ~]# oc get project bmengp1 Error from server: namespaces "bmengp1" not found fixed in git This has been merged into ose and is in OSE v3.3.0.22 or newer. Test on latest OCP code, bug have been fixed. egressnetworkpolicy could be delete successfully after delete project oc v3.3.0.22 kubernetes v1.3.0+507d3a7 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:1933 |