preparing v1 manifest images fails

[Steve Baker]

quay.io serves v1 manifests instead of the v2 manifests served by most other registries. The prepare code is v1 aware, but there are a couple of issues causing errors, specifically:
- copying an image from a v1 registry
- deleting a v1 image from the image-serve directory

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit c7ffea0745b068190c80d70dd1f9e9654ac8096f
Author: Steve Baker <email address hidden>
Date: Tue Apr 9 13:01:59 2019 +1200

    Fix support for v1 manifests

    v1 manifests store the layer digests in a different way, which the
    prepare code has conditional logic to handle, however this is missing
    from image copy when discovering source layer digests.

    There is also a v1 manifest format error in the image export delete code.

    This change fixes both of these issues, which should make it possible
    to copy images from quay.io.

    Change-Id: I3e6c95beb387dc4b462eb037eeb8cb628016b7e4
    Closes-Bug: #1823821

[OpenStack Infra (hudson-openstack)]

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