To: [email protected]
> Subject: Re: Cloudstack database and orphaned entities
>
> Hi Yordan,
>
> I think the best approach would be to submit an issue in the GitHub page of
> ACS and document the exact steps on reproducing this issue. From there on
> someone could p
PM
To: [email protected]
Subject: Re: Cloudstack database and orphaned entities
Hi Yordan,
I think the best approach would be to submit an issue in the GitHub page of ACS
and document the exact steps on reproducing this issue. From there on someone
could pick it up and fix it for the
Hi Yordan,
I think the best approach would be to submit an issue in the GitHub page of ACS
and document the exact steps on reproducing this issue. From there on someone
could pick it up and fix it for the next LTS release. Honestly I don’t think
that would be a common production problem, since
Dear all,
While testing different setups and also deleting them I noticed
that it is occasional/common occurrence that orphaned system VMs or hosts
remain in the database.
For example - during removal of a zone (system VMs, secondary
storages, host, cluster, pod
