[openstacksdk][RelMgmt] release-post job for openstack/releases for ref refs/heads/master failed

Sean McGinnis sean.mcginnis at gmx.com
Thu Oct 17 11:52:10 UTC 2019

----- Forwarded message from zuul at openstack.org -----

Date: Thu, 17 Oct 2019 10:19:24 +0000
From: zuul at openstack.org
To: release-job-failures at lists.openstack.org
Subject: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
Reply-To: openstack-discuss at lists.openstack.org

Build failed.

- tag-releases https://zuul.opendev.org/t/openstack/build/571c0f0e43cb469d8727121b77a3c92b : FAILURE in 3m 14s
- publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED

Release-job-failures mailing list
Release-job-failures at lists.openstack.org

----- End forwarded message -----

The tagging of the new stable/queens OpenStackSDK release failed. It appears to
be due to the .gitreview file in that branch still referring to the
python-openstacksdk name. That caused the automation to fail on trying to
interact with that repo, but it has since been renamed to

Since this wasn't able to process the release, even though the patch had
merged, I think the fix is actually fairly easy. I've proposed a backport of
the repo name changes with:


If we were to do another release to pick up that change, I believe it would
actually fail validation because it would not find the current 0.11.4 tag and
therefore think that two releases were needed instead of just one.

So since it was not able to process anything to actually perform the release, I
believe the easy path forward is to just revert the release patch of this last


Then wait for the .gitreview patch to merge, then propose the 0.11.4 release
again with the hash updated to include that rename fix.

Please let me know if there are any questions or if I've overlooked anything.


More information about the openstack-discuss mailing list