Red Hat Bugzilla – Bug 1516228
Normal user can delete networkpolicy in cli but cannot in web console
Last modified: 2018-04-05 05:32:46 EDT
Description of problem: Normal user can delete networkpolicy in cli but cannot in web console Version-Release number of selected component (if applicable): v3.7.9 How reproducible: Always Steps to Reproduce: 1. $ cat allow-all.yaml kind: NetworkPolicy apiVersion: extensions/v1beta1 metadata: name: allow-all spec: podSelector: ingress: - {} oc create -f allow-all.yaml 2. Login in web console, goto 'Other resources' page, select NetworkPolicy in dropdown list and try delete it. 3. oc get NetworkPolicy 4. oc delete NetworkPolicy allow-all 5, oc get NetworkPolicy Actual results: 3. After very long time, the allow-all networkpolicy still exists 5. CLI could be deleted successfully. Expected results: Should delete it immediately. Additional info: CLi and web should be consistent with delete network policy
This appears to be an issue with the garbage collector and NetworkPolicy because the console does foreground deletion of resources by default and the CLI defaults to no garbage collection policy. I can see the resource getting marked with the deletionTimestamp and the finalizer: apiVersion: extensions/v1beta1 kind: NetworkPolicy metadata: creationTimestamp: '2017-11-22T12:15:02Z' deletionGracePeriodSeconds: 0 deletionTimestamp: '2017-11-22T12:15:19Z' finalizers: - foregroundDeletion generation: 2 name: allow-all namespace: jwforres resourceVersion: '65432501' selfLink: /apis/extensions/v1beta1/namespaces/jwforres/networkpolicies/allow-all uid: c465ede7-cf7e-11e7-89cc-02306c0cdc4b spec: ingress: - {} podSelector: {}
See https://github.com/openshift/origin/pull/17426
Is this still an issue? I can't reproduce I think the above PR fixed the issue
This bug has been fixed by that PR, could you help change to ON_QA?
Check this issue with the OCP v3.7.14, this bug has been fixed. Could delete networkpolicy on web console.
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-2018:0636