yahoo-eng-team team mailing list archive

[OpenStack Infra <1796565@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/608454
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4ae8850decc07b41aca3752a35ddbcc04b005628
Submitter: Zuul
Branch:    master

commit 4ae8850decc07b41aca3752a35ddbcc04b005628
Author: Gary Kotton <gkotton@xxxxxxxxxx>
Date:   Sun Oct 7 07:03:07 2018 -0700

    Do not raise invalid message when port does not exist
    
    The exception handling for port, floating IP's or networks
    is too broad. Add specific error handling and in a case when
    the resource is not found do not raise a invalid message.
    
    Change-Id: I98ee2ff816c03980645752eebb4e39d3ecd2e158
    Closes-bug: #1796565


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1796565

Title:
  When deleting an instance the message "Unable to connect to Neutron"
  appears

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  This is due to the fact that the exception that is caught below is far too broad.
  https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/neutron.py#L1719
  In this specific case horizon is under load and neutron raises an exception that the port is not found.
  So the end user is complaining that irrelevant message are apprearing

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1796565/+subscriptions