Re: [Release-job-failures] Tag of openstack/cinder for ref refs/tags/15.0.0.0rc2 failed
zuul@openstack.org wrote:
Build failed.
- publish-openstack-releasenotes-python3 https://zuul.opendev.org/t/openstack/build/965908bbf69141c393d4728f7de07f7d : POST_FAILURE in 29m 45s
Looks like a transient failure
Collect sphinx build html: ssh: connect to host 162.242.237.111 port 22: Connection timed out rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
Collect artifacts: ssh: connect to host 162.242.237.111 port 22: Connection timed out rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
Release notes should be picked up at the next RC or the final, so no need to retry/reenqueue?
On 10/7/19 12:02 PM, Thierry Carrez wrote:
zuul@openstack.org wrote:
Build failed.
- publish-openstack-releasenotes-python3
https://zuul.opendev.org/t/openstack/build/965908bbf69141c393d4728f7de07f7d : POST_FAILURE in 29m 45s
Looks like a transient failure
Collect sphinx build html: ssh: connect to host 162.242.237.111 port 22: Connection timed out rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
Collect artifacts: ssh: connect to host 162.242.237.111 port 22: Connection timed out rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
Release notes should be picked up at the next RC or the final, so no need to retry/reenqueue?
That sounds OK to me.
participants (2)
-
Brian Rosmaita
-
Thierry Carrez