Re: [Release-job-failures] Tag of openstack/freezer failed
On Mon, Dec 10, 2018 at 04:49:47AM +0000, zuul@openstack.org wrote:
Build failed.
- publish-openstack-releasenotes-python3 http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/pu... : POST_FAILURE in 2m 31s
Looking at the logs I think this failed in create-afs-token[1]. If I Understand correctly this means the releasenotes weren't published but they will upon the next successful publish run. Yours Tony. [1] http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/pu...
On 2018-12-10 16:09:22 +1100 (+1100), Tony Breeds wrote: [...]
I think this failed in create-afs-token [...]
I concur, and the most common cause for that particular error is if the afsd daemon for OpenAFS isn't running (failed to start, crashed, et cetera). Indeed, this job ran from the ze12 Zuul executor we just brought on line at the end of last week, and it looks like we missed a bootstrapping step. I've brought it back down for the time being while I make sure it's got the right kernel booted and the corresponding openafs.ko LKM built/loaded. Thanks for spotting this!!! -- Jeremy Stanley
Tony Breeds <tony@bakeyournoodle.com> writes:
On Mon, Dec 10, 2018 at 04:49:47AM +0000, zuul@openstack.org wrote:
Build failed.
- publish-openstack-releasenotes-python3 http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/pu... : POST_FAILURE in 2m 31s
Looking at the logs I think this failed in create-afs-token[1]. If I Understand correctly this means the releasenotes weren't published but they will upon the next successful publish run.
Yours Tony.
[1] http://logs.openstack.org/31/31314e5e707bfe4933e1046dd0a18f1daa8cca6c/tag/pu... _______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
Yes, that job should run again as part of the post pipeline when another patch is merged in the openstack/freezer repository. The published docs should reflect the newly tagged version. -- Doug
participants (3)
-
Doug Hellmann
-
Jeremy Stanley
-
Tony Breeds