Story #5880
Updated by jsherril@redhat.com over 4 years ago
Currently pulp3 will abort a sync immediately if any download fails other than an HTTP response that has a status code of There are certain http codes were i think pulp should fail quickly (such as those in the 400 range). 429, 502, 503, or 504 I However i think there are other situations where users may experience an intermittent issue with their such as networking failures or dns that causes the download to fail without actually getting to the remote server at all. This could failures which may be an aborted connection or intermittent and where a dns resolution failure. Ideally there would be some option that would allow pulp to retry those failures. may succeed. I fear that without this option So if i'm a user syncing and am trying to sync a large RPM repository may have on a hard time ever completing the download if they don't have a perfect network (which you'd hope all networks were). So my proposal with intermittent failures, it would be that if this nice to have the option was enabled, any error of turning on download would be a more liberal retry policy where by most things are retried if: 1. at least a few times. it was Especially in the case where no http response code is returned (meaning we likely never actually got to the webserver). I believe that is actually my most pressing concern, not one where we got an HTTP response that was not one of 429, 502, 503, or 504 2. No http response was received 504, which will already retry.
.