The create_swift_rings_backup_container_plan workflow fails if the container already exists

[Dougal Matthews]

The create_swift_rings_backup_container_plan workflow will fail on a second run because it checks for the incorrect container name.

This problem likely happened because we conflate "plan name" and "container name".

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/526462

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/526462
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=4ad2410d68c535d7833797028e3107489f7f37cb
Submitter: Zuul
Branch: master

commit 4ad2410d68c535d7833797028e3107489f7f37cb
Author: Dougal Matthews <email address hidden>
Date: Thu Dec 7 17:09:52 2017 +0000

    Correct the container name confusion in the swift rings workflow

    The create_swift_rings_backup_container_plan workflow switches between
    using the overcloud swift container and the overcloud-swift-rings
    container (if given the input "overcloud"). This patch determines the
    container name in one place and updates all uses.

    While refactoring it also removes the duplication of the
    swift-rings.tar.gz file name.

    Closes-Bug: #1736998
    Change-Id: I5f988b003ed9600a530868dedc911a4f1333e730

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 8.3.0 release.