XO / Migration issue

scottalanmiller

From Github:

After migrating a VM, a "ghost" VM is shown in XO. This VM doesn't appear in XC, and it goes away after restarting xo-server.

https://cloud.githubusercontent.com/assets/7101313/13331481/4882d8a8-dbc3-11e5-923c-ddf2bfb0d365.jpg

https://cloud.githubusercontent.com/assets/7101313/13331488/53cfe200-dbc3-11e5-95ac-81236ec1c3ae.jpg

stacksofplates

I don't have two hosts to try on, but I did notice that when you import a VM creates what looks like a second temporary VM during the import. It disappears once the import is completely done. Not sure if these two things are related or not.

Deleted74295

NTG Lab would be nice for testing this

Danp

Yeah... it's like the temporary VM is being "cached" by XO until you restart xo-server. Since @olivier can't reproduce it, I thought someone here could try testing it for me.

Danp

Anybody willing to give this a go?!

dafyre

I'm actually not running XO/XS anymore... switched over to KVM due to other issues.

stacksofplates

@Danp said:

Anybody willing to give this a go?!

I would if I had more than one host.

olivier

Made around 50 migrations today, no issues, but I'm making mainly those tests on next-release. I really can't explain why this "duplicate" VM is appearing with an UUID coming from nowhere...

Danp

@olivier said:

Made around 50 migrations today, no issues, but I'm making mainly those tests on next-release. I really can't explain why this "duplicate" VM is appearing with an UUID coming from nowhere...

Does a temporary VM with a new UUID get created just prior to the final movement of the VM from one pool to another? This is what I'm seeing and this VM is what remains as the "ghost" once the migration is complete.

P.S. I recently tested this on 'next-release' and the observed the same thing.

Danp

@olivier FWIW, I just retested on the latest next-release with the same results. If I disconnect / reconnect the server from within XO, the "ghost" VM is now gone.