cloudstack icon indicating copy to clipboard operation
cloudstack copied to clipboard

CS 4.20.1 Urgent: Console not working after Upgrade from 4.20.0 to 4.20.1

Open tatay188 opened this issue 8 months ago • 5 comments

problem

After finishing the process and restarting the System VMs,

everything seems to be working fine, except the connectivity to the Console on proxy or any VM that was working before.

Additionally the latency increased after the migration - tested with pings only adding 200 ms - which is double than before - to the systemVMs compared to 4.20.0

versions

Cloudstack 4.20.1 Ceph storage primary EMC Unity secondary Guest VXLAN Public VLAN

Pings are successful to internet and to management. However latency is higher.

The steps to reproduce the bug

  1. Upgrade to 4.20.1
  2. enable VMs
  3. try to connect to console to proxy or to any VM, none works.
  4. Restarted the SystemVMs again - still does not work. ...

What to do about it?

No response

tatay188 avatar Jun 17 '25 06:06 tatay188

can you destroy the system vms , and retry after new system vms are created ?

@tatay188

weizhouapache avatar Jun 17 '25 06:06 weizhouapache

Thank you Wei, That worked on the second Attempt after I restarted the KVM agent again - first attempt did not work without the KVM restart - I did check all the logs, there are no warnings or errors.

tatay188 avatar Jun 17 '25 06:06 tatay188

The console died after the Hypervisor restarted, I restarted the SystemVMs, and did not work. I restarted everything, and did not work. At this time I have no console access.

tatay188 avatar Jun 18 '25 02:06 tatay188

@tatay188 , can you add some information to the description ;

  • what version did you upgrade from?
  • what hypervisor type/- version are you running?

DaanHoogland avatar Jun 18 '25 08:06 DaanHoogland

from 4.20.0 to 4.20.1 Ubuntu 22.04.05 KVM Hypervisor kvm --version QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.26) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

tatay188 avatar Jun 18 '25 14:06 tatay188

Fixed by restarting the Management server, Agent server, and restart the System-VM in that order.

tatay188 avatar Jul 03 '25 23:07 tatay188