Bug 1459929
| Summary: | Unable to collect inventory for 40,000 container images, results in kubeclient timeout | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Providers | Assignee: | Beni Paskin-Cherniavsky <cben> |
| Status: | CLOSED ERRATA | QA Contact: | Einat Pacifici <epacific> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.7.0 | CC: | akarol, cben, fsimonce, gblomqui, jfrey, jhardy, obarenbo, simaishi |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.8.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | container | ||
| Fixed In Version: | 5.8.1.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1440950 | Environment: | |
| Last Closed: | 2017-08-02 17:27:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | Container Management | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1440950 | ||
| Bug Blocks: | |||
|
Comment 2
CFME Bot
2017-06-08 15:18:38 UTC
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 |