Pecan: startup fails to associate plugins with some resources

[Salvatore Orlando]

In some cases, legit resources for supported extensions end up not having a plugin associated.

This happens because the startup process explicitly checks the supported_extension_aliases attribute, whereas it should instead do a deeper check leveraging the helper method get_supported_extension_aliases provided by the extension manager.

for instance the rbac extension will not work until this is fixed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/276707
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=517aa03da35fb4cfb3b16a5abbcc8115727b4a77
Submitter: Jenkins
Branch: master

commit 517aa03da35fb4cfb3b16a5abbcc8115727b4a77
Author: Salvatore Orlando <email address hidden>
Date: Fri Feb 5 03:29:57 2016 -0800

    Pecan: Fix association of plugins with resources

    The process was leveraing the supported_extension_aliases
    attribute, which might not provide a complete list of extension
    aliases.

    With this patch now Pecan leverages helper methods available
    in the extension manager, which have been slightly refactored in
    order to allow for retrieving aliases for a single plugin.

    Closes-Bug: #1542277

    Change-Id: Id944b27dcd84a92bf15242f5797408bf83b0d317

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/neutron 8.0.0.0b3 development milestone.