multiple tempest failures due to failure to allocate networks

Bug #1971466 reported by Alexander Balderson
14
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.

Crashdump at:
https://oil-jenkins.canonical.com/artifacts/f4039563-7faf-4865-b4dc-447ccf991cc5/generated/generated/openstack/juju-crashdump-openstack-2022-05-03-12.21.15.tar.gz

tags: added: cdo-tempest
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.