Ask Your Question

openstack server list always show ERROR status of instance

asked 2016-10-26 09:21:28 -0500

chansonzhang gravatar image

Hello, When I follow the guide Launch an instance, the status of the instance is always "ERROR"

  [root@controller ~]# openstack server list
| ID               | Name             | Status | Networks | Image Name         |
| f1d3769c-        | provider-        | ERROR  |          | cirros-0.3.4-x86_6 |
| d7d2-4419-b1bd-  | instance1        |        |          | 4-uec              |
| 2f450b45558d     |                  |        |          |                    |

In Dashboard I saw the following info:

2016年10月26日 14:02
1 分钟

object of type 'int' has no len()
File "/usr/lib/python2.7/site-packages/nova/conductor/", line 484, in build_instances context, request_spec, filter_properties) File "/usr/lib/python2.7/site-packages/nova/conductor/", line 555, in _schedule_instances hosts = self.scheduler_client.select_destinations(context, spec_obj) File "/usr/lib/python2.7/site-packages/nova/scheduler/", line 370, in wrapped return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/", line 51, in select_destinations return self.queryclient.select_destinations(context, spec_obj) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/", line 37, in __run_method return getattr(self.instance, __name)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/nova/scheduler/client/", line 32, in select_destinations return self.scheduler_rpcapi.select_destinations(context, spec_obj) File "/usr/lib/python2.7/site-packages/nova/scheduler/", line 126, in select_destinations return, 'select_destinations', **msg_args) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/", line 169, in call retry=self.retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/", line 97, in _send timeout=timeout, retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 464, in send retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 450, in _send msg=msg, timeout=timeout, retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 1278, in topic_send retry=retry) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 1162, in _ensure_publishing self.ensure(method, retry=retry, error_callback=_error_callback) File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 791, in ensure ret, channel = autoretry_method() File "/usr/lib/python2.7/site-packages/kombu/", line 436, in _ensured return fun(*args, **kwargs) File "/usr/lib/python2.7/site-packages/kombu/", line 508, in __call__ return fun(*args, channel=channels[0], **kwargs), channels[0] File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 767, in execute_method method() File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/", line 1193, in _publish compression=self.kombu_compression) File "/usr/lib/python2.7/site-packages/kombu/", line 168, in publish routing_key, mandatory, immediate, exchange, declare) File "/usr/lib/python2.7/site-packages/kombu/", line 184, in _publish mandatory=mandatory, immediate=immediate, File "/usr/lib/python2.7/site-packages/amqp/", line 2130, in basic_publish_confirm self.wait([(60, 80)]) File "/usr/lib/python2.7/site-packages/amqp/", line 2123, in _basic_publish basic_publish = _basic_publish File "/usr/lib/python2.7/site-packages/amqp/", line 56, in _send_method self.channel_id, method_sig, args, content, File "/usr/lib/python2.7/site-packages/amqp/ ...
edit retag flag offensive close merge delete


openstack server show may provide details about the error. Also check the logs under /var/log/nova. The stack trace in the dashboard indicates a problem with RabbitMQ, most likely a misconfiguration.

Bernd Bausch gravatar imageBernd Bausch ( 2016-10-27 22:55:21 -0500 )edit

2 answers

Sort by » oldest newest most voted

answered 2016-10-28 01:19:30 -0500

chansonzhang gravatar image

thank you! I finally solved this problem, the dashboard unexpectedly gave an unreal stack trace. After a day, when I try to launch the instance again, the dashboard show the real reason, which indicate that the image may be broken. So I changed image, and all get OK.

edit flag offensive delete link more

answered 2018-10-29 06:10:59 -0500

Heyyy guys... I have the same problem with openstack "newton" can you please help me to find a solution and what can i do exact to resolve the status error Thank you

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-10-26 09:21:28 -0500

Seen: 1,946 times

Last updated: Oct 29 '18