Could you share the error here?
Could you also post some more information (stack trace of the erro, ACS
version, hypervisors used, storage systems used, networking
configuration[advanced or basic])?
On Mon, Feb 13, 2017 at 2:31 PM, Natalia Costas Lago
wrote:
>
> I did that.
I did that. Now I am able to Destroy the VM... but I get an error when I
try to expunge. I can recover the VM.. destroy.. .but not expunge.
El 13/02/2017 a las 20:22, Rafael Weingärtner escribió:
I have already had this experience of VMs getting stuck in “Stopping”
state. It is quite
I have already had this experience of VMs getting stuck in “Stopping”
state. It is quite trivial the task, you just have to make sure you are
changing the states of the right VMs. You just have to change the state to
“Stopped” on the database.
On Mon, Feb 13, 2017 at 2:07 PM, Natalia Costas Lago
Dear all,
I stopped two VMs and it seems they where stopped but they appear
"Stopping" in the user interface. I have seen workarounds to this issue
that update the status of the VM directly in the database.. but this
seems risky to me.
How should I proceed? Is that the only way?
Thanx,
When the new host has a different network config, Add it to a new cluster in
the vCenter and then add that Cluster in ACS with cluster override traffic
labels for guest and public traffic. Refer the params: guestvswitchname,
guestvswitchtype, publicvswitchname and publicvswitchtype parameters
Hi Merlin,
It seems Agent is not running in CPVM. Can you please post the log
/var/log/cloud/cloud.log in CPVM. Also, reboot CPVM and observe the boot logs.
If you find any errors, please post them.
If agent is running in CPVM, check its connectivity to MS at port 8250.
Regards,
Suresh
On