openstack安装过程的一些错误

最新推荐文章于 2024-04-18 05:20:15 发布

qq_41898592

最新推荐文章于 2024-04-18 05:20:15 发布

阅读量5.4k

点赞数 2

文章标签： openstack 1006 nova创建虚拟机失败

本文链接：https://blog.csdn.net/qq_41898592/article/details/89398636

版权

错误

ERROR nova.compute.manager ResourceProviderRetrievalFailed: Failed to get resource provider with UUID dd4a5198-e199-45fe-99a2-00110fea1f57

解决

在controller查看[root@controller ~]# openstack compute service list --service nova-compute 发现为空

重启compute的nova服务：systemctl restart openstack-nova-compute.service

控制节点

su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova

openstack compute service list --service nova-compute

错误ERROR nova.compute.manager ResourceProviderRetrievalFailed: Failed to get resource provider with UUID dd4a5198-e199-45fe-99a2-00110fea1f57

2019-03-29 00:05:20.047 11164 ERROR nova.compute.manager

解决查看tailf /var/log/nova/nova-placement-api.log

AH01630: client denied by server configuration: /usr/bin/nova-placement-api

[root@controller ~]# openstack endpoint list

+----------------------------------+-----------+--------------+--------------+---------+-----------+-----------------------------+

+----------------------------------+-----------+--------------+--------------+---------+-----------+-----------------------------+

+----------------------------------+-----------+--------------+--------------+---------+-----------+-----------------------------+

可以看到是可以看到的.花费了一点时间，最后发现/etc/httpd/conf.d/00-nova-placement-api.conf:

Require all granted

</IfVersion>

Order allow,deny

Allow from all

</IfVersion>

</Directory>

没有配置，加上重启httpd服务解决。

错误：

2019-04-01 03:32:12.629 16837 ERROR nova (class_id, method_id), ConnectionError)

2019-04-01 03:32:12.629 16837 ERROR nova AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.

2019-04-01 03:32:12.629 16837 ERROR nova

可以发现是RABBIT（消息队列）问题

[root@controller ~]# rabbitmqctl status

Status of node rabbit@controller ...

[{pid,1153},

{running_applications,[{rabbit,"RabbitMQ","3.6.5"},

{mnesia,"MNESIA CXC 138 12","4.13.4"},

{os_mon,"CPO CXC 138 46","2.4"},

{rabbit_common,[],"3.6.5"},

{xmerl,"XML parser","1.3.10"},

{ranch,"Socket acceptor pool for TCP protocols.",

"1.2.1"},

{sasl,"SASL CXC 138 11","2.7"},

{stdlib,"ERTS CXC 138 10","2.8"},

{kernel,"ERTS CXC 138 10","4.2"}]},

{os,{unix,linux}},

{erlang_version,"Erlang/OTP 18 [erts-7.3.1.2] [source] [64-bit] [smp:4:4] [async-threads:64] [hipe] [kernel-poll:true]\n"},

{memory,[{total,52193488},

{connection_readers,33840},

{connection_writers,0},

{connection_channels,0},

{connection_other,19696},

{queue_procs,2808},

{queue_slave_procs,0},

{plugins,0},

{other_proc,19137144},

{mnesia,61024},

{mgmt_db,0},

{msg_index,51888},

{other_ets,930392},

{binary,5281520},

{code,19689812},

{atom,719761},

{other_system,6265603}]},

……

返回值正常

[root@controller ~]# rabbitmqctl list_users

Listing users ...

guest [administrator]

发现缺少openstack用户

解决：[root@controller ~]# rabbitmqctl add_user openstack 123456

Creating user "openstack" ...

[root@controller ~]# rabbitmqctl set_permissions openstack ".*" ".*" ".*"

Setting permissions for user "openstack" in vhost "/" ...

关于1006错误，首先检查配置文件，以下是我在网上找到的解决方案：

我遇到了同样的问题，最后用大量的谷歌搜索和试用/错误对其进行了整理。这是我的设置：

控制节点

controller - 10.30.177.42

服务running:

nova-consoleauth

nova-novncproxy

配置文件

nova.conf:

novncproxy_host=0.0.0.0

novncproxy_port=6080

novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.html

计算节点

compute - 10.30.177.39

服务running:

nova-compute

配置文件nova.conf:

vnc_enabled=True

novncproxy_base_url=http://10.30.177.42:6080/vnc_auto.html

vncserver_listen=0.0.0.0

vncserver_proxyclient_address=10.30.177.39

然后我重新启动了所有进程，并且能够建立连接。我的意思是“vncserver proxyclient address”是计算过程的设置，是另一台机器上novncproxy进程可以访问的计算进程的地址（即它需要是novncproxy可以连接的IP）如果你有多个网络进入计算节点）。我最初设置在nonvcproxy端和它的IP，这是错误的。我有一种感觉，你正在做类似的事情。

错误1006

查看日志 /var/log/nova/nova-novncproxy.log

2019-04-03 16:07:16.900 27138 INFO nova.console.websocketproxy [req-a97f2f1a-0aa5-4976-aadf-c3160007da0d - - - - -] handler exception: [Errno 113] EHOSTUNREACH

提示链接不可达，查看防火墙

[root@compute1 ~]# systemctl status firewalld

鈼[0m firewalld.service - firewalld - dynamic firewall daemon

Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)

Active: active (running) since Wed 2019-04-03 02:35:38 EDT; 1h 38min ago

Docs: man:firewalld(1)

Main PID: 4807 (firewalld)

Tasks: 2

CGroup: /system.slice/firewalld.service

鈹斺攢4807 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Apr 03 02:20:15 compute1 systemd[1]: Starting firewalld - dynamic firewall daemon...

Apr 03 02:35:38 compute1 systemd[1]: Started firewalld - dynamic firewall daemon.