Re: Error migrate System VMs after upgrageing to 4.17

2022-08-30 Thread Slavka Peleva
Hi Chris, The deployment fails because CS cannot find a free IP address to allocate for the system VM. Can you check if you explicitly added a range for the system VMs, or you can check with this `select * from user_ip_address where forsystemvms = 1;` If you don't have any ranges, you can get free

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread vas...@gmx.de
Hi Slavka, no, i am not using any kind of custome offerings. I try to provide a more detailled log this time. Situation: v-83-VM was the "broken" consoleproxy. So the following log starts with it's expunging. Afterwards the new consoleproxy shall be deployed - v-85-VM. This first deployment (log

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread Slavka Peleva
Thanks, Chris, for the information! Are you using custom offerings for the system VMs? Can you share more info if yes? About the log, it's not the complete log from where the deployment started. The deployment begins a bit earlier than what you shared. Can you search the management log for `Sync

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread vas...@gmx.de
Hi Slavka, thats what i did after your suggestion / informatin and where the error occured. Deleted / Destroyed the consoleproxy and waited till recreation. Which didn't worked throwing the error i pasted above. Sorry for beeing so unspecific. Regards, Chris Am Mo., 29. Aug. 2022 um 12:46 Uhr sc

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread Slavka Peleva
Hi Chris, I mean to recreate the system VMs by destroying them. On Mon, Aug 29, 2022 at 12:38 PM vas...@gmx.de wrote: > Hi Slavka, > > didn't tried to restart the SystemVMs. Reading through the docs i had the > impression that "live-patching" would be enough for this > Anyway - I tried my l

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread vas...@gmx.de
Hi Slavka, didn't tried to restart the SystemVMs. Reading through the docs i had the impression that "live-patching" would be enough for this Anyway - I tried my luck with the console proxy. Which failed utterly. Not starting as it isn't finding any useable storage pool. - logs at the end of

Re: Error migrate System VMs after upgrageing to 4.17

2022-08-29 Thread Slavka Peleva
Hi Chris, Did you recreate the system VMs? In the 4.17 version, the `systemvm.iso` is deprecated. In its place, you should have the file on agents `/usr/share/cloudstack-common/vms/agent.zip`. Can you share the complete log if the system VMs are newly created after the upgrade? Best regards, Slav

Error migrate System VMs after upgrageing to 4.17

2022-08-28 Thread vas...@gmx.de
Hi everyone, faceing some challanges again after upgradeing to 4.17. Did as explained in the docs. Afterwards I am now not able to migrate system VMs to different hosts. Getting the error "Exception during migrate: org.libvirt.LibvirtException: Cannot access storage file '/usr/share/cloudstack-co