Scoping not respecting scope defined order

[Joshua Harlow]

When look-up is occurring the possible provider ordering is used instead of the scope defined provider ordering. This causes incorrect matches when look-up argument names that are produced by multiple providers (all providing the same argument name); the scope order should be enforced as the de-facto order and not the order that the storage unit finds (which is hash based and varies depending on hash ordering).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/158956
Committed: https://git.openstack.org/cgit/openstack/taskflow/commit/?id=0a97fb96b5057bcde31b3373a444b531d8d9ee82
Submitter: Jenkins
Branch: master

commit 0a97fb96b5057bcde31b3373a444b531d8d9ee82
Author: Joshua Harlow <email address hidden>
Date: Tue Feb 24 16:19:04 2015 -0800

    Fix lookup scoping multi-match ordering

    When look-up is occurring the possible provider
    ordering is used instead of the scope returned provider
    ordering. This causes incorrect matches when look-up
    argument names that are produced by multiple providers (at
    the same scope level) all providing the same requirement
    name.

    The scope order should be enforced as the de-facto order
    and not the order that the storage unit finds (which is
    hash based and varies depending on hash ordering).

    Closes-Bug: #1425326

    Change-Id: I15f1ee5515758bdc470c0f7dd7a2f616923e5628