在公共网络上启动实例后，检查实例的状态： nova list 后 Status是error

先谢谢拉。

启动实例：

1、创建实例

$ nova boot --flavor m1.tiny --image cirros --nic net-id=PUBLIC_NET_ID \
  --security-group default --key-name mykey public-instance

使用``public``网络的ID替换``PUBLIC_NET_ID``和秘钥对的名称demo-key后。

nova boot --flavor m1.tiny --image cirros --nic net-id=e0336e55-32e5-412f-b76c-0ecc95e7d599 \
  --security-group default --key-name demo-key public-instance

结果见附件2.png

图2

2、检查实例
nova list

nova list后 “Status” 是”error“

结果见附件2.png



opens tack官网的value项是有nova的，我这里没有。

结果见附件4.png

3、查看nova-conductor.log
结果见附件3.png

图3：nova-conductor.log

root@controller:~# vi /var/log/nova/nova-conductor.log
2017-12-18 07:23:02.394 4153 WARNING oslo_config.cfg [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] Option "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from group "oslo_concurrency".
2017-12-18 07:23:02.409 4153 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 07:23:03.433 4153 INFO oslo.messaging._drivers.impl_rabbit [req-7ec4acfe-744a-4b80-a124-cde95ccbfa02 - - - - -] Connecting to AMQP server on localhost:5672
2017-12-18 07:23:03.461 4153 INFO oslo.messaging._drivers.impl_rabbit [req-7ec4acfe-744a-4b80-a124-cde95ccbfa02 - - - - -] Connected to AMQP server on 127.0.0.1:5672
2017-12-18 07:23:07.808 4153 INFO oslo.messaging._drivers.impl_rabbit [req-9f61dfdc-fb22-4537-8c5f-cab0c8d3db26 - - - - -] Connecting to AMQP server on localhost:5672
2017-12-18 07:23:07.823 4153 INFO oslo.messaging._drivers.impl_rabbit [req-9f61dfdc-fb22-4537-8c5f-cab0c8d3db26 - - - - -] Connected to AMQP server on 127.0.0.1:5672
2017-12-18 07:39:49.710 4153 INFO oslo_service.service [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] Caught SIGTERM, exiting
2017-12-18 07:39:49.711 4153 WARNING oslo_messaging.server [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] start/stop/wait must be called in the same thread
2017-12-18 07:39:49.711 4153 WARNING oslo_messaging.server [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] start/stop/wait must be called in the same thread
2017-12-18 07:39:56.034 4702 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 07:39:56.042 4702 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 07:39:56.177 4702 INFO oslo.messaging._drivers.impl_rabbit [req-42e1ca28-4e60-4893-a1b8-a1fa9ae5bcb7 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 07:39:56.184 4702 INFO oslo.messaging._drivers.impl_rabbit [req-42e1ca28-4e60-4893-a1b8-a1fa9ae5bcb7 - - - - -] Connected to AMQP server on controller:5672
2017-12-18 07:39:56.480 4702 INFO oslo.messaging._drivers.impl_rabbit [req-3fe3744b-ac33-4f1d-bcaa-f5159b568fa8 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 07:39:56.492 4702 INFO oslo.messaging._drivers.impl_rabbit [req-3fe3744b-ac33-4f1d-bcaa-f5159b568fa8 - - - - -] Connected to AMQP server on controller:5672
2017-12-18 20:40:21.374 898 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 20:40:21.464 898 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 20:40:22.164 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 20:40:22.187 898 ERROR oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
2017-12-18 20:40:23.229 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Reconnected to AMQP server on controller:5672
2017-12-18 20:40:23.230 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Connected to AMQP server on controller:5672
@
@
@
@
@
@
@
@
@
@
"/var/log/nova/nova-conductor.log" 90 lines, 14589 characters
2017-12-18 07:23:02.394 4153 WARNING oslo_config.cfg [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] Option "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from group "oslo_concurrency".
2017-12-18 07:23:02.409 4153 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 07:23:03.433 4153 INFO oslo.messaging._drivers.impl_rabbit [req-7ec4acfe-744a-4b80-a124-cde95ccbfa02 - - - - -] Connecting to AMQP server on localhost:5672
2017-12-18 07:23:03.461 4153 INFO oslo.messaging._drivers.impl_rabbit [req-7ec4acfe-744a-4b80-a124-cde95ccbfa02 - - - - -] Connected to AMQP server on 127.0.0.1:5672
2017-12-18 07:23:07.808 4153 INFO oslo.messaging._drivers.impl_rabbit [req-9f61dfdc-fb22-4537-8c5f-cab0c8d3db26 - - - - -] Connecting to AMQP server on localhost:5672
2017-12-18 07:23:07.823 4153 INFO oslo.messaging._drivers.impl_rabbit [req-9f61dfdc-fb22-4537-8c5f-cab0c8d3db26 - - - - -] Connected to AMQP server on 127.0.0.1:5672
2017-12-18 07:39:49.710 4153 INFO oslo_service.service [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] Caught SIGTERM, exiting
2017-12-18 07:39:49.711 4153 WARNING oslo_messaging.server [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] start/stop/wait must be called in the same thread
2017-12-18 07:39:49.711 4153 WARNING oslo_messaging.server [req-daad9826-4404-457a-8573-f037ec83a285 - - - - -] start/stop/wait must be called in the same thread
2017-12-18 07:39:56.034 4702 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 07:39:56.042 4702 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 07:39:56.177 4702 INFO oslo.messaging._drivers.impl_rabbit [req-42e1ca28-4e60-4893-a1b8-a1fa9ae5bcb7 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 07:39:56.184 4702 INFO oslo.messaging._drivers.impl_rabbit [req-42e1ca28-4e60-4893-a1b8-a1fa9ae5bcb7 - - - - -] Connected to AMQP server on controller:5672
2017-12-18 07:39:56.480 4702 INFO oslo.messaging._drivers.impl_rabbit [req-3fe3744b-ac33-4f1d-bcaa-f5159b568fa8 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 07:39:56.492 4702 INFO oslo.messaging._drivers.impl_rabbit [req-3fe3744b-ac33-4f1d-bcaa-f5159b568fa8 - - - - -] Connected to AMQP server on controller:5672
2017-12-18 20:40:21.374 898 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 20:40:21.464 898 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 20:40:22.164 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 20:40:22.187 898 ERROR oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
2017-12-18 20:40:23.229 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Reconnected to AMQP server on controller:5672
2017-12-18 20:40:23.230 898 INFO oslo.messaging._drivers.impl_rabbit [req-995936c5-c684-481f-8556-e54616796155 - - - - -] Connected to AMQP server on controller:5672
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2017-12-18 20:45:09.170 892 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 20:45:09.284 892 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 20:45:09.868 892 INFO oslo.messaging._drivers.impl_rabbit [req-8f7b9dba-fcb9-42fb-8c87-a485cf645648 - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 20:45:09.900 892 INFO oslo.messaging._drivers.impl_rabbit [req-8f7b9dba-fcb9-42fb-8c87-a485cf645648 - - - - -] Connected to AMQP server on controller:5672
2017-12-18 20:53:38.598 896 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-12-18 20:53:38.662 896 INFO nova.service [-] Starting conductor node (version 12.0.6)
2017-12-18 20:53:40.523 896 INFO oslo.messaging._drivers.impl_rabbit [req-5cca53fc-6abc-4fdb-8a6b-65e67bebfa9b - - - - -] Connecting to AMQP server on controller:5672
2017-12-18 20:53:40.570 896 ERROR oslo.messaging._drivers.impl_rabbit [req-5cca53fc-6abc-4fdb-8a6b-65e67bebfa9b - - - - -] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
2017-12-18 20:53:41.594 896 ERROR oslo.messaging._drivers.impl_rabbit [req-5cca53fc-6abc-4fdb-8a6b-65e67bebfa9b - - - - -] AMQP server on controller:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 2 seconds.

图1

图4

可用网络可能有问题，为何只有一个。

nextuser 发表于 2017-12-25 21:02
可用网络可能有问题，为何只有一个。

可用网络可能有问题是指什么，我小白，真的不懂。谢谢了。
我是按照opens tack官网来搭建的。做到启动实例这里就有问题
https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/launch-instance-public.html

nextuser 发表于 2017-12-25 21:02
可用网络可能有问题，为何只有一个。

可用网络可能有问题，是指哪里，我是小白，真不懂，求指点，谢谢。
我是按照opens tack官网的搭建的。
在启动实例这里就i有问题。
opens tack官网的教程
https://docs.openstack.org/liberty/zh_CN/install-guide-ubuntu/launch-instance-public.html

求大神

一楼大神。
可用网络可能有问题是指什么，我真的不懂，我小白。谢谢了。
我是按照opens tack官网搭建的。
在启动实例的时候有问题。
opens tack官网
https://docs.openstack.org/liber ... nstance-public.html

nextuser 发表于 2017-12-25 21:02
可用网络可能有问题，为何只有一个。

可用网络可能有问题是指什么问题啊。我真的不懂。谢谢了

nextuser 发表于 2017-12-25 21:02
可用网络可能有问题，为何只有一个。

我是按照open sack官网的搭建的。在启动实例有问题。

Morata 发表于 2017-12-25 22:08
我是按照open sack官网的搭建的。在启动实例有问题。

官网的网络，都是有子网的，看你的贴图好像并没有子网。
这是M版的
https://docs.openstack.org/mitak ... aunch-instance.html



https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/launch-instance-networks-provider.html



https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/launch-instance-networks-selfservice.html

从你列出来的内容来看，是没有问题的。查看下其它组件的错误日志