Agent driver fails with Glance swift_store_multiple_containers_seed

[Josh Gachnang]

If the setting swift_store_multiple_containers_seed is set to a number greater than 0 in Glance, the agent driver will attempt to use the same container as if the number is 0, which won't exist and any images using that format will fail. The setting lets Glance shard the containers it stores the images in by appending the first "swift_store_multiple_containers_seed" characters to the images container name.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/149451
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=412878ebb59899282d8069be05c606398700437f
Submitter: Jenkins
Branch: master

commit 412878ebb59899282d8069be05c606398700437f
Author: Josh Gachnang <email address hidden>
Date: Thu Jan 22 17:22:09 2015 -0800

    Agent driver fails with Swift Multiple Containers

    Glance added a config called swift_store_multiple_containers_seed which
    uses part of the image UUID to determine which container to store an image
    in. If it is set to a number greater than 0, the Swift temporary URLs won't
    account for the new container name and fail to download to the agent.

    Option added in: https://github.com/openstack/glance_store/commit/
    3cd690b37dc9d935445aca0998e8aec34a3e3530

    Change-Id: I92fb9365c76ce92982accf8dec370b5781aacd50
    Closes-Bug: 1413825