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-----