Comment 8 for bug 1449136

There seems to be a fair bit of misunderstanding going on.

The POST_FAILURES are unrelated to pypi and pip. They were caused by the addition of a new swift log storage backend that had a container quota set too low. We've bumped the quota and the problem seems corrected.

Also, on a thread to discuss.python.org it was stated that we were getting 404s from pypi which isn't the case. The problem is that we are/were getting stale package indexes from pypi. We then cached these in our mirrors and served them to our mirror users. The problem originated with pypi and our mirrors were just serving what they got. https://github.com/pypa/warehouse/issues/8568 was filed to help coordinate with pypi on debugging and fixing. I expect this is where we'll track the issue going forward.

From there it was determined that pypi's fallback mirror had run out of disk space in early August. This meant it had gone stale. Whenever fastly would fallback to that mirror for content we would get stale content from pypi. Pypi is working to correct this and things should get better for us as they do so.

A key thing to note in the error output was that pip was getting a list of valid versions that excluded the latest version. Constraints caused us to fail because the version we wanted wasn't listed, but many valid versions were there. There were no 404s and we were getting responses from pypi. They just happened to be stale.

Finally there was also confusion that an AFS problem was involved. AFS is not used for serving pypi contents. We proxy cache pypi.