Bug 2135363 - The multiple VM creation via templates fail with error ` nova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed`
Summary: The multiple VM creation via templates fail with error ` nova.exception.Virtu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.2 (Train)
Hardware: All
OS: All
urgent
high
Target Milestone: ---
: ---
Assignee: Slawek Kaplonski
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-17 11:37 UTC by Shailesh Chhabdiya
Modified: 2023-06-29 06:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-29 06:11:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-19471 0 None None None 2022-10-17 11:46:20 UTC

Description Shailesh Chhabdiya 2022-10-17 11:37:02 UTC
Description of problem:
Multiple VM creation in a single go fails with error mentioned in summary

The failure is not constant its always random

Version-Release number of selected component (if applicable):
RHOSP16.2.2
CISCO APIC SDN

How reproducible:
ALways 

Steps to Reproduce:
1. Create VM via templates 
2. atleast 2 VM creation fails always
3.

Actual results:
VM creation fails

Expected results:
VM creation should be completed successfully

Comment 5 Brendan Shephard 2022-10-18 06:34:00 UTC
To summarise my understanding here. From Cisco's perspective, it seems their investigation shows that the port was configured, added to the DB and then we reached this point at which a message should have been published on the Message bus (RabbitMQ):
https://github.com/openstack/neutron/blob/stable/train/neutron/db/provisioning_blocks.py#L140-L145

Which is done by neutron-lib:
https://github.com/openstack/neutron-lib/blob/stable/train/neutron_lib/callbacks/registry.py#L59-L60

So assuming that all worked up until that point, then there could have been some issue with RabbitMQ during that time that prevented the message being published or received by Nova.

Can you verify if there are any RabbitMQ issues seen during the time of the error? Last time this issue come up, I called out errors that were seen with RMQ as well. So it could be the case here too:
https://bugzilla.redhat.com/show_bug.cgi?id=2082009#c4


Adding in PIDONE as FYI if we need to go down the RMQ route.


Note You need to log in before you can comment on or make changes to this bug.