pip conf not correctly building

Created by: BjoernT

In case of the Juno (10.1.16) to Kilo upgrade (r11.1.0rc3), the upgrade script stopped because of a trusty backport repo issue so we continued running the setup-infrastructure and openstack-setup.yml playbooks. After that I wanted to run setup-maas but realized that the pip.conf was missing the link:

http://172.29.236.207:8181/rpc-releases/r11.1.0rc3/

so I rerun repo-pip-setup.yml which now created a more correct pip.conf but the rpc-release version is now wrong:

find-links = http://172.29.236.207:8181/rpc-releases/r11.1.0rc2/ http://172.29.236.207:8181/os-releases/11.2.4/

The reason for this is group_vars/all.yml contains the wrong version at rpc_release

This is more so an issue when running OSA playbooks which can rewrite the pip.conf removing the rpc-releases link again

Imported comments:

By byronmccollum on 2015-11-17 22:14:36 UTC

rpc_release is incorrect for tags r11.1.0rc3 and r11.0.3...

By BjoernT on 2015-11-20 21:31:57 UTC

There is actually another issue, the rpc_release.link seems to grow instead of being replaced with a new release information and you end up with multiple releases inside the pip.conf: I can image this being a problem when we downgraded packages in new releases..

[global] no-index = True pre = True timeout = 120 trusted-host = 172.29.236.207

[install] upgrade = True allow_all_external = True find-links = http://172.29.236.207:8181/rpc-releases/r11.1.0rc3/ http://172.29.236.207:8181/rpc-releases/r11.1.0rc2/ http://172.29.236.207:8181/os-releases/11.2.4/