Re: [Release-job-failures][ansible] Release of openstack/openstack-ansible failed
zuul@openstack.org writes:
Build failed.
- announce-release http://logs.openstack.org/14/1426df14f2bec09521dbf85486537250b8865fbc/releas... : FAILURE in 3m 33s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
This looks like a transient failure installing pbr (another job for the same repo at a different version worked fine). I ran tools/announce.sh in the releases repo by hand to send the announcement instead of requeuing the job [1]. That script did report a warning: No bug url found in 'openstack/openstack-ansible/README.rst' It just means that the script couldn't find the pattern it was looking for to be able to link to the bug tracker in the generated email. When that happens it just leaves the section out of the message body. I don't know how important that is to the OSA team. [1] http://lists.openstack.org/pipermail/release-announce/2019-February/006474.h... -- Doug
On Fri, Feb 22, 2019 at 1:07 PM Doug Hellmann <doug@doughellmann.com> wrote:
zuul@openstack.org writes:
Build failed.
- announce-release http://logs.openstack.org/14/1426df14f2bec09521dbf85486537250b8865fbc/releas... : FAILURE in 3m 33s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
This looks like a transient failure installing pbr (another job for the same repo at a different version worked fine). I ran tools/announce.sh in the releases repo by hand to send the announcement instead of requeuing the job [1].
That script did report a warning:
No bug url found in 'openstack/openstack-ansible/README.rst'
It just means that the script couldn't find the pattern it was looking for to be able to link to the bug tracker in the generated email. When that happens it just leaves the section out of the message body. I don't know how important that is to the OSA team.
Is there any specific format we should be using/maintaining?
[1] http://lists.openstack.org/pipermail/release-announce/2019-February/006474.h...
-- Doug
-- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
Mohammed Naser <mnaser@vexxhost.com> writes:
On Fri, Feb 22, 2019 at 1:07 PM Doug Hellmann <doug@doughellmann.com> wrote:
zuul@openstack.org writes:
Build failed.
- announce-release http://logs.openstack.org/14/1426df14f2bec09521dbf85486537250b8865fbc/releas... : FAILURE in 3m 33s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
This looks like a transient failure installing pbr (another job for the same repo at a different version worked fine). I ran tools/announce.sh in the releases repo by hand to send the announcement instead of requeuing the job [1].
That script did report a warning:
No bug url found in 'openstack/openstack-ansible/README.rst'
It just means that the script couldn't find the pattern it was looking for to be able to link to the bug tracker in the generated email. When that happens it just leaves the section out of the message body. I don't know how important that is to the OSA team.
Is there any specific format we should be using/maintaining?
[1] http://lists.openstack.org/pipermail/release-announce/2019-February/006474.h...
-- Doug
-- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
https://review.openstack.org/638738 will add the link to future releases off of master. I think you'll need to backport that if you want it in the stable branches. -- Doug
participants (2)
-
Doug Hellmann
-
Mohammed Naser