Bug 1618657
| Summary: | Random errors pushing images to docker-registry on router reload | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Pili Guerra <pguerra> |
| Component: | Image Registry | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED CANTFIX | QA Contact: | Dongbo Yan <dyan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.9.0 | CC: | aos-bugs, pguerra, public, tobias.brunner |
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-08-17 14:03:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pili Guerra
2018-08-17 08:55:01 UTC
It may be that the actual issue is within the Docker client code, not with the registry or OpenShift. When the OpenShift application router (HAProxy) reloads the configuration, requests may end up failing. The Docker client code has provisions to retry some failing requests, but looking at the code, they are not all done while pushing an image. Pili based on your last comment what would you like us to do with this bug? Do the registry logs show these errors? > Do the registry logs show these errors?
The registry pod(s) show nothing. The errors stem from failing HTTP requests in the Docker client which aren't retried.
ok. I can either close this as "can't fix", or we can send it to the router/networking team if you think the router should be handling this differently. Up to you. I don't think the router in OpenShift or the Docker registry can handle it differently. Changes would be required in the Docker client which isn't under your control. Context: I work for the company which opened the support case which led to this report via Pili. On our end we got multiple reports from customers who experienced these issues. It was only after in-depth debugging that we discovered that it was a client-side issue, not in OpenShift. As such it was a follow-up to the support case which assumed that it's an OpenShift-specific issue. Please go ahead and close as WONTFIX. We'll have to report it to upstream if it continues to be an issue. Thanks The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |