swift erasure encoding library installation failures

[Matt Thompson]

In kilo, we're getting a gate failure attempting to install swift dependencies:

2015-04-24 13:28:33,706 p=10156 u=root | failed: [aio1] => (item=curl,gcc,git-core,liberasurecode1,liberasurecode-dev,libffi-dev,openssh-server,python-dev,rsync) => {"attempts": 5, "failed": true, "item": "curl,gcc,git-core,liberasurecode1,liberasurecode-dev,libffi-dev,openssh-server,python-dev,rsync"}

We've narrowed this down to HP cloud not having the Ubuntu backports repo defined in apt sources.

[OpenStack Infra (hudson-openstack)]

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

commit 39bab4d683171e688a32d9437800d16e20b6b1e7
Author: Kevin Carter <email address hidden>
Date: Tue Apr 21 18:02:50 2015 -0500

    Add release pinning to galera roles

    As both Ubuntu and the MariaDB repositories carry packages with the same
    names, apt package pinning is required to ensure that the packages we install
    come from the right repository. This patch adds a pinning preference file to
    ensure that the packages we install come from the MariaDB repository.

    Due to the OpenStack CI images having conflicting packages installed in the
    base image, this patch also includes the removal of these packages during the
    AIO bootstrap to ensure that the deployment succeeds.

    For environments where the same two packages are installed on the hosts prior
    to the deployment of os-ansible-deployment, they would need to ensure that the
    packages are removed first. This has been seen in environments where
    monitoring tooling has installed the packages as a dependancy.

    Also, the swift installation process requires access to the Ubuntu backports
    repository to install the liberasurecode1 and liberasurecode-dev packages. In
    the hpcloud environments used in OpenStack-CI the backport repository is not
    implemented, so we need to ensure that it's there if it hasn't already been
    configured. This patch does that as part of the AIO bootstrap process.

    Finally, this patch also updates the global requirements and the sha's for all
    openstack branches that we're pinned to.

    Closes-Bug: #1446772
    Closes-Bug: #1448152
    Change-Id: I5ad0b9010e49832c4f866c0b141e1c035d5f9268
    (cherry picked from commit 886fe01edb01b9f21e3576f50711738687b236d9)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/177284
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=bdee1d5ac8ef50c33a821fec19d9f3c7002f237f
Submitter: Jenkins
Branch: master

commit bdee1d5ac8ef50c33a821fec19d9f3c7002f237f
Author: Jesse Pretorius <email address hidden>
Date: Fri Apr 24 15:22:02 2015 +0100

    Add ubuntu backports repository to AIO if it's not present

    The swift installation process requires access to the Ubuntu backports
    repository to install the liberasurecode1 and liberasurecode-dev packages. In
    the hpcloud environments used in OpenStack-CI the backport repository is not
    implemented, so we need to ensure that it's there if it hasn't already been
    configured. This patch does that as part of the AIO bootstrap process.

    Additionally, heat now requires python-saharaclient >= 0.9.0 and we bump here
    to allow heat to install successfully.

    Note that both issues are causing the gate to fail and need to be addressed
    together to get a successful gate.

    Closes-Bug: #1448126
    Closes-Bug: #1448152
    Change-Id: I5d8c6f4eb7182129ab22defd70a50d78e7ffe86f

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Kevin Carter (<email address hidden>) on branch: kilo
Review: https://review.openstack.org/177782
Reason: This was abandoned due to the change being moved into a different commit.

[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.