How to solve the problem that you cannot use noVNC login to access the created virtual machine when docking with FusionCompute?
In this issue, the editor will bring you about how to solve the virtual machine created by being unable to access the virtual machine when docking with FusionCompute. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.
[problem phenomenon]
The OpenStack Kiko version docks with Huawei FusionCompute. Virtual machines created through the interface are opened using the console, prompting Authentication fail.
[problem Analysis]
From the prompt, vnc failed to verify the password after a successful handshake, which can be confirmed by the browser's F12 tool.
View the CNA node where the virtual machine is located, and analyze the virtual machine log
/ var/log/xen/qemu-dm-i-00000093.log
[2013-07-13 12:09:04] New client on socket 28
[2013-07-13 12:09:04] vnc_set_share_mode/28: undefined-> connecting
[2013-07-13 12:09:04] Set the controller (type:1) of qemu_timer_mode 2.
[2013-07-13 12:09:04] the controller (type:1) frame freq is 200.
[2013-07-13 12:09:04] Client request protocol version 3.8
[2013-07-13 12:09:04] Telling client we support auth 2
[2013-07-13 12:09:04] Client requested auth 2
[2013-07-13 12:09:04] Start VNC auth
[2013-07-13 12:09:04] Client challenge response did not match
[2013-07-13 12:09:04] Closing down client sock: protocol error
[2013-07-13 12:09:04] vnc_set_share_mode/28: connecting-> disconnected
[2013-07-13 12:09:04] Unset the controller (type:1) of qemu_timer_mode 2.
You can also see that there is a mismatch after the validation is started.
However, the virtual machine can be accessed through the vnc console of FusionCompute Portal. Querying the information of the virtual machine shows that the virtual machine has vncPassword set, so the virtual machine cannot be accessed.
By analyzing the source code of vnc, we can find that the original vnc password encryption uses DES, while FC's vnc encryption algorithm uses sha256.
[solution]
The virtual machine can be accessed by encrypting the vnc password of the virtual machine using sha256
This is how to solve the virtual machine created when you cannot use noVNC login to access the virtual machine when interfacing with FusionCompute. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.
