Re: [Release-job-failures] release-post job for openstack/releases failed
zuul@openstack.org wrote:
Build failed.
- tag-releases http://logs.openstack.org/76/762e357c0d821c35b0373ac344d697807be031bf/releas... : FAILURE in 3m 35s - publish-tox-docs-static publish-tox-docs-static : SKIPPED
Error during release-post job processing https://opendev.org/openstack/releases/commit/22a2d440f0abddff4ba8d9e3cb8a17... The tags went through, but the Launchpad comment-adding script failed with: python3 -u /home/zuul/scripts/release-tools/launchpad_add_comment.py '--subject=Fix included in openstack/panko 3.1.1' '--content=This issue was fixed in the openstack/panko 3.1.1 release.' 1710812 Connecting to Launchpad at 'production' using credentials in '/home/zuul/.launchpadlib/creds'... Adding comment to #1710812... ERROR during save ! (HTTP Error 401: Unauthorized Response headers: --- content-length: 60 content-type: text/plain date: Wed, 24 Apr 2019 05:17:10 GMT server: zope.server.http (HTTP) status: 401 x-lazr-oopsid: OOPS-f5382a2ee4e917c314954fb63ea98c61 x-powered-by: Zope (www.zope.org), Python (www.python.org) --- Response body: --- b'Unknown consumer (System-wide: Ubuntu (review.opendev.org)).' --- ) We might have to reestablish credentials for that to work again... Impact: Bugs were not commented on (job failed), and the release website was not refreshed (job skipped). -- Thierry Carrez (ttx)
On 2019-04-24 11:56:39 +0200 (+0200), Thierry Carrez wrote: [...]
Unknown consumer (System-wide: Ubuntu (review.opendev.org)). [...] We might have to reestablish credentials for that to work again...
Impact: Bugs were not commented on (job failed), and the release website was not refreshed (job skipped).
This is almost certainly the result of my job configuration updates during The Great OpenDev Migration. I won't link the commit because Gitea does a not-so-great job of displaying commits which touch hundreds of files, but suffice to say here the hostname of the Gerrit server was changed in the consumer_key: https://opendev.org/openstack/project-config/src/commit/aca4bbb9009dfd49ec8c... I think we have a couple of viable options. We can either generate and replace the secret there with new LP access credentials now, or we can switch the consumer_key back to its pre-maintenance value for now. -- Jeremy Stanley
Impact: Bugs were not commented on (job failed), and the release website was not refreshed (job skipped).
This is almost certainly the result of my job configuration updates during The Great OpenDev Migration. I won't link the commit because Gitea does a not-so-great job of displaying commits which touch hundreds of files, but suffice to say here the hostname of the Gerrit server was changed in the consumer_key:
https://opendev.org/openstack/project-config/src/commit/aca4bbb9009dfd49ec8c...
I think we have a couple of viable options. We can either generate and replace the secret there with new LP access credentials now, or we can switch the consumer_key back to its pre-maintenance value for now. -- Jeremy Stanley
Either option sounds fine to me. Who can actually perform these operations?
On 2019-04-24 08:11:34 -0500 (-0500), Sean McGinnis wrote: [...]
This is almost certainly the result of my job configuration updates during The Great OpenDev Migration. I won't link the commit because Gitea does a not-so-great job of displaying commits which touch hundreds of files, but suffice to say here the hostname of the Gerrit server was changed in the consumer_key:
https://opendev.org/openstack/project-config/src/commit/aca4bbb9009dfd49ec8c...
I think we have a couple of viable options. We can either generate and replace the secret there with new LP access credentials now, or we can switch the consumer_key back to its pre-maintenance value for now.
Either option sounds fine to me. Who can actually perform these operations?
Anyone can propose a change for the second option (just replace "opendev" with "openstack" in that line). The first option requires access to log into Launchpad with the account in question and create a new API token, I think (if I've ever done that it's been a while and will need a bit of poking around in the UI/docs), so probably has to be an Infra root sysadmin with access to the LP credentials to do that. -- Jeremy Stanley
Jeremy Stanley wrote:
On 2019-04-24 08:11:34 -0500 (-0500), Sean McGinnis wrote: [...]
This is almost certainly the result of my job configuration updates during The Great OpenDev Migration. I won't link the commit because Gitea does a not-so-great job of displaying commits which touch hundreds of files, but suffice to say here the hostname of the Gerrit server was changed in the consumer_key:
https://opendev.org/openstack/project-config/src/commit/aca4bbb9009dfd49ec8c...
I think we have a couple of viable options. We can either generate and replace the secret there with new LP access credentials now, or we can switch the consumer_key back to its pre-maintenance value for now.
Either option sounds fine to me. Who can actually perform these operations?
Anyone can propose a change for the second option (just replace "opendev" with "openstack" in that line). The first option requires access to log into Launchpad with the account in question and create a new API token, I think (if I've ever done that it's been a while and will need a bit of poking around in the UI/docs), so probably has to be an Infra root sysadmin with access to the LP credentials to do that.
I'll submit a patch for the second option. IIRC the steps for the first option were a bit tricky. -- Thierry Carrez (ttx)
participants (3)
-
Jeremy Stanley
-
Sean McGinnis
-
Thierry Carrez