IpAddressGenerationFailure warning while running tempest test test_create_subnet_from_pool_with_subnet_cidr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Medium
|
Unassigned | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When I run tempest run
neutron.
I see below warning in neutron-server
Apr 02 08:46:28 test.rdocloud neutron-
This test tries to create a subnet with cidr 10.11.12.0/31 i.e only one address to allocate(which will be taken for gateway_ip). This subnet creation will notify dhcp agent, which will try to create a dhcp port but will fail as there are no address available. Still the subnet create api will be successful as port creation is triggered later from dhcp agent.
These tests may fail with vendor's drivers if their implementation try to create dhcp port as part of subnet creation. There is no point in creating a subnet with no IP address. Better to change the tempest tests to provide CIDR with adequate addresses.
Changed in neutron: | |
status: | Confirmed → Invalid |
The other option is to pass "disable-dhcp" when creating the subnet. I guess I would prefer this since technically a /31 is valid for a subnet (point to point links).
We would just have to add this to the body in the API call:
'enable_dhcp': False