The release job for magnum failed, but luckily it was after tagging and branching the release. It was not able to get to the point of uploading a tarball to http://tarballs.openstack.org/magnum/ though. The problem the job encountered is that magnum is now configured to publish to Pypi. The tricky part ends up being that the "magnum" package on Pypi is not this magnum project. It appears to be an older abandoned project by someone, not related to OpenStack. There is an openstack-magnum registered. But since the setup.cfg file in openstack/magnum has "name = magnum", it attempts to publish to the one that is not ours. I have put up a patch to openstack/magnum to change the name to openstack-magnum here: https://review.openstack.org/#/c/542371/ That, or something like it, will need to merge and be backported to stable/queens before we can get this project published. If there are any questions, please feel free to drop in to the #openstack-release channel. Thanks, Sean ----- Forwarded message from zuul at openstack.org ----- Date: Thu, 08 Feb 2018 17:09:44 +0000 From: zuul at openstack.org To: release-job-failures at lists.openstack.org Subject: [Release-job-failures] release-post job for openstack/releases failed Reply-To: openstack-dev at lists.openstack.org Build failed. - tag-releases http://logs.openstack.org/11/1160e02315eaef3a8380af3d6dd9f707eccc214e/release-post/tag-releases/ff8305f/ : TIMED_OUT in 32m 28s - publish-static publish-static : SKIPPED _______________________________________________ Release-job-failures mailing list Release-job-failures at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures ----- End forwarded message -----