run-upgrade script assumes rings are locally held for deployment

[Bjoern]

At https://github.com/openstack/openstack-ansible/blob/kilo/scripts/run-upgrade.sh#L181 we do check for a local swift ring directory which is usually only present on the first swift object node.

Since the upgrade script is executed on the deployment host, the swift rings are not necessarily present on this machine.

Personally I can't find a reason why we even check this in the first place, checking the inventory for actual swift nodes seem sufficient.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: kilo
Review: https://review.openstack.org/280844

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/280844
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=99217b3aa1dc29fe939a6a9e21bec0407dd6fcd1
Submitter: Jenkins
Branch: kilo

commit 99217b3aa1dc29fe939a6a9e21bec0407dd6fcd1
Author: Bjoern Teipel <email address hidden>
Date: Tue Feb 16 11:39:55 2016 -0600

    Remove local swift ring directory check

    This fix will remove the local check for the swift ring directory.
    Assuming the upgrade script is executed on the deployment host,
    the swift ring files are not necessarily on this host, rather than
    the first swift server.

    Change-Id: Ie1f07a7884b669e2a0c44868711ce76070c8e4bf
    Closes-Bug: #1546225

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

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

[Doug Hellmann (doug-hellmann)]

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