Bug 1810595 - Kuryr is restarted if NP got removed during its processing
Summary: Kuryr is restarted if NP got removed during its processing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Luis Tomas Bolivar
QA Contact: GenadiC
URL:
Whiteboard:
Depends On: 1810571
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-05 14:47 UTC by Michał Dulko
Modified: 2020-05-04 11:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1810571
Environment:
Last Closed: 2020-05-04 11:44:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 181 0 None closed [release-4.4] Bug 1810595: Raise K8sResourceNotFound for all client methods 2020-04-27 08:44:42 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:45:26 UTC

Description Michał Dulko 2020-03-05 14:47:37 UTC
+++ This bug was initially created as a clone of Bug #1810571 +++

Description of problem:
I've seen following traceback on NP tests run:

 Traceback (most recent call last):
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/handlers/logging.py", line 37, in __call__
     self._handler(event)
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/handlers/retry.py", line 79, in __call__
     self._handler(event)
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/handlers/k8s_base.py", line 77, in __call__
     self.on_deleted(obj)
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/controller/handlers/vif.py", line 164, in on_deleted
     crd_pod_selectors = self._drv_sg.delete_sg_rules(pod)
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/controller/drivers/network_policy_security_groups.py", line 512, in delete_sg_rules
     crd_selector)
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/controller/drivers/utils.py", line 247, in patch_kuryrnetworkpolicy_crd
     'networkpolicy_spec': np_spec})
   File "/usr/local/lib/python3.6/site-packages/kuryr_kubernetes/k8s_client.py", line 137, in patch_crd
     raise exc.K8sClientException(response.text)
 kuryr_kubernetes.exceptions.K8sClientException: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"kuryrnetpolicies.openstack.org \"np-allow-ingress\" not found","reason":"NotFound","details":{"name":"np-allow-ingress","group":"openstack.org","kind":"kuryrnetpolicies"},"code":404}

Version-Release number of selected component (if applicable):


How reproducible:
Probably a bit random. To verify it's worth to run the OpenShift network policy tests and look for similar tracebacks in logs.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Jon Uriarte 2020-03-16 17:38:22 UTC
Verified in 4.4.0-0.nightly-2020-03-13-073111 on OSP 16 RHOS_TRUNK-16.0-RHEL-8-20200226.n.1 puddle.

Didn't find the traceback described in the BZ after running Network Policy tests.

Comment 5 errata-xmlrpc 2020-05-04 11:44:56 UTC
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-2020:0581


Note You need to log in before you can comment on or make changes to this bug.