[原][openstack-pike][compute node][issue-1]openstack-nova-compute.service holdoff time over, scheduli

在安裝pike  compute node節點的時候遇到啓動nova-compute失敗，問題以下(注意紅色字體)：

[root@compute1 nova]# systemctl start openstack-nova-compute.service
Job for openstack-nova-compute.service failed because the control process exited with error code. 
See "systemctl status openstack-nova-compute.service" and "journalctl -xe" for details.

[root@compute1 nova]# systemctl status openstack-nova-compute.service
● openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled; vendor preset: disabled)
   Active: activating (start) since Tue 2018-09-04 09:37:58 CST; 2s ago
 Main PID: 3431 (nova-compute)
    Tasks: 1
   CGroup: /system.slice/openstack-nova-compute.service
           └─3431 /usr/bin/python2 /usr/bin/nova-compute

Sep 04 09:37:58 compute1 systemd[1]: openstack-nova-compute.service holdoff time over, scheduling restart.
Sep 04 09:37:58 compute1 systemd[1]: Starting OpenStack Nova Compute Server...
[root@compute1 nova]# date
Tue Sep  4 09:38:14 CST 2018
[root@compute1 nova]# journalctl -xe
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing workstation service for lo.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing workstation service for virbr0-nic.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing address record for 192.168.122.1 on virbr0.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing workstation service for virbr0.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing address record for fe80::fc81:46e3:49a7:d1da on ens35.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing address record for fe80::8fb9:3258:5058:d538 on ens35.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing address record for 192.168.70.73 on ens35.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing workstation service for ens35.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Withdrawing address record for fe80::fe24:180a:91a7:8bdf on ens34.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Host name conflict, retrying with compute1-60
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for fe80::fc81:46e3:49a7:d1da on ens35.*.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for fe80::8fb9:3258:5058:d538 on ens35.*.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for 192.168.70.73 on ens35.IPv4.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for fe80::fe24:180a:91a7:8bdf on ens34.*.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for fe80::1041:9aae:6318:6a4a on ens34.*.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for 10.50.70.73 on ens34.IPv4.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering new address record for 192.168.184.135 on ens33.IPv4.
Sep 04 09:38:59 compute1 avahi-daemon[692]: Registering HINFO record with values 'X86_64'/'LINUX'.
Sep 04 09:39:00 compute1 systemd[1]: openstack-nova-compute.service: main process exited, code=exited, status=1/FAILURE
Sep 04 09:39:00 compute1 systemd[1]: Failed to start OpenStack Nova Compute Server.
-- Subject: Unit openstack-nova-compute.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit openstack-nova-compute.service has failed.
-- 
-- The result is failed.
Sep 04 09:39:00 compute1 systemd[1]: Unit openstack-nova-compute.service entered failed state.
Sep 04 09:39:00 compute1 systemd[1]: openstack-nova-compute.service failed.
Sep 04 09:39:00 compute1 systemd[1]: openstack-nova-compute.service holdoff time over, scheduling restart.
Sep 04 09:39:00 compute1 systemd[1]: Starting OpenStack Nova Compute Server...

[root@compute1 nova]#vim /var/log/nova/nova-compute.log 
... 2695 ERROR nova AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. 
For details see the broker logfile.

從上面的記錄中能夠推斷應該message queue出了問題。致使沒法login。

再想一想涉及login到rabbit的使用的是用戶名和密碼：

查看rabbit server [on controller node]用戶名密碼：

[root@controller ~]# rabbitmq-plugins enable rabbitmq_management                 //開啓rabbit web界面 

[root@controller ~]#lsof |grep rabbit                                            //查詢rabbit web服務端口 15672

async_63   1089 2034       rabbitmq   49u     IPv4              32616       0t0        TCP *:15672 (LISTEN)

在瀏覽器中輸入controller:15672地址，以下圖

再在compute node中的nova.conf中查找相關的用戶名和密碼

[DEFAULT]

。。。
enabled_apis = osapi_compute,metadata
transport_url = rabbit://openstack:rabbit@controller

用戶名爲openstack

密碼爲rabbit

login 失敗

查看rabbit sever的用戶列表發現沒有openstack這個用戶：

[root@controller ~]# rabbitmqctl list_users
Listing users ...
admin [administrator]
guest    [administrator]

[重點]使用admin用戶登陸，因爲忘記密碼又不能直接查看明文密碼，因此在rabbit_server[controller node]上重置用戶爲admin的用戶密碼：

[root@controller nova]# rabbitmqctl change_password admin admin

再次使用用戶名和密碼登陸

用戶名：admin

密碼：admin

最後修改nova.conf [on compute node or controller node] 

transport_url= rabbit://admin:admin@controller

 啓動nova-compute.service

[root@compute1 nova]# systemctl start openstack-nova-compute.service
[root@compute1 nova]# systemctl status openstack-nova-compute.service
● openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-09-04 13:46:08 CST; 49s ago
 Main PID: 25205 (nova-compute)
    Tasks: 22
   CGroup: /system.slice/openstack-nova-compute.service
           └─25205 /usr/bin/python2 /usr/bin/nova-compute

Sep 04 13:46:05 compute1 systemd[1]: Starting OpenStack Nova Compute Server...
Sep 04 13:46:08 compute1 systemd[1]: Started OpenStack Nova Compute Server.

問題解決