yahoo-eng-team team mailing list archive

[Vishal Agarwal <vishala@xxxxxx>]

Public bug reported:

I am trying below scenario:-
1.	Create one external network i.e. with router:external=True option.
2.	Create one subnet under the above network with gateway-ip provided.
3.	Create one router.
4.	Issue command “neutron router-gateway-set <routerID-point3 above>  <networkID-point1 above>”
5.	Update the subnet in point2 above with new gateway IP i.e “neutron subnet-update <subnetID-point2>  --gateway-ip <newIP>”
6.	I can see success-full subnet updated response on cli.
7.	For validating the changed gateway-ip I verified router namespace present on Network node by using command “ip netns exec <router-namespace-point3> route -n”. But in the output the new gateway-ip is not updated it is still showing the old one.

Brief about my setup:-
1.	It has one controller node, one Network node and 2 Compute nodes.
2.	I am on Icehouse-GA. 

If the Subnet update API does not have a constraint to prevent the
change then the L3 agent should affect it properly.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-ipam-dhcp

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1317363

Title:
  Unable to update external network subnet's gateway-ip

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I am trying below scenario:-
  1.	Create one external network i.e. with router:external=True option.
  2.	Create one subnet under the above network with gateway-ip provided.
  3.	Create one router.
  4.	Issue command “neutron router-gateway-set <routerID-point3 above>  <networkID-point1 above>”
  5.	Update the subnet in point2 above with new gateway IP i.e “neutron subnet-update <subnetID-point2>  --gateway-ip <newIP>”
  6.	I can see success-full subnet updated response on cli.
  7.	For validating the changed gateway-ip I verified router namespace present on Network node by using command “ip netns exec <router-namespace-point3> route -n”. But in the output the new gateway-ip is not updated it is still showing the old one.

  Brief about my setup:-
  1.	It has one controller node, one Network node and 2 Compute nodes.
  2.	I am on Icehouse-GA. 

  If the Subnet update API does not have a constraint to prevent the
  change then the L3 agent should affect it properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1317363/+subscriptions