Hi Nick,
Can you try destroying old ssvms, cpvms? Then, can you share the management
server logs (at /var/log/cloudstack/management/management-server.log) around
the exceptions/errors?
After upgrading did CloudStack copy systemvm.iso and scripts to the xcp-ng
hosts? You can force this by:
1. Clearing the host tags on hosts:
# for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe
host-param-clear uuid=$host param-name=tags; done;
2. Restart management server, on reconnecting to xs/xcp-ng hosts it will
copy the artifacts (systemvm.iso, scripts etc, see in the logs)
3. Destroy old VRs and CPVM
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
________________________________
From: Nick Thompson <[email protected]>
Sent: Wednesday, February 26, 2020 20:45
To: '[email protected]' <[email protected]>
Subject: Upgrading from 4.11.3 to 4.13 with XCP-NG 7.5
Hi All,
Just wondering if there are any known problems upgrading to the latest version
of CloudStack (4.13) when using XCP-NG 7.5? (working fine in 4.11.3)
For some reason the SystemVMs (Storage and Console Proxy) cloud agent doesn't
start, when running a "service cloud start" it seems to failed with message
'failed at step CHROOT.
The Virtual Routers fail to start (start up and then power off) with the
message "cloudstack Unable to start instance due to Unable to start due to
error in finalizeStart, not retrying" inside the management server log.
Telnetting to port 8250 on the management server seems to be fine on all system
VMs.
Any thoughts on this would be greatly apricated.
Regards,
Nick.
[email protected]
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
@shapeblue
