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.
Upstream PR @ https://github.com/intel/multus-cni/pull/490
Doug, the PR merged, what's the path to getting the code into the product?
Downstream PR for 4.5 available @ https://github.com/openshift/multus-cni/pull/64
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.
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