Bug 1344337

Summary: If connection issues happened, fallback to XMLRPC protocol is much faster than expected
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: BLL.InfraAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: movciari
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, gklein, lsvaty
Target Milestone: ovirt-4.0.0-rcFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1345779 (view as bug list) Environment:
Last Closed: 2016-07-26 10:58:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1345779    

Description Martin Perina 2016-06-09 12:37:45 UTC 
Description of problem:

If there is a connection issue during 1st connection to the host after installation, we switch to XMLRPC protocol immediately instead of trying number of times as defined in ProtocolFallbackRetries.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2016-06-09 12:38:43 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 Martin Perina 2016-06-10 15:10:37 UTC 
Setting target release to 4.0.0 as it's included in today's 4.0.0.4 build
Comment 4 Lukas Svaty 2016-07-26 10:58:53 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA