[Infra][ironic][Release-job-failures] release-post job for openstack/releases failed
There was a failure in the post job for ironic-inspector in stable/stein. The error was after tagging during the log collection task. "rsync: connection unexpectedly closed" http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas... It appears all necessary tasks completed though, so I believe this should be safe to ignore. This failures caused the doc publishing job to be skipped, but we had other releases that would have picked that up. Just sharing in case we run into something similar again and need to start tracking down root cause of the rsync failure. If anyone sees anything unusual that may be a side effect of this, please let us know and we can try to investigate. Sean ----- Forwarded message from zuul@openstack.org ----- Date: Wed, 22 May 2019 16:08:49 +0000 From: zuul@openstack.org To: release-job-failures@lists.openstack.org Subject: [Release-job-failures] release-post job for openstack/releases failed Reply-To: openstack-discuss@lists.openstack.org Build failed. - tag-releases http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas... : POST_FAILURE in 4m 48s - publish-tox-docs-static publish-tox-docs-static : SKIPPED _______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures ----- End forwarded message -----
Hi Sean, I just started noticing the same error in other jobs, for example this: http://logs.openstack.org/08/660708/1/check/build-openstack-api-ref/4a33c64/... This is of course making the entire Zuul check routine fail. Riccardo On Wed, 22 May 2019 at 18:42, Sean McGinnis <sean.mcginnis@gmx.com> wrote:
There was a failure in the post job for ironic-inspector in stable/stein. The error was after tagging during the log collection task.
"rsync: connection unexpectedly closed"
http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas...
It appears all necessary tasks completed though, so I believe this should be safe to ignore. This failures caused the doc publishing job to be skipped, but we had other releases that would have picked that up.
Just sharing in case we run into something similar again and need to start tracking down root cause of the rsync failure. If anyone sees anything unusual that may be a side effect of this, please let us know and we can try to investigate.
Sean
----- Forwarded message from zuul@openstack.org -----
Date: Wed, 22 May 2019 16:08:49 +0000 From: zuul@openstack.org To: release-job-failures@lists.openstack.org Subject: [Release-job-failures] release-post job for openstack/releases failed Reply-To: openstack-discuss@lists.openstack.org
Build failed.
- tag-releases http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas... : POST_FAILURE in 4m 48s - publish-tox-docs-static publish-tox-docs-static : SKIPPED
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
----- End forwarded message -----
Hello again! I think this change https://review.opendev.org/659975 broke a couple of things. For example, when running build-openstack-api-ref, the tox_envlist is correctly set to api-ref, overwriting the value of docs from the parent openstack-tox-docs That means that tox will never build docs, so the doc/build dir doesn't exist, that's why the rsync error afterwards. The fetch-sphinx-output role should reflect that or at least evaluate the presence of the dir. Thanks, Riccardo On Thu, 23 May 2019 at 10:18, Riccardo Pittau <elfosardo@gmail.com> wrote:
Hi Sean,
I just started noticing the same error in other jobs, for example this: http://logs.openstack.org/08/660708/1/check/build-openstack-api-ref/4a33c64/...
This is of course making the entire Zuul check routine fail.
Riccardo
On Wed, 22 May 2019 at 18:42, Sean McGinnis <sean.mcginnis@gmx.com> wrote:
There was a failure in the post job for ironic-inspector in stable/stein. The error was after tagging during the log collection task.
"rsync: connection unexpectedly closed"
http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas...
It appears all necessary tasks completed though, so I believe this should be safe to ignore. This failures caused the doc publishing job to be skipped, but we had other releases that would have picked that up.
Just sharing in case we run into something similar again and need to start tracking down root cause of the rsync failure. If anyone sees anything unusual that may be a side effect of this, please let us know and we can try to investigate.
Sean
----- Forwarded message from zuul@openstack.org -----
Date: Wed, 22 May 2019 16:08:49 +0000 From: zuul@openstack.org To: release-job-failures@lists.openstack.org Subject: [Release-job-failures] release-post job for openstack/releases failed Reply-To: openstack-discuss@lists.openstack.org
Build failed.
- tag-releases http://logs.openstack.org/8f/8f71bcfb8d02cae91d0e49e5813c03c745745c92/releas... : POST_FAILURE in 4m 48s - publish-tox-docs-static publish-tox-docs-static : SKIPPED
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
----- End forwarded message -----
On Thu, 2019-05-23 at 11:36 +0200, Riccardo Pittau wrote:
Hello again!
I think this change https://review.opendev.org/659975 broke a couple of things.
For example, when running build-openstack-api-ref, the tox_envlist is correctly set to api-ref, overwriting the value of docs from the parent openstack-tox-docs That means that tox will never build docs, so the doc/build dir doesn't exist, that's why the rsync error afterwards.
The fetch-sphinx-output role should reflect that or at least evaluate the presence of the dir.
I think the correct fix is to keep the removed variable as proposed in https://review.opendev.org/660962 . Sorry for merging the broken patch in the first place. Jens
participants (3)
-
Jens Harbott
-
Riccardo Pittau
-
Sean McGinnis