This was supposed to be a cry for help, but during the log collection I've managed to find and fix the cause of the problem. I'm posting this, hoping it might save somebody's time and sanity in the future.
Shortly after upgrading to 6.2, I've started to experience a weird behavior every time the nodes in the cluster needed to exchange some data in real time. Specifically during the live migration between nodes and opening a noVNC session across nodes (logged onto node A, VM running on node B).
Live migration log provides no useful info:
Live migration while disk is on local storage provides more info:
And finally javascript console in browser (while openning noVNC) confirms the suspission:
Problem was the following line I've added to the .bashrc on each node shortly before the upgrade. It changes the window title, so you can easily distinguish between multiple SSH sessions.
I'd like to take this oportunity to ask the devs - Wouldn't it make sense NOT to run bash during machine to machine communication? And in case it's necessary, at least NOT execute the .bashrc?
Shortly after upgrading to 6.2, I've started to experience a weird behavior every time the nodes in the cluster needed to exchange some data in real time. Specifically during the live migration between nodes and opening a noVNC session across nodes (logged onto node A, VM running on node B).
Live migration log provides no useful info:
2020-05-31 17:36:53 starting migration of VM 883 to node 'g7' (192.168.1.151)
2020-05-31 17:36:53 starting VM 883 on remote node 'g7'
2020-05-31 17:36:56 ERROR: online migrate failure - unable to detect remote migration address
2020-05-31 17:36:56 aborting phase 2 - cleanup resources
2020-05-31 17:36:56 migrate_cancel
2020-05-31 17:36:58 ERROR: migration finished with problems (duration 00:00:06)
TASK ERROR: migration problems
Live migration while disk is on local storage provides more info:
2020-05-31 17:17:18 ERROR: online migrate failure - can't open migration tunnel - got strange reply from mtunnel (']0;G7tunnel online')
And finally javascript console in browser (while openning noVNC) confirms the suspission:
Failed when connecting: Invalid server version G7�RFB
Problem was the following line I've added to the .bashrc on each node shortly before the upgrade. It changes the window title, so you can easily distinguish between multiple SSH sessions.
echo -en "\033]0;NameOfTheNode\a"
I'd like to take this oportunity to ask the devs - Wouldn't it make sense NOT to run bash during machine to machine communication? And in case it's necessary, at least NOT execute the .bashrc?