Bug #3876
Poweroff + Delete leaves VM defined in vCenter
| Status: | Closed | Start date: | 07/16/2015 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: |  Tino Vázquez | % Done: | 90% | ||
| Category: | vCenter | ||||
| Target version: | Release 4.14 | ||||
| Resolution: | fixed | Pull request: | |||
| Affected Versions: | OpenNebula 4.12 |
Description
Wed Jul 15 19:44:32 2015 [Z0][VM][I]: New state is ACTIVE
Wed Jul 15 19:44:32 2015 [Z0][VM][I]: New LCM state is PROLOG
Wed Jul 15 19:44:32 2015 [Z0][VM][I]: New LCM state is BOOT
Wed Jul 15 19:44:32 2015 [Z0][VMM][I]: Generating deployment file: /home/oneadmin/4.14/var/vms/68/deployment.0
Wed Jul 15 19:44:32 2015 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Wed Jul 15 19:44:57 2015 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Wed Jul 15 19:44:57 2015 [Z0][VMM][I]: Successfully execute network driver operation: post.
Wed Jul 15 19:44:57 2015 [Z0][VM][I]: New LCM state is RUNNING
Wed Jul 15 19:47:59 2015 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Wed Jul 15 19:48:05 2015 [Z0][VMM][I]: Successfully execute virtualization driver operation: shutdown.
Wed Jul 15 19:48:05 2015 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Wed Jul 15 19:48:05 2015 [Z0][VM][I]: New state is POWEROFF
Wed Jul 15 19:48:05 2015 [Z0][VM][I]: New LCM state is LCM_INIT
Wed Jul 15 19:48:16 2015 [Z0][VM][I]: New LCM state is LCM_INIT
Wed Jul 15 19:48:16 2015 [Z0][VM][I]: New state is DONE
Wed Jul 15 19:48:17 2015 [Z0][LCM][E]: epilog_success_action, VM in a wrong state
Associated revisions
Bug #3876: Adjust vcenter driver for delete operation after poweroff/stop/suspend
Bug #3876: Trigger cancel on other states than active if host is hybrid
Bug #3876: Fix erasing VMs in pending
Bug #3876: Adjust locking order in vm and host
Bug #3876: Initialize error message
History
#1
Updated by Tino Vázquez almost 6 years ago
- % Done changed from 0 to 90
Keep open to evaluate other options in the core side
#2
Updated by Tino Vázquez almost 6 years ago
- Status changed from New to Closed
- Resolution set to fixed
#3
Updated by Sebastiaan Smit over 4 years ago
It looks like this bug still exists in 5.2.1.
If we do a "terminate" action after "power off" the VM disappears from OpenNebula, but stays within vcenter. This gives a couple of side effects, like vcenter alarms when the ip is reassigned to another new vm and a mac address conflict arrises. See below the log of a specific case.
Wed Mar 8 14:34:14 2017 [Z0][VM][I]: New state is ACTIVE
Wed Mar 8 14:34:14 2017 [Z0][VM][I]: New LCM state is PROLOG
Wed Mar 8 14:34:14 2017 [Z0][VM][I]: New LCM state is BOOT
Wed Mar 8 14:34:14 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/247/deployment.0
Wed Mar 8 14:34:14 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Wed Mar 8 14:34:23 2017 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Wed Mar 8 14:34:23 2017 [Z0][VMM][I]: Successfully execute network driver operation: post.
Wed Mar 8 14:34:23 2017 [Z0][VM][I]: New LCM state is RUNNING
Wed Mar 8 14:34:48 2017 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Wed Mar 8 14:34:50 2017 [Z0][VMM][I]: Successfully execute virtualization driver operation: shutdown.
Wed Mar 8 14:34:50 2017 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Wed Mar 8 14:34:50 2017 [Z0][VM][I]: New state is POWEROFF
Wed Mar 8 14:34:50 2017 [Z0][VM][I]: New LCM state is LCM_INIT
Wed Mar 8 14:36:19 2017 [Z0][VM][I]: New state is ACTIVE
Wed Mar 8 14:36:19 2017 [Z0][VM][I]: New LCM state is EPILOG
Wed Mar 8 14:36:19 2017 [Z0][VM][I]: New state is DONE
Wed Mar 8 14:36:19 2017 [Z0][VM][I]: New LCM state is LCM_INIT