Re: VM in incorrect state

I did nothing unsual to the nic. What it is true is that: I had two sessions opened: - 1 session as user. This user owns two specific networks. And this VM had two nics on those networks. - 1 session ad Admin The user belongs to a specific domain. Therefore the admin cannot do all

Re: VM in incorrect state

I saw something like this when VM ‘lost’ a NIC somehow. Can you check if there is at least one NIC assigned to the VM? Fix was to restore NIC record for that VM in the DB. Another option (if VM is slated for destruction) is just to change VM state to ‘Destroyed’ and garbage collector thread

Re: VM in incorrect state

Hi Natalia, This problem is caused at class method “org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.releaseNic(VirtualMachineProfile, long)” line 1631 as you can see by the stack trace. Did you change something else in the database or ACS while these VMs were stuck in "stopping"?

Re: VM in incorrect state

Dear Rafael, Thre requested information: ACS version: 4.9.0 hypervisors used: kvm storage systems used: gluster as primary networking: advanced And this is the error... 2017-02-14 17:48:56,112 DEBUG [c.c.u.d.T.Transaction] (API-Job-Executor-2:ctx-4eca9fd0 job-1329 ctx-39cd3fd6)

Re: VM in incorrect state

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.

Re: VM in incorrect state

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

Re: VM in incorrect state

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

VM in incorrect state

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,