Re: [Release-job-failures] Release of openstack/monasca-tempest-plugin for ref refs/tags/2.2.0 failed
Hello monasca team, FYI a release failure happened on monasca-tempest-plugin within the job publish-monasca-tempest-plugin-docker-image. This build was triggered by https://review.opendev.org/c/openstack/releases/+/768551 (the Wallaby part). A new incompatibility in requirements was found by pip's new resolver:
pykafka 2.8.0 has requirement kazoo==2.5.0, but you'll have kazoo 2.8.0 which is incompatible. (c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... )
I didn't find a trace of these requirements on your repo so I think they are pulled/resolved from/for underlying libraries. After that the job fails to push the "latest" docker tag because the tag is not found, I think it's a side effect of the previous error. (c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... ) Let us know if we can help you, The Release Team. Le lun. 18 janv. 2021 à 23:31, <zuul@openstack.org> a écrit :
Build failed.
- openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/8dd9a4fce3bc4ae2a32134b7d7fec5b5 : SUCCESS in 52s - release-openstack-python https://zuul.opendev.org/t/openstack/build/ff7c8136563444df9c565f07f618c559 : SUCCESS in 3m 44s - announce-release https://zuul.opendev.org/t/openstack/build/78731c6e0948490d82e1e2d14eb67857 : SUCCESS in 3m 42s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/3eab7a3209a84a33b8d7b69e41e185cb : SUCCESS in 2m 49s - publish-monasca-tempest-plugin-docker-image https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa : POST_FAILURE in 8m 19s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Hi Hervé, Thanks for your note. This change will fix the problem https://review.opendev.org/c/openstack/monasca-tempest-plugin/+/771523 Now the Monasca-tempest images are published properly as you can see here: https://zuul.opendev.org/t/openstack/builds?job_name=publish-monasca-tempest... We detected this issue recently too, which affects the rest of Monasca Repositories. It can be tracked with this topic: https://review.opendev.org/q/(projects:openstack/monasca+OR+project:openstac... Could you help us please to restart the monasca-tempest-plugin release? Thanks in advance, Martin (chaconpiza) P.S. Thanks Adrian Czarnecki for the original fix! El mar, 19 de ene. de 2021 a la(s) 09:42, Herve Beraud (hberaud@redhat.com) escribió:
Hello monasca team,
FYI a release failure happened on monasca-tempest-plugin within the job publish-monasca-tempest-plugin-docker-image.
This build was triggered by https://review.opendev.org/c/openstack/releases/+/768551 (the Wallaby part).
A new incompatibility in requirements was found by pip's new resolver:
pykafka 2.8.0 has requirement kazoo==2.5.0, but you'll have kazoo 2.8.0 which is incompatible. (c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... )
I didn't find a trace of these requirements on your repo so I think they are pulled/resolved from/for underlying libraries.
After that the job fails to push the "latest" docker tag because the tag is not found, I think it's a side effect of the previous error.
(c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... )
Let us know if we can help you,
The Release Team.
Le lun. 18 janv. 2021 à 23:31, <zuul@openstack.org> a écrit :
Build failed.
- openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/8dd9a4fce3bc4ae2a32134b7d7fec5b5 : SUCCESS in 52s - release-openstack-python https://zuul.opendev.org/t/openstack/build/ff7c8136563444df9c565f07f618c559 : SUCCESS in 3m 44s - announce-release https://zuul.opendev.org/t/openstack/build/78731c6e0948490d82e1e2d14eb67857 : SUCCESS in 3m 42s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/3eab7a3209a84a33b8d7b69e41e185cb : SUCCESS in 2m 49s - publish-monasca-tempest-plugin-docker-image https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa : POST_FAILURE in 8m 19s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- *Martín Chacón Pizá* *chacon.piza@gmail.com <chacon.piza@hotmail.com>*
Le mer. 20 janv. 2021 à 11:01, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Hi Hervé,
Thanks for your note. This change will fix the problem https://review.opendev.org/c/openstack/monasca-tempest-plugin/+/771523
You're welcome
Now the Monasca-tempest images are published properly as you can see here:
https://zuul.opendev.org/t/openstack/builds?job_name=publish-monasca-tempest...
We detected this issue recently too, which affects the rest of Monasca Repositories. It can be tracked with this topic:
https://review.opendev.org/q/(projects:openstack/monasca+OR+project:openstac...
Could you help us please to restart the monasca-tempest-plugin release?
Sure, I asked the infra team to reenqueue the job, let's wait for that, do not hesitate to join #openstack-infra to join the discussion.
Thanks in advance, Martin (chaconpiza)
P.S. Thanks Adrian Czarnecki for the original fix!
El mar, 19 de ene. de 2021 a la(s) 09:42, Herve Beraud (hberaud@redhat.com) escribió:
Hello monasca team,
FYI a release failure happened on monasca-tempest-plugin within the job publish-monasca-tempest-plugin-docker-image.
This build was triggered by https://review.opendev.org/c/openstack/releases/+/768551 (the Wallaby part).
A new incompatibility in requirements was found by pip's new resolver:
pykafka 2.8.0 has requirement kazoo==2.5.0, but you'll have kazoo 2.8.0 which is incompatible. (c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... )
I didn't find a trace of these requirements on your repo so I think they are pulled/resolved from/for underlying libraries.
After that the job fails to push the "latest" docker tag because the tag is not found, I think it's a side effect of the previous error.
(c.f https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa/... )
Let us know if we can help you,
The Release Team.
Le lun. 18 janv. 2021 à 23:31, <zuul@openstack.org> a écrit :
Build failed.
- openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/8dd9a4fce3bc4ae2a32134b7d7fec5b5 : SUCCESS in 52s - release-openstack-python https://zuul.opendev.org/t/openstack/build/ff7c8136563444df9c565f07f618c559 : SUCCESS in 3m 44s - announce-release https://zuul.opendev.org/t/openstack/build/78731c6e0948490d82e1e2d14eb67857 : SUCCESS in 3m 42s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/3eab7a3209a84a33b8d7b69e41e185cb : SUCCESS in 2m 49s - publish-monasca-tempest-plugin-docker-image https://zuul.opendev.org/t/openstack/build/aba1acc623e74cf08e82ffc4d73134aa : POST_FAILURE in 8m 19s
_______________________________________________ Release-job-failures mailing list Release-job-failures@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- *Martín Chacón Pizá* *chacon.piza@gmail.com <chacon.piza@hotmail.com>*
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On 2021-01-20 11:18:56 +0100 (+0100), Herve Beraud wrote:
Le mer. 20 janv. 2021 à 11:01, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Thanks for your note. This change will fix the problem https://review.opendev.org/c/openstack/monasca-tempest-plugin/+/771523 [...] Could you help us please to restart the monasca-tempest-plugin release?
Sure, I asked the infra team to reenqueue the job, let's wait for that, do not hesitate to join #openstack-infra to join the discussion. [...]
I'm still catching up, sorry (it's been a busy day), but I have the same question which was posed by others in IRC when you initially brought it up. If the fix merged after the release request, isn't a new release request needed instead which references a later branch state containing the fix? Just trying to re-run release jobs with a ref from the old unfixed state of the repository will presumably only reproduce the same error, unless I'm misunderstanding the problem. -- Jeremy Stanley
Le jeu. 21 janv. 2021 à 00:13, Jeremy Stanley <fungi@yuggoth.org> a écrit :
On 2021-01-20 11:18:56 +0100 (+0100), Herve Beraud wrote:
Le mer. 20 janv. 2021 à 11:01, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Thanks for your note. This change will fix the problem https://review.opendev.org/c/openstack/monasca-tempest-plugin/+/771523 [...] Could you help us please to restart the monasca-tempest-plugin release?
Sure, I asked the infra team to reenqueue the job, let's wait for that, do not hesitate to join #openstack-infra to join the discussion. [...]
I'm still catching up, sorry (it's been a busy day), but I have the same question which was posed by others in IRC when you initially brought it up. If the fix merged after the release request, isn't a new release request needed instead which references a later branch state containing the fix? Just trying to re-run release jobs with a ref from the old unfixed state of the repository will presumably only reproduce the same error, unless I'm misunderstanding the problem.
Yes you're right, a new release should be done first to release the fix, sorry. @Martin: Can you propose a new release, the previous one version will stay absent of the registry. --
Jeremy Stanley
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Hi Hervé, I just proposed the new release. https://review.opendev.org/c/openstack/releases/+/772845 I am not sure whether the version should be 2.2.1 Regards, Martin El jue, 21 de ene. de 2021 a la(s) 07:49, Herve Beraud (hberaud@redhat.com) escribió:
Le jeu. 21 janv. 2021 à 00:13, Jeremy Stanley <fungi@yuggoth.org> a écrit :
On 2021-01-20 11:18:56 +0100 (+0100), Herve Beraud wrote:
Le mer. 20 janv. 2021 à 11:01, Martin Chacon Piza < chacon.piza@gmail.com> a écrit :
Thanks for your note. This change will fix the problem
https://review.opendev.org/c/openstack/monasca-tempest-plugin/+/771523 [...]
Could you help us please to restart the monasca-tempest-plugin release?
Sure, I asked the infra team to reenqueue the job, let's wait for that, do not hesitate to join #openstack-infra to join the discussion. [...]
I'm still catching up, sorry (it's been a busy day), but I have the same question which was posed by others in IRC when you initially brought it up. If the fix merged after the release request, isn't a new release request needed instead which references a later branch state containing the fix? Just trying to re-run release jobs with a ref from the old unfixed state of the repository will presumably only reproduce the same error, unless I'm misunderstanding the problem.
Yes you're right, a new release should be done first to release the fix, sorry. @Martin: Can you propose a new release, the previous one version will stay absent of the registry.
--
Jeremy Stanley
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
participants (4)
-
Herve Beraud
-
Jeremy Stanley
-
Martin Chacon Piza
-
Martin Chacon Piza