apt-get update: retries and error handling about apt HOT 3 CLOSED

I am sometimes living behind a (really not small) proxy service and I am getting quite often such sequences of failure as you can see below. When manually invoked for me it can take some 1 to >10 attempts to get all querys succeeding.

I suspect that opening this bigger bunch of locations is just giving up a tiny little bit too fast - you might know from your browser... trying the refresh keystroke after an "endlesse loading" situation will nearly instantly succeed, for whatever non-evident reason this happens. Care should be taken to allow similar behaviour either by default or by special expressed desire. An option for changing (=increasing) the retry count value on the command line that applies to the any individual open for a location should be made availabel.

See here an expample what currently happens to me:

# apt update [...] Get:6 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [391 kB] Err:6 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages Hash Sum mismatch [...] Get:10 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [114 kB] Fetched 562 kB in 3s (182 kB/s) Reading package lists... Done E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/by-hash/SHA256/6a4dfa61229a6e9d1e82f5fb3434c9b650bc856aca68add08343380e3fb48afe Hash Sum mismatch E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-i386/by-hash/SHA256/17dc81048807986276d6314abbacc968efe9da255679863b06667b5ffa60ffd8 E: Some index files failed to download. They have been ignored, or old ones used instead.

from apt.

We've removed the apt_update and apt_repository resources from this cookbook as they were merged into core chef. I'm going to close this issue out now. If you think it's still valid against a new chef-client release please open it up against the chef/chef repo so we can work on it where the code now resides.

from apt.

the resource change is not related, but the original bug seems to be "fixed" by setting "ignore_failure" to true in 24a68c0 anyhow

from apt.