Bug 1152579 - Deleting a network while a Load Balancer is still defined breaks the Load Balance GUI page.
Summary: Deleting a network while a Load Balancer is still defined breaks the Load Bal...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 5.0 (RHEL 7)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ga
: 7.0 (Kilo)
Assignee: John Schwarz
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-14 13:04 UTC by Andrew Spurrier
Modified: 2016-04-27 00:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the OpenStack Dashboard LBaaS pool details page would not correctly handle the unexpected case of the subnet attached to an LBaaS pool being deleted. Consequently, if you created a network, subnet, router, and load balancer, and then deleted the network, subnet, and router, but retained the load balancer, the OpenStack Dashboard LBaaS details page would return error 500. This update addresses this issue by checking for this scenario and displaying a warning message instead. As a result, the LBaaS details page now renders correctly and displays a warning as needed.
Clone Of:
Environment:
Last Closed: 2015-08-05 13:14:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 147790 0 None None None Never
OpenStack gerrit 174268 0 None None None Never
OpenStack gerrit 174384 0 None None None Never
Red Hat Product Errata RHEA-2015:1548 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 17:07:06 UTC

Description Andrew Spurrier 2014-10-14 13:04:44 UTC
Description of problem:  Deleting a network while a Load Balancer is still defined breaks the Load Balance GUI page.


Version-Release number of selected component (if applicable):
RHELOSP 5

How reproducible:  I imagine completely but I can't test it at this stage because I can not define any more Load Balancers!


Steps to Reproduce:
1.  Via the RHELOSP 5 Web interface
2. Define a network
3. Define a router
4. add an interface to the router
5. add a load balancer
6. delete the interface on the router
7. delete the router
8. delete the network 

Actual results:
The network is deleted and from now on the "Load Balancer" tab on the network page cannot be accessed.
 
> Something went wrong!
> 
> An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator.
> 
> Home
> 
> Help


Expected results:
Error reported that the network cannot be deleted while a "Load Balancer" is defined.

Additional info:

Comment 3 Nir Yechiel 2014-10-14 13:37:31 UTC
Hi Toni,

Can you please try to reproduce this issue? I am also interested to know what is the behavior in the CLI to determine if this is a Neutron issue or Horizon one.

Thanks,
Nir

Comment 4 lpeer 2015-01-15 09:53:16 UTC
Toni - can you please reproduce on OSP-6.

Comment 5 Toni Freger 2015-01-18 07:02:12 UTC
Have tested on RHEL7 the latest rhos6  

openstack-neutron-2014.2.1-6.el7ost.noarch
python-django-horizon-2014.2.1-5.el7ost.noarch

The issue has reproduced via Horizon.
In CLI the same behaviour, can delete network even the LB pool exists.

Comment 6 John Schwarz 2015-04-16 14:05:48 UTC
A patch which fixes the GUI error has been merged late January [1] by the community, so it should be fixed in OSP-7.

John.


[1]: https://review.openstack.org/#/c/147790/

Comment 7 Toni Freger 2015-06-07 16:32:13 UTC
Alex, please try to reproduce it on the latest puddle.
Pay attention it's LBaaS v1.

Thanks

Comment 8 Alexander Stafeyev 2015-06-11 06:26:01 UTC
verified on 
rhos 7 rhel 7.1

Comment 11 errata-xmlrpc 2015-08-05 13:14:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548


Note You need to log in before you can comment on or make changes to this bug.