yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02097
[Bug 1102504] Re: Subnet creation (Quantum) defaults to mask /32
** Changed in: horizon/folsom
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1102504
Title:
Subnet creation (Quantum) defaults to mask /32
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in OpenStack Dashboard (Horizon) folsom series:
Fix Released
Bug description:
When creating a subnet during the network creation process, if the
user doesn't include a mask in the Network address field, the subnet
mask defaults to /32, making it impossible to allocate an IP when
launching an instance later on (Quantum logs:
IpAddressGenerationFailure No more IP addresses available on network).
It's easy to miss when creating a new network.
Steps to reproduce:
1. Go to the network page and create a new network
2. On the subnet page, specify an ip without a netmask
3. Try to launch an instance with that network
Actual results:
The subnet was created with a netmask of /32 and the instance errors.
Expected results:
Probably creating a subnet without a netmask should fail. Quantum does allow you to create a subnet with cidr /32, but because providing the netmask is mandatory this problem is less likely to happen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1102504/+subscriptions