Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1469680

Summary: Remove the gateway of external net won't affect router
Product: Red Hat OpenStack Reporter: Brian Haley <bhaley>
Component: openstack-neutronAssignee: Brian Haley <bhaley>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: amuller, chrisw, jjoyce, nyechiel, srevivo
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-9.4.0-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-06 17:17:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian Haley 2017-07-11 15:39:54 UTC 
Cloned from launchpad bug 1520775.

Description:

I found this one when build up a test env.

Steps to reproduce:
1) I create a set of external network, internal network and router. The external network has gateway ip in its subnet.
2) connect the external, internal network and router, by using router-gateway-set, router-interface-add.
3) Then I realize my physical network doesn't have a gateway. So I update the subnet of external network with --no-gateway.
4) I can't see the default route be deleted in router namespace, even if I restart l3-agent.


I try it in legacy router and DVR, they both have this problem, and I believe HA router will have this problem.

Specification URL (additional information):

https://bugs.launchpad.net/neutron/+bug/1520775
Comment 2 Brian Haley 2017-07-14 20:39:40 UTC 
https://code.engineering.redhat.com/gerrit/112357
Comment 5 errata-xmlrpc 2017-09-06 17:17:18 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/RHBA-2017:2663