Bug 1826084 - Multus should have a shorter timeout for API calls
Summary: Multus should have a shorter timeout for API calls
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Douglas Smith
QA Contact: Weibin Liang
URL:
Whiteboard: SDN-CI-IMPACT
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-20 20:23 UTC by Douglas Smith
Modified: 2020-07-13 17:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:29:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift multus-cni pull 64 0 None closed Bug 1826084: [backport 4.5] Sets the Kubernetes API calls timeout to 60 seconds 2020-12-15 12:11:23 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:29:31 UTC

Description Douglas Smith 2020-04-20 20:23:06 UTC
Description of problem: Multus should set a timeout for API calls (potentially even a timeout for an entire run) in order to complete within a time limit. 

Discovered during the 

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1826075 for making OCICNI context aware and have the ability to context cancel. 

Since Multus isn't directly tied into this chain of events starting with CRI-O and then into OCICNI (e.g. as directly call by go code, and therefore isolated from that as a CNI plugin), Multus will need to finish within the interval as is possible from CRIO & OCICNI.

Comment 1 Douglas Smith 2020-04-22 17:53:26 UTC
Upstream PR @ https://github.com/intel/multus-cni/pull/490

Comment 2 Ben Bennett 2020-05-08 19:09:16 UTC
Doug, the PR merged, what's the path to getting the code into the product?

Comment 3 Douglas Smith 2020-05-11 14:19:55 UTC
Downstream PR for 4.5 available @ https://github.com/openshift/multus-cni/pull/64

Comment 6 Weibin Liang 2020-05-12 18:09:52 UTC
Confirm with Douglas, it's not easy to cause an API timeout to reproduce this bug.
QE close this bug now and will re open it if the issue happen again.

Comment 7 errata-xmlrpc 2020-07-13 17:29:11 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:2409


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