The client release you tagged had a build failure. It looks like
the tag was pushed directly, so I will relay the results of the
debugging work but let you decide how to deal with it.
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
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 09:29:09 +0000:
OpenStack Development Mailing List (not for usage questions)