browbeat dependencies conflict with its consumers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-browbeat |
Fix Released
|
Undecided
|
Aakarsh | ||
tripleo-quickstart |
New
|
Undecided
|
Unassigned |
Bug Description
As of today browbeat declared dependencies to pin ansible to an ancient version, also pinning few other dependencies without clear reasons for doing so.
This create dependency conflict with other openstack project that do use browbeat, like tripleo-quickstart which already requires an ansible version newer.
browbeat dependencies should use open ranges that require minimal known to work version and optionally ceiling maximum version but only when it is known that the newer version will broke
the product.
Example:
ansible>
python-
This would declare the fact that we know not to be working with 2.8.0 because of some changes made there.
For the specific case where a new minor release of a dependency breaks browbeat, we can use `fooo>=
Also, to prevent introducing conflicts due to wrong dependency declaration, we need to run "pip check" after installing depencies.
`pip check` report conflicts and return non-zero error code if any conflict is found.
Related to tripleo-quickstart https:/
affects: | openstack-browbeat → tripleo-quickstart |
affects: | tripleo-quickstart → openstack-browbeat |
description: | updated |
Changed in openstack-browbeat: | |
assignee: | nobody → Aakarsh (agopi) |
Changed in openstack-browbeat: | |
status: | New → In Progress |
https:/ /review. openstack. org/#/c/ 613588/ fixed the dependency issues, and https:/ /review. openstack. org/#/c/ 616677 will ensure that installing tripleo-quickstart would not pull in numpy, which is now an extra as it's only used for CLI cases to compare results.