NoVNC glitches with cloud-init/serial console

[arcanatigris]

Im having this strange issue when I open the console from a cloud-init vm on a node other than the one im actually on it glitches noVNC.

So Im pointing my browser to node A then when I open a cloud-init vm on node B the console keeps restarting. Works fine when I open a cloud-init vm on node A. If I point my browser to node B I get the same behavior vice-versa.

 

[dcsapak]

check if you can ssh from one node to the other without password, this is necessary for the cross node consoles to work
also pleas post the output of pveversion -v

 

[arcanatigris]

check if you can ssh from one node to the other without password, this is necessary for the cross node consoles to work
also pleas post the output of pveversion -v

Yes ssh to the other cluster nodes work as it should.

Spoiler: pveversion -v

proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve)
pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)
pve-kernel-4.15: 5.2-11
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph: 12.2.8-pve1
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-41
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-3
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-29
pve-docs: 5.2-9
pve-firewall: 3.0-14
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-38
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve2~bpo1

 

[dcsapak]

is there anything in the console task log or syslog that indicates any error?

 

[arcanatigris]

No logs seem fine, If I change the display to default it works fine. The problem only exists when using display serial

 

[dcsapak]

hi, yes i can now reproduce it, it seems to be bug with the combination of remote node -> novnc -> serial display
can you open a bug report here : https://bugzilla.proxmox.com/
so that we can track the progress