Bug 2033584 - Update subnet with same gateway_ip as is already used should be allowed
Summary: Update subnet with same gateway_ip as is already used should be allowed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Slawek Kaplonski
QA Contact: Bharath M V
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-17 11:08 UTC by Slawek Kaplonski
Modified: 2022-03-24 10:56 UTC (History)
4 users (show)

Fixed In Version: openstack-neutron-15.2.1-1.20211222153343.40d217c.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-24 10:56:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1955121 0 None None None 2021-12-20 14:58:47 UTC
OpenStack gerrit 822098 0 None NEW Don't fail subnet validation if gw_ip is actually not changed 2021-12-20 14:58:47 UTC
Red Hat Issue Tracker OSP-11874 0 None None None 2021-12-17 11:10:25 UTC
Red Hat Product Errata RHSA-2022:0990 0 None None None 2022-03-24 10:56:43 UTC

Description Slawek Kaplonski 2021-12-17 11:08:27 UTC
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.

This came from the bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2032295

Comment 9 errata-xmlrpc 2022-03-24 10:56:13 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 (Moderate: Red Hat OpenStack Platform 16.1 (openstack-neutron) security update), 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/RHSA-2022:0990


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