Bug 1345779 - [downsream clone - 3.6.8] If connection issues happened, fallback to XMLRPC protocol is much faster than expected
Summary: [downsream clone - 3.6.8] If connection issues happened, fallback to XMLRPC p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-3.6.8
: ---
Assignee: Martin Perina
QA Contact: movciari
URL:
Whiteboard:
Depends On: 1344337
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-13 07:31 UTC by rhev-integ
Modified: 2016-07-27 14:12 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1344337
Environment:
Last Closed: 2016-07-27 14:12:10 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1507 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager (rhevm) bug fix 3.6.8 2016-07-27 18:10:22 UTC
oVirt gerrit 58911 0 master MERGED core: Fix fallback to XMLRPC during protocol detection 2016-06-13 07:31:33 UTC
oVirt gerrit 58965 0 ovirt-engine-4.0 MERGED core: Fix fallback to XMLRPC during protocol detection 2016-06-13 07:31:33 UTC
oVirt gerrit 59032 0 ovirt-engine-3.6 MERGED core: Fix fallback to XMLRPC during protocol detection 2016-06-13 11:03:29 UTC

Comment 1 Martin Perina 2016-06-13 08:31:25 UTC 
Retargeting to 3.6.8 as this issue haven't been raised in production so far and we will have more time to verify the fix
Comment 3 errata-xmlrpc 2016-07-27 14:12:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1507.html
Note You need to log in before you can comment on or make changes to this bug.