[release] Status: RED - pip resolver issue with publish-openstack-releasenotes-python3
Dear release managers, We are currently experiencing an issue with the new pip resolver in our release job (publish-openstack-releasenotes-python3), so, please hold all the release's validations for now. Indeed, today we faced an issue [1][2] during the releasing tripleo-image-elements [3]. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements [4] This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. All the repo who fit the same conditions (no doc/requirements.txt available) will fail too. We've almost identified all of these repos [5], I'll get the full list to you in a while. In parallel, fungi (Jeremy Stanley) will bring this topic on the zuul side too, to see if we can add something there to override this rule (test-requirements.txt as the default case). Thanks for reading [1] https://zuul.opendev.org/t/openstack/build/d82e8c8db7754394907459895f3f58fa [2} http://paste.openstack.org/show/801385/ [3] https://review.opendev.org/c/openstack/releases/+/768237 [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tas... [5] http://paste.openstack.org/show/801396/ -- 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-----
Here is the filtered list of projects that meet the conditions leading to the bug, and who should be fixed to completely solve our issue: adjutant-ui api-site blazar blazar-nova blazar-tempest-plugin ceilometermiddleware cinder-tempest-plugin cloudkitty cloudkitty-tempest-plugin contributor-guide cyborg-tempest-plugin debtcollector designate-tempest-plugin etcd3gw freezer-api freezer-dr glance-tempest-plugin governance governance-sigs governance-website i18n ideas ironic-python-agent-builder kuryr-libnetwork manila-image-elements manila-tempest-plugin molteniron monasca-api monasca-events-api monasca-log-api monasca-persister monasca-statsd monasca-tempest-plugin murano-dashboard networking-baremetal networking-hyperv neutron-dynamic-routing neutron-tempest-plugin neutron-vpnaas openstack-manuals openstack-virtual-baremetal openstack-zuul-roles os-apply-config os-collect-config os-refresh-config os-service-types osprofiler ossa pycadf pyeclib pymod2pkg python-cyborgclient python-masakariclient python-monascaclient release-test security-analysis security-doc senlin-tempest-plugin solum-dashboard sushy sushy-tools telemetry-tempest-plugin tempest-lib tempest-stress training-guides tripleo-common tripleo-common-tempest-plugin tripleo-heat-templates tripleo-image-elements tripleo-puppet-elements tripleo-quickstart-extras tripleo-repos tripleo-upgrade trove-dashboard virtualbmc vitrage-tempest-plugin whereto workload-ref-archs zaqar-tempest-plugin zun-tempest-plugin Notice that some of these projects aren't deliverables but if possible it could be worth fixing them too. These projects have an incompatibility between entries in their test-requirements.txt, and they're missing a doc/requirements.txt file. The more straightforward path to unlock our job " publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...). I propose to track the related advancement by using the "fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status. Also it could be worth fixing test-requirements.txt incompatibilities but this task is more on the projects teams sides and this task could be done with a follow up patch. Thoughts? Le lun. 4 janv. 2021 à 16:15, Herve Beraud <hberaud@redhat.com> a écrit :
Dear release managers,
We are currently experiencing an issue with the new pip resolver in our release job (publish-openstack-releasenotes-python3), so, please hold all the release's validations for now.
Indeed, today we faced an issue [1][2] during the releasing tripleo-image-elements [3].
The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements [4]
This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error.
All the repo who fit the same conditions (no doc/requirements.txt available) will fail too. We've almost identified all of these repos [5], I'll get the full list to you in a while.
In parallel, fungi (Jeremy Stanley) will bring this topic on the zuul side too, to see if we can add something there to override this rule (test-requirements.txt as the default case).
Thanks for reading
[1] https://zuul.opendev.org/t/openstack/build/d82e8c8db7754394907459895f3f58fa [2} http://paste.openstack.org/show/801385/ [3] https://review.opendev.org/c/openstack/releases/+/768237 [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tas... [5] http://paste.openstack.org/show/801396/
-- 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-----
-- 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 Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions leading to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if possible it could be worth fixing them too.
These projects have an incompatibility between entries in their test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job "publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the "fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé! Done for python-masakariclient in [1]. etcd3gw needs more love in general but I will have this split in mind. [1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163 -yoctozepto
Thanks all! Here we can track our advancement: https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...) Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek <radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions leading
to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if possible
it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities
but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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 Mon, Jan 4, 2021 at 7:25 PM Herve Beraud <hberaud@redhat.com> wrote:
Thanks all!
Here we can track our advancement:
https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...)
Herve thanks very much for your efforts - I was just getting caught up on this to post the tripleo changes but I see you already beat me to it. I'll check your list to see if there are any more and will post. I'll bring this to the tripleo irc meeting today as well so we can get help merging those asap. thank you marios
Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek < radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions leading
to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if possible
it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities
but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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 Herve, I have added this topic to the Monasca irc meeting today. Thank you, Martin (chaconpiza) El lun, 4 de ene. de 2021 a la(s) 18:30, Herve Beraud (hberaud@redhat.com) escribió:
Thanks all!
Here we can track our advancement:
https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...)
Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek < radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions leading
to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if possible
it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities
but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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>*
@release mangaers: For now I think we can restart validating projects that aren't present in the previous list (c.f http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h... ). Normally they aren't impacted by this problem. I'll move to the "Orange" state when all the projects of list will be patched or at least when a related patch will be present in the list (c.f https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open...)). For now my monitoring indicates that ~50 projects still need related changes. So, for now, please, ensure that the repos aren't listed here before validate a patch http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h... Thanks to everyone who helped here! Much appreciated! Le mar. 5 janv. 2021 à 12:05, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Hi Herve,
I have added this topic to the Monasca irc meeting today.
Thank you, Martin (chaconpiza)
El lun, 4 de ene. de 2021 a la(s) 18:30, Herve Beraud (hberaud@redhat.com) escribió:
Thanks all!
Here we can track our advancement:
https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...)
Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek < radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions leading
to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if possible
it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities
but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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-----
Hello everyone, @release managers: all impacted projects now have fixes submitted, so before validating a patch you only have to ensure that the released projects aren't in the list of opened patches: https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open) I move our status to ORANGE as the situation seems improving for now and also because we can easily monitor the state. @all: Notice that some projects have been ignored here because they aren't released, here is the list: i18n ideas openstack-manuals openstack-zuul-roles os-apply-config os-collect-config os-refresh-config ossa pyeclib security-analysis security-doc tempest-lib tempest-stress training-guides workload-ref-archs However it could be worth it to uniformize them, but we leave it to the teams to update them. Also notice that we proposed to add the capabilities to zuul to retrieve requirements from a dedicated place: https://review.opendev.org/c/zuul/zuul-jobs/+/769292 It will help projects that haven't documentation but that produce release notes to split their requirements more properly. If you've questions do not hesitate to ping us on #openstack-release Thanks for your reading Le mer. 6 janv. 2021 à 12:47, Herve Beraud <hberaud@redhat.com> a écrit :
@release mangaers: For now I think we can restart validating projects that aren't present in the previous list (c.f http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h... ). Normally they aren't impacted by this problem.
I'll move to the "Orange" state when all the projects of list will be patched or at least when a related patch will be present in the list (c.f https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open...)). For now my monitoring indicates that ~50 projects still need related changes.
So, for now, please, ensure that the repos aren't listed here before validate a patch http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h...
Thanks to everyone who helped here! Much appreciated!
Le mar. 5 janv. 2021 à 12:05, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Hi Herve,
I have added this topic to the Monasca irc meeting today.
Thank you, Martin (chaconpiza)
El lun, 4 de ene. de 2021 a la(s) 18:30, Herve Beraud (hberaud@redhat.com) escribió:
Thanks all!
Here we can track our advancement:
https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...)
Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek < radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions
leading to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if
possible it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt incompatibilities
but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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-----
-- 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-----
Hello, @release managers: Just a heads-up to highlight projects that need to be approved carefully. I think we could improve our filtering by only considering the failing projects in the list of patched and unmerged projects: https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open) Most of these projects CI met a pip resolver issue, so if we release these projects without merging the associated patches we will fail at least with: - publish-openstack-releasenotes-python3 - publish-openstack-sphinx-doc Take a look to the following example: - https://review.opendev.org/c/openstack/os-service-types/+/769766 - https://zuul.opendev.org/t/openstack/build/53eec1ae61734bf39fb24a106920bbcf @ptl: Please ensure that your projects aren't in the list of failing projects and if so, please try to address the resolver issue in your requirements. Thanks for your reading PS: Notice that you can consider that this email is also a friendly reminder about the fact that we are still at the Orange level status :) Le jeu. 7 janv. 2021 à 17:53, Herve Beraud <hberaud@redhat.com> a écrit :
Hello everyone,
@release managers: all impacted projects now have fixes submitted, so before validating a patch you only have to ensure that the released projects aren't in the list of opened patches:
https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open)
I move our status to ORANGE as the situation seems improving for now and also because we can easily monitor the state.
@all: Notice that some projects have been ignored here because they aren't released, here is the list:
i18n ideas openstack-manuals openstack-zuul-roles os-apply-config os-collect-config os-refresh-config ossa pyeclib security-analysis security-doc tempest-lib tempest-stress training-guides workload-ref-archs
However it could be worth it to uniformize them, but we leave it to the teams to update them.
Also notice that we proposed to add the capabilities to zuul to retrieve requirements from a dedicated place:
https://review.opendev.org/c/zuul/zuul-jobs/+/769292
It will help projects that haven't documentation but that produce release notes to split their requirements more properly.
If you've questions do not hesitate to ping us on #openstack-release
Thanks for your reading
Le mer. 6 janv. 2021 à 12:47, Herve Beraud <hberaud@redhat.com> a écrit :
@release mangaers: For now I think we can restart validating projects that aren't present in the previous list (c.f http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h... ). Normally they aren't impacted by this problem.
I'll move to the "Orange" state when all the projects of list will be patched or at least when a related patch will be present in the list (c.f https://review.opendev.org/q/topic:%2522fix-relmgt-pip-doc%2522+(status:open...)). For now my monitoring indicates that ~50 projects still need related changes.
So, for now, please, ensure that the repos aren't listed here before validate a patch http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.h...
Thanks to everyone who helped here! Much appreciated!
Le mar. 5 janv. 2021 à 12:05, Martin Chacon Piza <chacon.piza@gmail.com> a écrit :
Hi Herve,
I have added this topic to the Monasca irc meeting today.
Thank you, Martin (chaconpiza)
El lun, 4 de ene. de 2021 a la(s) 18:30, Herve Beraud ( hberaud@redhat.com) escribió:
Thanks all!
Here we can track our advancement:
https://review.opendev.org/q/topic:%22fix-relmgt-pip-doc%22+(status:open%20O...)
Le lun. 4 janv. 2021 à 18:02, Radosław Piliszek < radoslaw.piliszek@gmail.com> a écrit :
On Mon, Jan 4, 2021 at 4:34 PM Herve Beraud <hberaud@redhat.com> wrote:
Here is the filtered list of projects that meet the conditions
leading to the bug, and who should be fixed to completely solve our issue:
... etcd3gw ... python-masakariclient ...
Notice that some of these projects aren't deliverables but if
possible it could be worth fixing them too.
These projects have an incompatibility between entries in their
test-requirements.txt, and they're missing a doc/requirements.txt file.
The more straightforward path to unlock our job
"publish-openstack-releasenotes-python3" is to create a doc/requirements.txt file that only contains the needed dependencies to reduce the possibility of pip resolver issues. I personally think that we could use the latest allowed version of requirements (sphinx, reno, etc...).
I propose to track the related advancement by using the
"fix-relmgt-pip-doc" gerrit topic, when all the projects will be fixed we would be able to update our status.
Also it could be worth fixing test-requirements.txt
incompatibilities but this task is more on the projects teams sides and this task could be done with a follow up patch.
Thoughts?
Thanks, Hervé!
Done for python-masakariclient in [1].
etcd3gw needs more love in general but I will have this split in mind.
[1] https://review.opendev.org/c/openstack/python-masakariclient/+/769163
-yoctozepto
-- 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-----
-- 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-----
-- 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-04 16:15:45 +0100 (+0100), Herve Beraud wrote: [...]
In parallel, fungi (Jeremy Stanley) will bring this topic on the zuul side too, to see if we can add something there to override this rule (test-requirements.txt as the default case). [...]
Well, what I was originally suggesting was that we'd want some way to have it use doc/requirements.txt instead of test-requirements.txt, but on closer reading of the role it already actually does that automatically, so I'm not sure there's much else to be done on the Zuul end of things. Really as you point out this needs to be fixed in the individual projects by either correcting these incompatibilities between intentionally unconstrained linters/static analyzers in their test-requirements.txt files, or by following OpenStack's long-standing docs PTI recommendations (and ideally doing both): "List python dependencies needed for documentation in doc/requirements.txt" https://governance.openstack.org/tc/reference/project-testing-interface.html... -- Jeremy Stanley
participants (5)
-
Herve Beraud
-
Jeremy Stanley
-
Marios Andreou
-
Martin Chacon Piza
-
Radosław Piliszek