Add missing try/except to extension_supported call in Ports

[Rob Cresswell]

The Ports forms make Neutron api calls ('is_extension_supported') without proper Exception handling

[Itxaka Serrano (itxaka)]

Seems that this affects other components.

Im wondering, wouldnt it be easier to modify the actual api.neutron.is_extension_supported call with a try/catch + logging, returns False if an Exception is raised?

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/324095
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c704623cceb2122814a6933d9aac47a845ef9bf9
Submitter: Jenkins
Branch: master

commit c704623cceb2122814a6933d9aac47a845ef9bf9
Author: Ankur Gupta <email address hidden>
Date: Wed Jun 1 15:22:34 2016 -0500

    Add Try/Exception to Extension Supported call in Ports

    The port form makes 2 Neutron api calls ('is_extension_supported')
    without proper exception handling.

    Placed each call within try/except block. For admin and project
    dashboards.

    Potential solution posed by itxakaserrano is to make the actual
    Neutron api call try/catch with logging and return the
    Exception if raised.

    Change-Id: I357175e4be43b09dfa74ffe8a1d2c8c7ea49ce93
    Closes-Bug: #1434116

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.