pabelanger and clarkb helped debug this failure today, but because the release was tagged manually the release team will let the project owners handle addressing the failure, too. Clark determined that the files on PyPI do not exactly match the files on our tarballs server. One of the JSON metadata files was regenerated, and because dictionaries are unordered it came out in a different order. Clark also checked the MD5 sum on PyPI and found that the signatures match. It's not clear why the job failed. Subsequent jobs have passed. One course of action you could take is to retag the same commit with a new version number to get new packages, just to be safe. If you choose to stick with the existing packages, you will need to manually submit the constraint update, since that job was skipped after the upload job reported a failure. Please also file the update in the releases repository, so that there is a record of the fact that the release was made. Excerpts from jenkins's message of 2017-04-12 03:52:00 +0000: > Build failed. > > - diskimage-builder-docs-ubuntu-xenial http://logs.openstack.org/1f/1f200386061fe145645c9f8ffde627829cf998c9/release/diskimage-builder-docs-ubuntu-xenial/1e76d31/ : SUCCESS in 37s > - diskimage-builder-tarball http://logs.openstack.org/1f/1f200386061fe145645c9f8ffde627829cf998c9/release/diskimage-builder-tarball/6bf2ca2/ : SUCCESS in 43s > - diskimage-builder-tarball-signing http://logs.openstack.org/1f/1f200386061fe145645c9f8ffde627829cf998c9/release/diskimage-builder-tarball-signing/f219fb0/ : SUCCESS in 11s > - diskimage-builder-pypi-both-upload http://logs.openstack.org/1f/1f200386061fe145645c9f8ffde627829cf998c9/release/diskimage-builder-pypi-both-upload/077722e/ : FAILURE in 11s > - diskimage-builder-announce-release diskimage-builder-announce-release : SKIPPED > - propose-diskimage-builder-update-constraints propose-diskimage-builder-update-constraints : SKIPPED >