Bug 907871

Summary:	no check prevents deletion of router interface needed by a floating ip
Product:	Red Hat OpenStack	Reporter:	Gary Kotton <gkotton>
Component:	openstack-quantum	Assignee:	Gary Kotton <gkotton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0 (Folsom)	CC:	chrisw, ykaul
Target Milestone:	snapshot3	Keywords:	Rebase, Triaged
Target Release:	2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-28 14:41:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gary Kotton 2013-02-05 12:46:36 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 Ofer Blaut 2013-03-11 14:50:04 UTC

already tested , can't delete router when associated ip is used 


quantum router-gateway-clear 835ffa1f-4aab-44f1-a0b6-c5292fa0ebb4
Gateway cannot be updated for router 835ffa1f-4aab-44f1-a0b6-c5292fa0ebb4, since a gateway to external network 84e146ef-da0d-4369-98d5-9217536c4794 is required by one or more floating IPs.

quantum router-delete 835ffa1f-4aab-44f1-a0b6-c5292fa0ebb4
Router 835ffa1f-4aab-44f1-a0b6-c5292fa0ebb4 still has active ports


openstack-quantum-2012.2.3-5.el6ost.noarch