Hi Tino, I think we have a misunderstanding. This is what I did:
- Shutdown the VM from within the guest - OpenNebula learned that the machine was powered off - From within OpenNebula delete the VM - VM is removed from OpenNebula's database - VM stays on vcenter cluster (in poweroff state) I expected that OpenNebula would delete the VM from my vcenter cluster. If I look at the VM state diagram (*1) I interpret that from any state you can go do a delete and go to "done". Or is my assumption wrong? Best regards, *1) http://archives.opennebula.org/_media/documentation:rel4.4:states-simple.png -- Sebastiaan Smit Echelon BV E: b...@echelon.nl T: (088) 3243566 (hoofdnummer) T: (088) 3243505 (servicedesk) F: (053) 4336222 W: www.echelon.nl KVK: 06055381 -----Oorspronkelijk bericht----- Van: Tino Vazquez [mailto:cvazquez@opennebula.systems] Verzonden: woensdag 11 februari 2015 12:44 Aan: Sebastiaan Smit CC: users@lists.opennebula.org Onderwerp: Re: [one-users] Deleting vcenter VM's in POWEROFF state leaves stray VM's on cluster Hi Sebastiaan, Thanks a lot for the testing, this is precious feedback. In this I'm afraid that, by design, and to maintain compatibility with other hypervisors, we cannot change the OpenNebula assumption that if the VM is in poweroff, OpenNebula thinks it has been removed from the hypervisor. There are two alternatives: * at the time of powering off in vCenter, unregister it as well * poweron the VM first, and then delete it Best, -Tino -- OpenNebula - Flexible Enterprise Cloud Made Simple -- Constantino Vázquez Blanco, PhD, MSc VP of Engineering | Head of Research at OpenNebula Systems cvazquez@OpenNebula.Systems | @OpenNebula -- Confidentiality Warning: The information contained in this e-mail and any accompanying documents, unless otherwise expressly indicated, is confidential and privileged, and is intended solely for the person and/or entity to whom it is addressed (i.e. those identified in the "To" and "cc" box). They are the property of OpenNebula.Systems S.L.. Unauthorized distribution, review, use, disclosure, or copying of this communication, or any part thereof, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify us immediately by e-mail at abuse@opennebula.systems and delete the e-mail and attachments and any copy from your system. OpenNebula's thanks you for your cooperation. On 11 February 2015 at 11:55, Sebastiaan Smit <b...@echelon.nl> wrote: > Hi Tino, > > Yes I did. It was a robustness check. One detected the poweroff state, > but was not able to clean it up after removal. > > > Best, > > Sebastiaan > > > > Op 11 feb. 2015 om 11:09 heeft Tino Vazquez > <cvazquez@opennebula.systems> het volgende geschreven: > > Hi Sebastiaan, > > We are trying to reproduce this problem. From the log it looks like > the VM went to poweroff state on its own. Did you power it off from the > vCenter? > > Best, > > -Tino > > On Tue Feb 10 2015 at 1:04:33 PM Sebastiaan Smit <b...@echelon.nl> wrote: >> >> Hi list, >> >> >> >> I’ve encountered strange behavior with my vcenter 4.10.2 demo setup. >> When I delete a VM which is in POWEROFF state, it disappears as >> expected from OpenNebula, but remains in poweroff state on my vcenter >> cluster. The last log lines of the VM are the following: >> >> >> >> Wed Feb 4 22:32:47 2015 [Z0][VMM][I]: Successfully execute network >> driver >> operation: pre. >> >> Wed Feb 4 22:41:23 2015 [Z0][VMM][I]: Successfully execute >> virtualization driver operation: deploy. >> >> Wed Feb 4 22:41:23 2015 [Z0][VMM][I]: Successfully execute network >> driver >> operation: post. >> >> Wed Feb 4 22:41:23 2015 [Z0][LCM][I]: New VM state is RUNNING >> >> Tue Feb 10 12:55:06 2015 [Z0][VMM][I]: VM running but monitor state >> is POWEROFF >> >> Tue Feb 10 12:55:06 2015 [Z0][DiM][I]: New VM state is POWEROFF >> >> Tue Feb 10 12:56:18 2015 [Z0][VMM][I]: VM running but monitor state >> is POWEROFF >> >> Tue Feb 10 12:57:30 2015 [Z0][VMM][I]: VM running but monitor state >> is POWEROFF >> >> Tue Feb 10 12:57:37 2015 [Z0][DiM][I]: New VM state is DONE. >> >> Tue Feb 10 12:57:37 2015 [Z0][LCM][E]: epilog_success_action, VM in a >> wrong state >> >> >> >> Has anybody else encountered the same situation? >> >> >> >> Thanks in advance, >> >> -- >> >> Sebastiaan Smit >> >> Echelon BV >> >> E: b...@echelon.nl >> >> T: (088) 3243566 (hoofdnummer) >> >> T: (088) 3243505 (servicedesk) >> >> F: (053) 4336222 >> >> W: www.echelon.nl >> >> KVK: 06055381 >> >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
