Bug 907872 - Update router gateway successful with existed floatingip association
Summary: Update router gateway successful with existed floatingip association
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: snapshot3
: 2.1
Assignee: Gary Kotton
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 12:48 UTC by Gary Kotton
Modified: 2016-04-26 17:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-28 14:41:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1081877 0 None None None Never

Description Gary Kotton 2013-02-05 12:48:00 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:45:35 UTC 
Tested

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.


User can't clear router-gateway-clear while floating ip associate 

openstack-quantum-2012.2.3-5.el6ost.noarch
Note You need to log in before you can comment on or make changes to this bug.