Bug 1381487

Summary: Instance creation getting failed becase of "Timeout waiting for vif plugging callback"
Product: Red Hat OpenStack Reporter: VIKRANT <vaggarwa>
Component: openstack-neutronAssignee: Jakub Libosvar <jlibosva>
Status: CLOSED NOTABUG QA Contact: Toni Freger <tfreger>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0 (RHEL 6)CC: amuller, chrisw, nyechiel, srevivo, vaggarwa
Target Milestone: async   
Target Release: 5.0 (RHEL 6)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-09 09:18:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description VIKRANT 2016-10-04 09:23:54 UTC 
Description of problem:

Instance creation getting failed becase of "Timeout waiting for vif plugging callback"

Version-Release number of selected component (if applicable):
OSP 5 on RHEL 6

How reproducible:
Everytime for cu. 

Steps to Reproduce:
1. Try to spawn an instance. It's getting stuck in BUILD state for 5 mins and eventually ending in error state.
2. Call trace seen is similar to one mentioned in solution [a]

[a] https://access.redhat.com/solutions/1256593

Actual results:
Instance is getting into ERROR state. 

Expected results:
Instance should get successfully completed.

Additional info:

Provider network based setup.
Comment 3 Assaf Muller 2016-10-04 12:05:18 UTC 
We need a full sos report from the relevant compute and controllers.
Comment 4 Assaf Muller 2016-10-04 12:06:07 UTC 
Please confirm this is an OSP 5 install on RHEL 6. Additionally, is there a customer ticket attached?
Comment 11 VIKRANT 2016-10-09 03:43:32 UTC 
After restarting openvswitch agent on problematic compute node. Instance started taking ip address without any issue, we are good to close this Bug.
Comment 12 Nir Yechiel 2016-10-09 09:18:48 UTC 
Closing as per comment #11.