nova-novncproxy is not starting after a reboot
Hi,
I am not able to access console for any of the instances after a reboot of my controller. I observed that nova-novncproxy is not starting. When i try to start it, it starts and dies immediately. I could see the below info in /var/log/nova/nova-novncproxy.log. Rest of nova services are running fine.
2017-08-02 06:53:49.068 11139 CRITICAL nova [-] Unhandled error: NoSuchOptError: no such option in group DEFAULT: verbose
2017-08-02 06:53:49.068 11139 ERROR nova Traceback (most recent call last):
2017-08-02 06:53:49.068 11139 ERROR nova File "/usr/bin/nova-novncproxy", line 10, in <module>
2017-08-02 06:53:49.068 11139 ERROR nova sys.exit(main())
2017-08-02 06:53:49.068 11139 ERROR nova File "/usr/lib/python2.7/dist-packages/nova/cmd/novncproxy.py", line 41, in main
2017-08-02 06:53:49.068 11139 ERROR nova port=CONF.vnc.novncproxy_port)
2017-08-02 06:53:49.068 11139 ERROR nova File "/usr/lib/python2.7/dist-packages/nova/cmd/baseproxy.py", line 64, in proxy
2017-08-02 06:53:49.068 11139 ERROR nova verbose=CONF.verbose,
2017-08-02 06:53:49.068 11139 ERROR nova File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2183, in __getattr__
2017-08-02 06:53:49.068 11139 ERROR nova raise NoSuchOptError(name)
2017-08-02 06:53:49.068 11139 ERROR nova NoSuchOptError: no such option in group DEFAULT: verbose
2017-08-02 06:53:49.068 11139 ERROR nova
2017-08-02 06:53:50.736 11174 WARNING oslo_reports.guru_meditation_report [-] Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be re
gistered in a future release, so please use SIGUSR2 to generate reports.
2017-08-02 06:53:50.737 11174 CRITICAL nova [-] Unhandled error: NoSuchOptError: no such option in group DEFAULT: verbose
2017-08-02 06:53:50.737 11174 ERROR nova Traceback (most recent call last):
Here are the [vnc] configuration in controller and compute nodes.
controller:
[vnc]
vncserver_listen = $my_ip
vncserver_proxyclient_address = $my_ip
Above my_ip = 192.168.40.20 (IP of controller)
compute:
[vnc]
enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = $my_ip
novncproxy_base_url = http://192.168.40.20:6080/vnc_auto.html
Above my_ip = IP of compute node.
I was able to access the console of instances prior to reboot of controller node. Can you please suggest what can be done to get this working again?
Regards Krishna