-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
taskflow cap is blocking the usage of newer versions of taskflow in openstack #12
Comments
actually, it looks like pypowervm will be held back because it has a cap on taskflow now. |
* Update requirements from branch 'master' - Merge "Block pypowervm 1.1.21" - Block pypowervm 1.1.21 It includes a cap on taskflow, blocking updates. powervm/pypowervm#12 Change-Id: I88a21382a147ef79fd773574ec98fd59ba7d198a
It includes a cap on taskflow, blocking updates. powervm/pypowervm#12 Change-Id: I88a21382a147ef79fd773574ec98fd59ba7d198a
* Update requirements from branch 'master' - Merge "Updated from generate-constraints" - Updated from generate-constraints -grpcio===1.21.1 +grpcio===1.15.0 taskflow email, needs a release as well to unblock -pypowervm===1.1.21 +pypowervm===1.1.20 powervm/pypowervm#12 - will mask the bad version -tornado===5.1.1;python_version=='2.7' +tornado===4.5.3;python_version=='2.7' py27 keeps pulling in too new versions, will need to either maintain a secondary requirements list for for py27 caps in constraints only libraries (those not tracked by global-requirements.txt). -urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1 openshift is capping things, they don't seem to want to change perhaps we should request that the only two projects using openshift to not use it anymore. openstack/kuryr-tempest-plugin x/flame -jsonschema===3.0.1 +jsonschema===2.6.0 bunch of stuff in openstack still has a cap -fasteners===0.15 +fasteners===0.14.1 harlowja/fasteners#36 Change-Id: Ida5b084be8b68c0eaa021f548199ad477398e008
-grpcio===1.21.1 +grpcio===1.15.0 taskflow email, needs a release as well to unblock -pypowervm===1.1.21 +pypowervm===1.1.20 powervm/pypowervm#12 - will mask the bad version -tornado===5.1.1;python_version=='2.7' +tornado===4.5.3;python_version=='2.7' py27 keeps pulling in too new versions, will need to either maintain a secondary requirements list for for py27 caps in constraints only libraries (those not tracked by global-requirements.txt). -urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1 openshift is capping things, they don't seem to want to change perhaps we should request that the only two projects using openshift to not use it anymore. openstack/kuryr-tempest-plugin x/flame -jsonschema===3.0.1 +jsonschema===2.6.0 bunch of stuff in openstack still has a cap -fasteners===0.15 +fasteners===0.14.1 harlowja/fasteners#36 Change-Id: Ida5b084be8b68c0eaa021f548199ad477398e008
any update on this? |
no response to upstream issue powervm/pypowervm#12 Change-Id: I57bd21ecbc53380114b163b482b74056c6f64428
* Update requirements from branch 'master' - Merge "block pypowervm===1.1.22 for capping taskflow" - block pypowervm===1.1.22 for capping taskflow no response to upstream issue powervm/pypowervm#12 Change-Id: I57bd21ecbc53380114b163b482b74056c6f64428
@prometheanfire I'm still getting notified on this repo, but I no longer have the access/ability to do anything about these issues. The powervm team, such as it is, conducts meetings in #openstack-powervm [1]. That looks like it's probably an inconvenient time for you, but it may give you a clue who to stalk in that channel. You might also get some mileage by emailing the powervm CI address, listed here [2]. Assuming there are still warm bodies at the other end, they should be (or at least be able to connect you to) the same people who maintain pypowervm. Good luck, [1] http://eavesdrop.openstack.org/meetings/openstack_powervm/2019/openstack_powervm.2019-07-10-09.04.log.html |
-grpcio===1.21.1 +grpcio===1.15.0 taskflow email, needs a release as well to unblock -pypowervm===1.1.21 +pypowervm===1.1.20 powervm/pypowervm#12 - will mask the bad version -tornado===5.1.1;python_version=='2.7' +tornado===4.5.3;python_version=='2.7' py27 keeps pulling in too new versions, will need to either maintain a secondary requirements list for for py27 caps in constraints only libraries (those not tracked by global-requirements.txt). -urllib3===1.25.3 +urllib3===1.24.3 -kubernetes===9.0.0 +kubernetes===8.0.1 openshift is capping things, they don't seem to want to change perhaps we should request that the only two projects using openshift to not use it anymore. openstack/kuryr-tempest-plugin x/flame -jsonschema===3.0.1 +jsonschema===2.6.0 bunch of stuff in openstack still has a cap -fasteners===0.15 +fasteners===0.14.1 harlowja/fasteners#36 Change-Id: Ida5b084be8b68c0eaa021f548199ad477398e008
-grpcio===1.21.1 +grpcio===1.15.0 taskflow email, needs a release as well to unblock -pypowervm===1.1.21 +pypowervm===1.1.20 powervm/pypowervm#12 - will mask the bad version -tornado===5.1.1;python_version=='2.7' +tornado===4.5.3;python_version=='2.7' py27 keeps pulling in too new versions, will need to either maintain a secondary requirements list for for py27 caps in constraints only libraries (those not tracked by global-requirements.txt). -kubernetes===9.0.0 +kubernetes===8.0.1 openshift is capping things, they don't seem to want to change perhaps we should request that the only two projects using openshift to not use it anymore. openstack/kuryr-tempest-plugin x/flame -jsonschema===3.0.1 +jsonschema===2.6.0 bunch of stuff in openstack still has a cap -fasteners===0.15 +fasteners===0.14.1 harlowja/fasteners#36 Change-Id: Ida5b084be8b68c0eaa021f548199ad477398e008
It includes a cap on taskflow, blocking updates. powervm/pypowervm#12 Change-Id: I88a21382a147ef79fd773574ec98fd59ba7d198a
see http://logs.openstack.org/29/661429/4/check/requirements-tox-py27-check-uc/293a0e7/job-output.txt.gz#_2019-05-27_00_37_29_789938 while the logs last
The text was updated successfully, but these errors were encountered: