5ce4d64150
Currently all pip install tasks only require the package to be present. This means that when an environment undergoes a minor upgrade the package is not upgraded to the same version that was tested with. This ultimately results in a deployed environment that does not match the tested environment. While for the services installed into venvs this is not an issue, it does affect those which do not use venvs and any packages which are installed outside of a venv or on top of a venv. This patch changes the behaviour to ensure that the install task will always use the latest available package. In developer_mode this will mean using the version specified in upper-constraints, and in an integrated build this will mean the version which is available in the wheel repo's folder for the tag. Change-Id: I22821cb24642aad4bface0ae0838351cd0cce257 |
||
|---|---|---|
| .. | ||
| main.yml | ||
| neutron_check.yml | ||
| neutron_db_setup.yml | ||
| neutron_install.yml | ||
| neutron_l3_ha.yml | ||
| neutron_lbaas.yml | ||
| neutron_post_install.yml | ||
| neutron_pre_install.yml | ||
| neutron_service_add.yml | ||
| neutron_service_setup.yml | ||
| neutron_upstart_common_init.yml | ||
| neutron_upstart_init.yml | ||
| nuage_neutron_config.yml | ||
| plumgrid_config.yml | ||