Bug 1381487 - Instance creation getting failed becase of "Timeout waiting for vif plugging callback"
Summary: Instance creation getting failed becase of "Timeout waiting for vif plugging ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 5.0 (RHEL 6)
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: async
: 5.0 (RHEL 6)
Assignee: Jakub Libosvar
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 09:23 UTC by VIKRANT
Modified: 2019-12-16 06:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-09 09:18:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.