New commit detected on ManageIQ/manageiq-gems-pending/fine: https://github.com/ManageIQ/manageiq-gems-pending/commit/090bb77f454bdb351f34e3f365eadb6ec368b1fe commit 090bb77f454bdb351f34e3f365eadb6ec368b1fe Author: Adam Grare <agrare> AuthorDate: Wed May 10 09:07:44 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Jun 8 11:18:11 2017 -0400 Merge pull request #156 from cben/kubeclient-timeout bump kubeclient ~> 2.4.0 (cherry picked from commit 0aeea3dee8d470eca4f0553d79bf8cb35d66e344) https://bugzilla.redhat.com/show_bug.cgi?id=1459929 manageiq-gems-pending.gemspec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Backported to fine via https://github.com/ManageIQ/manageiq/pull/15090: kubernetes_connect, openshift_connect: add timeout settings Merge pull request ManageIQ/manageiq-providers-kubernetes#10 from cben/kubeclient-timeout kubernetes_connect: add timeout settings (cherry picked from merge commit ManageIQ/manageiq-providers-kubernetes@1ee90b5) openshift_connect: use kubernetes timeout settings (cherry picked from unmerged ManageIQ/manageiq-providers-openshift#8 - unnecessary on master but required in backports) Requires kubeclient >= 2.4.0 Tested on fine that read_timeout has an effect — too low (eg. '0.001.seconds') causes a timeout. (See parent bug 1440950 for ideas on more realistic testing)
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/RHSA-2017:1758