Public bug reported:
During subnet update neutron validates, if gateway_ip is passed in the PUT
request and if it is, validates if old gateway_ip isn't already allocated to
some router's port. If it is, Neutron will forbid to update subnet.
That's totally valid behavior but in case when "new" gateway_ip is actually the
same as old one Neutron should not raise exception and allow to update subnet.
It may be useful for example for some automation tools, like Heat and Tripleo
which will not need to have additional logic to check if gateway_ip is actually
changed or not and if it should be eventually cleaned manually.
** Affects: neutron
Importance: Low
Assignee: Slawek Kaplonski (slaweq)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1955121
Title:
Update subnet with same gateway_ip as is already used should be
allowed
Status in neutron:
New
Bug description:
During subnet update neutron validates, if gateway_ip is passed in the PUT
request and if it is, validates if old gateway_ip isn't already allocated to
some router's port. If it is, Neutron will forbid to update subnet.
That's totally valid behavior but in case when "new" gateway_ip is actually
the same as old one Neutron should not raise exception and allow to update
subnet.
It may be useful for example for some automation tools, like Heat and Tripleo
which will not need to have additional logic to check if gateway_ip is actually
changed or not and if it should be eventually cleaned manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1955121/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
