Hi Martin,
My initial fear was that it was trying to execute the VM twice,
however
it turned out to be just a GUI issue.
> VM management was unaffected.
How many times do you see the VM in the REST API? /ovirt-engine/api/vms
If you see two of them, do they have different or the same ID?
I didn't notice any differing IDs in the logs & it was the same in the
interface (although it wasn't possible to select the 2 listed items
independently, they displayed & acted as a single item).
I've made a note to check the REST API if it occurs in the future, however
my HE has since borked itself & I'm now in the process of
restoring/redeploying it. I've got access to the logs, but the engine & API
are now offline.
Doug
On Tue, Jan 17, 2017 at 1:52 PM, Doug Ingham <dougti(a)gmail.com>
wrote:
> Hi Tomas,
>
> Heh, that seems interesting. Any chance you have the engine and vdsm logs
> from the time the second vm has shown up?
>
>
> I'll see if there's anything shareable in the Engine logs during the
> window it happened, however VDSM logs will be difficult as the VMs moved
> around a lot whilst I was trying to get everything back online.
>
>
> BTW if you restart the VM, will one of them disappear? or you will have 2
> down VMs?
>
>
> It's persisted reboots of the VM, hosts and the Engine.
>
> My initial fear was that it was trying to execute the VM twice, however
> it turned out to be just a GUI issue. VM management was unaffected.
>
> Doug
>
> On Mon, Jan 9, 2017 at 8:09 PM, Doug Ingham <dougti(a)gmail.com> wrote:
>
>> Hi all,
>> We had some hiccups in our datacenter over the new year which caused
>> some problems with our hosted engine.
>>
>> I've managed to get everything back up & running, however now one of the
>> VMs is listed twice in the UI. When I click on the VM, both items are
>> highlighted & I'm able to configure & manage the VM as usual.
>> The FQDN & other things are picked up from the guest agent & displayed
>> on the UI as usual, however the CPU, RAM & Uptime stats for one of the pair
>> continue to show the stats from when the cluster died.
>>
>> Any ideas?
>>
>> oVirt 4.0.3.7
>> Gluster 3.8.5
>> CentOS 7
>>
>> [image: Inline images 1]
>>
>> Many thanks,
>> --
>> Doug
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>>
> .
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
--
Doug