Bug 1254672

Summary:	cannot reconnect to ovirt machine after Boxes kicked me out
Product:	Red Hat Enterprise Linux 7	Reporter:	Vladimir Benes <vbenes>
Component:	gnome-boxes	Assignee:	Felipe Borges <feborges>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	elima, mclasen
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-07 13:05:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimir Benes 2015-08-18 15:48:15 UTC

Description of problem:
Boxes are unable to connect to the VM after this error with yet another one: (gnome-boxes:30615): Boxes-WARNING **: machine.vala:580: Failed to connect to w7x64-35-1-dj: Couldn't start oVirt VM 'w7x64-35-1-dj': Conflict

Version-Release number of selected component (if applicable):
gnome-boxes-3.14.3.1-6
libgovirt-0.3.3-1.el7

How reproducible:
always

Steps to Reproduce:
this "Conflict" error is more generic as it happens after any 
ovirt VM disconnection. This can be caused by powering off from VM itself,
from web UI ,or just after disconnection caused by not in RUNNING state
issue (1034354)

Comment 1 Vladimir Benes 2015-08-18 15:49:15 UTC

workaround is to restart Boxes

Comment 2 Matthias Clasen 2015-08-20 17:53:55 UTC

we have deferred working ovirt connections with gnome-boxes to 7.3

Comment 5 Felipe Borges 2020-01-07 13:05:41 UTC

We have removed support for ovirt upstream since 3.30. Please REOPEN if fixing this issue is really important.