Comment 4 for bug 1539236

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-lxc_hosts (master)

Reviewed: https://review.openstack.org/289339
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=45beccf508b9fcd31d85e0895efc1efaac0e2032
Submitter: Jenkins
Branch: master

commit 45beccf508b9fcd31d85e0895efc1efaac0e2032
Author: Jesse Pretorius <email address hidden>
Date: Mon Mar 7 13:35:08 2016 +0000

    Always ensure that the local lxc cache file matches the upstream image

    Ansible 1.9x only actually checks whether there's a local file - it never
    checks whether the local file matches the given sha256sum.

    We therefore need to set 'force:yes' to ensure that Ansible does the
    following:
     - download the file to a temporary location, checking its sha256sum
       against the given value
     - check the sha256sum of the existing file and the downloaded file
     - if the sha256sums match, then throw away the temp file
     - if the sha256sums do not match, replace the existing file

    In order to also provide the ability to forcibly delete any existing lxc
    cache which was previously prepared (successfully or unsuccessfully), the
    boolean variable 'lxc_container_base_delete' has been added.

    Change-Id: I988940892c89679edea887716851314fc1cf13b5
    Closes-Bug: #1539236