← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1760584] Re: IpAddressGenerationFailure warning while running tempest test test_create_subnet_from_pool_with_subnet_cidr

 

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1760584

Title:
  IpAddressGenerationFailure warning while running  tempest test
  test_create_subnet_from_pool_with_subnet_cidr

Status in neutron:
  Invalid
Status in tempest:
  Invalid

Bug description:
  When I run tempest run

  neutron.tests.tempest.api.test_subnetpools.SubnetPoolsTest.test_create_subnet_from_pool_with_subnet_cidr

  I see below warning in neutron-server
  Apr 02 08:46:28 test.rdocloud neutron-server[12690]: WARNING neutron.api.rpc.handlers.dhcp_rpc [None req-4bfb3f1d-659f-49b8-8572-c74e7d955731 None None] Action create_port for network 8e90dae6-018e-4979-bfad-2cc96e281ea8 could not complete successfully: No more IP addresses available on network 8e90dae6-018e-4979-bfad-2cc96e281ea8.: IpAddressGenerationFailure: No more IP addresses available on network 8e90dae6-018e-4979-bfad-2cc96e281ea8.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1760584/+subscriptions



References