failed to launch an instance from ISO image: TRACE nova.compute.manager MessagingTimeout: Timed out waiting for a reply to message ID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
David Ripton |
Bug Description
Description of problem:
The Openstack is installed as AIO (with nova networking) on fedora 20. The instance was launched on a flavor that has the following parameters:
+------
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+------
| 8ddee6ea-
+------
On the first try the instance status was stuck on 'spawning', even after a time out stopped the process.
On the second try the instance status was changed from 'spawning' to 'Error'.
The nova compute log:
2014-03-26 15:33:58.548 15699 DEBUG nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
2014-03-26 15:33:58.548 15699 TRACE nova.compute.
Version-Release number of selected component (if applicable):
python-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
python-
python-
python-
openstack-
How reproducible:
100%
Steps to Reproduce:
1. upload an ISO image.
2. change a flavor to have the same parameters as it shows above.
3. launch an instance.
Actual results:
The launch fails.
Expected results:
The instance is up and running.
tags: | added: scheduler |
tags: |
added: compute removed: scheduler |
Changed in nova: | |
assignee: | nobody → David Ripton (dripton) |
Changed in nova: | |
status: | Incomplete → Invalid |
This is a generic error (MessagingTimeout). Is your openstack deployment otherwise working? Are you able to launch instances successfully from other types of images and/or flavors?