Bug 1314338

Summary: update subnet gateway cause wrong DHCP pool calculation
Product: Red Hat OpenStack Reporter: Martin Pavlásek <mpavlase>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED WONTFIX QA Contact: Toni Freger <tfreger>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: amuller, aortega, athomas, chrisw, mrunge, nyechiel, srevivo
Target Milestone: ---Keywords: ZStream
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-07 23:28:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Pavlásek 2016-03-03 12:29:01 UTC 
Description of problem:
Later updated subnet gateway leads to IP address conflict with DHCP pool range.

Version-Release number of selected component (if applicable):
RHEL 7.2
python-django-horizon-8.0.1-1.el7ost.noarch
openstack-dashboard-8.0.1-1.el7ost.noarch
openstack-packstack-puppet-7.0.0-0.12.dev1699.g8f54936.el7ost.noarch
openstack-neutron-common-7.0.1-10.el7ost.noarch
openstack-neutron-ml2-7.0.1-10.el7ost.noarch
openstack-neutron-7.0.1-10.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
Log in as demo user.
1. Project - Network - Networks - Create Network
2. network "test_net", subnet "test_subnet", network address 10.0.0.0/24, IPv4, tick Disable Gateway, Create
3. click to test_net row, click to Edit Subnet for test_subnet row
4. untick Disable Gateway, gateway IP 10.0.0.1, Next, leave Allocation Pools unchanged, Save

Actual results:
Computed Allocation pools is "10.0.0.1,10.0.0.254", click to Save cause red alert:
Error: Failed to update subnet "10.0.0.0/24": Gateway ip 10.0.0.1 conflicts with allocation pool 10.0.0.1-10.0.0.254

Expected results:
it should exclude the IP of gateway from the DHCP pool, so:
10.0.0.2,10.0.0.254

Additional info:
Comment 2 Matthias Runge 2016-04-07 08:30:49 UTC 
According to upstream bug, it's actually a bug in neutron.
Comment 3 Assaf Muller 2016-06-07 23:28:54 UTC 
The issue is not significant enough to justify the devotion of development resources. I'd rather close the bug than keep it open without any traction for years.