Open Stack

Hi Carl,

Thanks for the response. The bug id is "Bug #1317363".

Regards,
Vishal

-----Original Message-----
From: Carl Baldwin [mailto:carl at ecbaldwin.net]
Sent: Wednesday, May 07, 2014 9:05 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][Subnet] Unable to update external network subnet's gateway-ip

Vishal,

I have not yet had the chance to try to replicate this bug in my environment.  Will you file this  as a bug?  Gateway IPs on external networks don't change much.  In most environments there is never a need to change the IP.  However, if the API does not have a constraint to prevent the change then the L3 agent should affect it properly.  We can discuss more in the bug report.

Could you reply with the bug number?  The L3 subteam will triage.

Carl

On Wed, May 7, 2014 at 12:58 AM, Vishal2 Agarwal <vishal2.agarwal at aricent.com> wrote:
> Hi All,
>
>
>
> I am trying below scenario, please let me know the correctness of the
> 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.
>
>
>
>
>
> Regards,
>
> Vishal
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be
> circulated or used for any purpose other than for what it is intended.
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying,
> altering, or disclosing the contents of this message. Aricent accepts
> no responsibility for loss or damage arising from the use of the
> information transmitted by this email including damage from virus."
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."