按照官方文档部署openstack的O版,创建实例失败

yanghuabin1202 2017-09-20 01:56:41
在完成openstack主要组件的部署后,并且每个组件都进行过验证,但在创建实例时失败

希望大神能够指点迷津,帮忙确认一下是哪里出了错误!
...全文
1138 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
alinly 2017-09-27
  • 打赏
  • 举报
回复
一个服务一个服务的排查, 例如keystone 例如nova 例如neutron 看日志,提示比较全了. 你这大面积报错,不好定位,或者说有很多错误. 一个一个来解决。
yanghuabin1202 2017-09-25
  • 打赏
  • 举报
回复
启动实例失败后,看/var/log/nova/nova-api.log 日志,也看不出出了什么错。



yanghuabin1202 2017-09-25
  • 打赏
  • 举报
回复
很多服务中都出现了同样的问题,也不知道是哪里出了问题。 ● openstack-nova-consoleauth.service - OpenStack Nova VNC console auth Server Loaded: loaded (/usr/lib/systemd/system/openstack-nova-consoleauth.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2017-09-25 20:45:11 CST; 19min ago Main PID: 932 (nova-consoleaut) CGroup: /system.slice/openstack-nova-consoleauth.service └─932 /usr/bin/python2 /usr/bin/nova-consoleauth Sep 25 20:43:31 controller systemd[1]: Starting OpenStack Nova VNC console auth Server... Sep 25 20:45:11 controller systemd[1]: Started OpenStack Nova VNC console auth Server. Sep 25 20:45:13 controller nova-consoleauth[932]: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.DefaultRPCAccessPolicy'> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy. Sep 25 20:45:13 controller nova-consoleauth[932]: access_policy) ● openstack-nova-scheduler.service - OpenStack Nova Scheduler Server Loaded: loaded (/usr/lib/systemd/system/openstack-nova-scheduler.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2017-09-25 20:45:14 CST; 19min ago Main PID: 936 (nova-scheduler) CGroup: /system.slice/openstack-nova-scheduler.service └─936 /usr/bin/python2 /usr/bin/nova-scheduler Sep 25 20:43:31 controller systemd[1]: Starting OpenStack Nova Scheduler Server... Sep 25 20:45:14 controller systemd[1]: Started OpenStack Nova Scheduler Server. Sep 25 20:45:14 controller nova-scheduler[936]: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.DefaultRPCAccessPolicy'> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy. Sep 25 20:45:14 controller nova-scheduler[936]: access_policy) ● openstack-nova-conductor.service - OpenStack Nova Conductor Server Loaded: loaded (/usr/lib/systemd/system/openstack-nova-conductor.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2017-09-25 20:45:12 CST; 19min ago Main PID: 940 (nova-conductor) CGroup: /system.slice/openstack-nova-conductor.service └─940 /usr/bin/python2 /usr/bin/nova-conductor Sep 25 20:43:31 controller systemd[1]: Starting OpenStack Nova Conductor Server... Sep 25 20:45:12 controller systemd[1]: Started OpenStack Nova Conductor Server. Sep 25 20:45:13 controller nova-conductor[940]: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.DefaultRPCAccessPolicy'> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy. Sep 25 20:45:13 controller nova-conductor[940]: access_policy)
SimonYCJ 2017-09-24
  • 打赏
  • 举报
回复
@yanghuabin123 去看下/var/log/nova/nova-api.log 日志文件里说的错,你应该是遇见bug了。

999

社区成员

发帖
与我相关
我的任务
社区描述
OpenStack
社区管理员
  • OpenStack社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧