DB migration doesn't seem to handle metadata encryption

[Stuart McLaren]

As far as I can tell from the code, this function:

'migrate_location_credentials'

in "glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py"
doesn't check to see if the location is encrypted using the metadata_encryption_key parameter.
So if the location is encrypted the new fix_uri_credentials edit won't be applied.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/19418
Committed: http://github.com/openstack/glance/commit/fad36d8ef79e52d8bf67c89bde876911990abf8f
Submitter: Jenkins
Branch: master

commit fad36d8ef79e52d8bf67c89bde876911990abf8f
Author: Alex Meade <email address hidden>
Date: Thu Jan 10 12:24:02 2013 -0500

    Add migration to quote encrypted image location urls

    Migration 015_quote_swift_credentials.py failed to take into account
    encrypted location values. This patch adds a similar migration
    that if the value is encrypted then:
    1. Decrypts the value
    2. Quotes the url string
    3. Encrypts the value
    4. Inserts back into DB

    fixes bug 1081043

    Change-Id: Iadfe5f5082b3932307eef8e76571e36c6ff9fce7