Bug 1106374

Summary: Failed to lunch instance, compute.log -> Timed out waiting for nova-conductor
Product: Red Hat OpenStack Reporter: Tzach Shefi <tshefi>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: urgent Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: ndipanov, yeylon
Target Milestone: ---   
Target Release: 5.0 (RHEL 7)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-09 14:30:43 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:
Embargoed:
Attachments:
Description Flags
Conf and log files none

Description Tzach Shefi 2014-06-09 08:19:32 UTC 
Created attachment 904578 [details]
Conf and log files

Description of problem: Failed to launch instance. 
Packstack deployment AIO RHOS5 RHEl7, using Nova network and QPID, setup used to verify bz 1084495. Bug is basically verified, opted to boot an instance to be sure all works, this is where I get instance state error. 

Openstack-status all active and ok
qpid is listing
[root@dhcp160-231 ~(keystone_admin)]# netstat -tln | grep 5672
tcp        0      0 0.0.0.0:5672            0.0.0.0:*               LISTEN
tcp6       0      0 :::5672

Setup deployed on RHEVM instance not on physical hardware.

Version-Release number of selected component (if applicable):
RHEL7
openstack-nova-console-2014.1-3.el7ost.noarch
openstack-packstack-2014.1.1-0.20.dev1109.el7ost.noarch
openstack-nova-compute-2014.1-3.el7ost.noarch
openstack-nova-scheduler-2014.1-3.el7ost.noarch
openstack-nova-api-2014.1-3.el7ost.noarch
openstack-nova-network-2014.1-3.el7ost.noarch
openstack-nova-common-2014.1-3.el7ost.noarch
openstack-nova-conductor-2014.1-3.el7ost.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Disable selinux and firewall
2. Packstack AIO setup, Nova network using QPID.
2. Try to boot instance from Cirros
3.

Actual results:
Instance fails to boot, error state.

compute.log -> Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?


Expected results:
Instance should boot up.

Additional info:
On attached logs, last instance tried to boot "test1"
Comment 1 Russell Bryant 2014-06-09 14:30:43 UTC 
It looks like the root cause of this failure is #1103800

*** This bug has been marked as a duplicate of bug 1103800 ***