Bug 1397919 - connection to ovirt broker doesn't work
Summary: connection to ovirt broker doesn't work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-boxes
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1395724 1477211
TreeView+ depends on / blocked
 
Reported: 2016-11-23 14:53 UTC by Vladimir Benes
Modified: 2020-01-07 13:06 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:06:03 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 774899 0 Normal RESOLVED ovirt seems to be completely broken 2020-01-07 12:27:27 UTC

Description Vladimir Benes 2016-11-23 14:53:47 UTC
Description of problem:
I am trying to add ovirt broker (4.0.4) version but I have no luck with it. We are probably hitting the certificate issue again.

I am adding internal ovirt broker ovirt://<engine_fqdn> with all certificates imported as stated here:
https://www.ovirt.org/develop/release-management/features/infra/pki/#services

but it looks something is broken and "Connection to ovirt broker failed" is not helpful.

running as:
G_MESSAGES_DEBUG=all gnome-boxes

says:
(gnome-boxes:19895): libgovirt-DEBUG: CA certificate URI: https://<engine_fqdn>/ovirt-engine/ca.crt

so this seems to be incorrect


Version-Release number of selected component (if applicable):
3.22.2-1

How reproducible:
always

Steps to Reproduce:
1. open boxes and create new box via url
2. add ovirt://<engine_fqdn>

Actual results:
Connection to ovirt broker failed

Expected results:
sign in dialog

Additional info:

Comment 1 Felipe Borges 2020-01-07 13:06:03 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.