yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53294
[Bug 1353962] Re: Test job fails with FixedIpLimitExceeded with nova network
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: Medium => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1353962
Title:
Test job fails with FixedIpLimitExceeded with nova network
Status in OpenStack Compute (nova):
Expired
Status in tempest:
Invalid
Bug description:
VM creation failed due to a `shortage` in fixed IP.
The fixed range is /24, tempest normally does not keeps up more than
~8 VM.
message: "FixedIpLimitExceeded" AND filename:"logs/screen-n-net.txt"
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkZpeGVkSXBMaW1pdEV4Y2VlZGVkXCIgQU5EIGZpbGVuYW1lOlwibG9ncy9zY3JlZW4tbi1uZXQudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MDc0MTA0MzE3MTgsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0=
http://logs.openstack.org/23/112523/1/check/check-tempest-dsvm-
postgres-
full/acac6d9/logs/screen-n-cpu.txt.gz#_2014-08-07_09_42_18_481
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1353962/+subscriptions
References