multiple tempest failures due to failure to allocate networks
Bug #1971466 reported by
Alexander Balderson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
New
|
Undecided
|
Unassigned |
Bug Description
Starting with Focal Yoga
We have seen some cases where 10+ tempest tests fail because openstack is failing to create the instances for the test, reporting "failed to allocate network(s)"
In the crashdump attached:
Nova 3,4 shows multiple timeouts waiting for the interface.
Novas 1,4 shows a timeout waiting for a response from a message
Alex K suggested that this many timeouts may mean that rabbit is dropping messages, but nothing stands out in the rabbit logs.
tags: | added: cdo-tempest |
To post a comment you must log in.