Hello Andrija
Presently, CloudStack's host lists exhibited stability prior to the
disaster, but their statuses are currently fluctuating continuously. Some
hosts are initially marked as disconnected, but after a period, they
transition to a connected state."
[image: image.png]
*Using virsh w
Congratulations everyone on the new release. Thanks Wei.
-Jithin
From: Wei ZHOU
Date: Friday, 15 September 2023 at 7:15 PM
To: users
Subject: [ANNOUNCEMENT] Apache CloudStack LTS Maintenance Release 4.18.1.0
The Apache CloudStack project is pleased to announce the release of
CloudStack 4.18.1.0
Hi Wei,
There are no reason to migrate, there is enough capacity on the same host. No
storage tags and we use local storage.
Regards,
Cristian
-Original Message-
From: Wei ZHOU
Sent: Monday, September 18, 2023 11:24 AM
To: users@cloudstack.apache.org
Subject: Re: Index 0 out of boun
Hi,
it looks there is no suitable pool found for the migration. good to know
you fixed by manual db changes.
However, If you expect the volume not be migrated in the future, it would
be better to figure out why cloudstack tried to migrate it ( probably due
to storage tags or capacity, etc)
-Wei
Dear community members,
I am writing to remind that on September 22nd, we are closing the CFP for the
CloudStack Collaboration Conference.
We would love to have at least a few more submissions from the community of
interesting talks until Friday.
REMINDER: Sharing your success stories with Apac
Hi Wei,
Please see,.:
2023-09-18 02:07:13,556 INFO [c.c.s.ManagementServerImpl]
(API-Job-Executor-2:ctx-89843446 job-85583 ctx-db5354a6) (logid:f25c5504)
Volume Vol[709
8|name=ROOT-4591|vm=4591|ROOT] isn't attached to any running vm. Looking for
storage pools in the cluster to which this v
Hi,
any error logs ?
-Wei
On Mon, 18 Sept 2023 at 08:16, wrote:
> Hello,
>
>
>
>I just upgraded to cloudstack 4.18.1 from 4.17.2, and looks like the
> offering change/scale still not working. Any suggestion how can I scale
> these VMs without rebuild?
>
>
>
>(localcloud) 🐱 > scale vir
Thank you. I recently installed a new SSL certificate via UI, which I
believe caused this issue. Sadly, I could not fix it even after
destroying SSVM. I deleted all ISOs and had to re-register them and now
it works as expected.
On 9/18/23 09:00, Andrija Panic wrote:
Hi,
you should check the
Hi,
you should check the mgmt logs to see WHY this ISO failed to register
(perhaps there is HTTPS ssl issue or similar).
No reason to destroy SSVM (though it doesn't hurt) - a simple SSVM reboot
(or service cloud restartinside SSVM) will trigger checking all the
templates/ISOs and try to reg