create subnet doesn't calculate DHCP pool

Bug #1553972 reported by Martin Pavlásek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Expired
Undecided
Unassigned

Bug Description

Description of problem:
Later updated subnet gateway leads to IP address conflict with DHCP pool range.

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, gateway IP 10.0.0.1, Next, leave Allocation Pools unchanged

Actual results:
Allocation pools is blank

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

Revision history for this message
Kevin Chen (kevchentw) wrote :

It didn't happened to me.

I got the result of
IP allocation pool Start 10.0.0.2 - End 10.0.0.254
when network address 10.0.0.0/24, IPv4, gateway IP 10.0.0.1

Revision history for this message
Rahul U Nair (rahulunair) wrote :

Could you please go through the client and try to do this and paste the logs so that we can see whats going on, also which version of OpenStack are you using?

Changed in horizon:
status: New → Incomplete
hanjiabao (hanjiabao)
Changed in horizon:
assignee: nobody → hanjiabao (hanjiabao)
hanjiabao (hanjiabao)
Changed in horizon:
assignee: hanjiabao (hanjiabao) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]

Changed in horizon:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.