Bug 1059079

Summary: Ensure a new connection is created after XML-RPC failure
Product: [Retired] Beaker Reporter: Nick Coghlan <ncoghlan>
Component: lab controllerAssignee: Nick Coghlan <ncoghlan>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.15CC: aigao, asaha, dcallagh, llim, qwan, rmancy, xjia
Target Milestone: 0.15.4   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-18 01:38:46 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 Nick Coghlan 2014-01-29 06:11:45 UTC 
Reviewing the kobo XML-RPC code suggests that kobo may sometimes (always?) attempt to reuse an existing socket connection on Python 2.6 and earlier.

I suspect this may cause misbehaviour in some circumstances (such as when the original failure was a timeout during SSL/TLS processing)

We should ensure the underlying transport is always closed in our own failure handling/XML-RPC retry loop.
Comment 1 Nick Coghlan 2014-01-29 06:27:59 UTC 
On Gerrit: http://gerrit.beaker-project.org/2734
Comment 4 xjia 2014-02-14 10:17:42 UTC 
After smoke test, QE didn't find regression bugs for this issue. So move to "VERIFIED"
Comment 5 Dan Callaghan 2014-02-18 01:38:46 UTC 
Beaker 0.15.4 has been released.