Bug 1469680 - Remove the gateway of external net won't affect router
Summary: Remove the gateway of external net won't affect router
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z4
: 10.0 (Newton)
Assignee: Brian Haley
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-11 15:39 UTC by Brian Haley
Modified: 2017-09-06 17:17 UTC (History)
5 users (show)

Fixed In Version: openstack-neutron-9.4.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 17:17:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1520775 0 None None None 2017-07-11 15:39:58 UTC
Red Hat Product Errata RHBA-2017:2663 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-09-06 20:58:42 UTC

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


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