RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1254672 - cannot reconnect to ovirt machine after Boxes kicked me out
Summary: cannot reconnect to ovirt machine after Boxes kicked me out
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-boxes
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-18 15:48 UTC by Vladimir Benes
Modified: 2020-01-07 13:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-07 13:05:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.