run-upgrade/plays should remove existing rpc_release.link

[Bjoern]

If you upgrade from a lower OSAD version, the old rpc_release.link pip repo file is still sourced into the pip.conf and you end up with the new repo VIP and the old repository as backup.
Neither one is good if you use the run-upgrade.sh since you can't interrupt the execution to actually generate a F5 config containing the frozen repo VIP. (Opened a different bug, because the rpc_f5_config.sh script does not generate a port 8181 VIP)

Failed config :

find-links =
http://172.29.236.10:8181/os-releases/kilo/
https://mirror.rackspace.com/rackspaceprivatecloud/python_packages/10.1.4/

[Kevin Carter (kevin-carter)]

From bug triage meeting:

[05.05.15-11:11:05] <cloudnull> while it was left for redundancy in an environment that may be running "other" links besides what we use upstream, it seems that its not something that we need.
[05.05.15-11:11:35] <cloudnull> and removing the rpc_release.link file shouldn't impact any other links that may be present.
[05.05.15-11:14:17] <cloudnull> i think we can do something like # ansible hosts:all_containers -m shell -a "rm /root/.pip/links.d/rpc_release.link" somewhere around https://github.com/stackforge/os-ansible-deployment/blob/master/scripts/run-upgrade.sh#L291 and it should be all good.

[Kevin Carter (kevin-carter)]

Kilo fix: https://review.openstack.org/#/c/196497/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/196497
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=a6222b1dda6218d354da372eb1b2b4357d9ed2fd
Submitter: Jenkins
Branch: kilo

commit a6222b1dda6218d354da372eb1b2b4357d9ed2fd
Author: kevin <email address hidden>
Date: Fri Jun 26 16:00:56 2015 -0500

    Remove all of the rpc_release.link files

    This removes the link files that are powering the basic pip config
    thoughout the stack. The removal is to ensure that there are no
    conflicting sources of truth when upgrading from Juno.

    Closes-Bug: #1450580
    Change-Id: I074f46c9b35793b35cf22ab49dd97f938df0cfac
    (cherry picked from commit 0f4b5c9e6e96189a2404a40d45bdc78419b264f7)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.