# Missing wild VMS following upgrade from v5.12.0.3 to v6.2.0.1

**URL:** https://forum.opennebula.io/t/missing-wild-vms-following-upgrade-from-v5-12-0-3-to-v6-2-0-1/10661
**Category:** Installation & Configuration
**Created:** [June 17, 2022, 2:57pm UTC](https://forum.opennebula.io/t/missing-wild-vms-following-upgrade-from-v5-12-0-3-to-v6-2-0-1/10661 "2022-06-17T14:57:30Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Colm\_Ennis](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/colm_ennis/32/5969_2.png) [@Colm\_Ennis](https://forum.opennebula.io/u/Colm_Ennis)
#### Post date: [June 18, 2022, 8:06am UTC](https://forum.opennebula.io/t/missing-wild-vms-following-upgrade-from-v5-12-0-3-to-v6-2-0-1/10661/2 "2022-06-18T08:06:31Z")

</div>

After fiddling around for several hours, I eventually discovered a workaround here.

Looking at the VM delete workaround I used which came from [here](https://forum.opennebula.io/t/solved-remove-imported-vms/6936/10):

> onedb update-body vm --id 255  
> Remove the tag IMPORTED  
> onevm recover --delete-db 255

Removal of the IMPORTED tag means that ‘–delete-db’ leaves behind a record in the the vm\_import table which in turn prevents the VM from ever appearing as a wild.

To fix, I had to run the the following from the DB:

> MariaDB [opennebula]\> delete from vm\_import where vmid = ‘255’;

Colm

---

_[View the full topic](https://forum.opennebula.io/t/missing-wild-vms-following-upgrade-from-v5-12-0-3-to-v6-2-0-1/10661)._