Bug 1067745

Description of problem:
rhts-sync-block cannot reach other hosts in a recipe set. beah reports "Connection refused", because the remote beah is only listening on loopback instead of on all interfaces.

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

How reproducible:
always

Steps to Reproduce:
1. Run a multihost recipe set with a task that uses rhts-sync-block/rhts-sync-set, for example /distribution/beaker/Sanity/sync-set_block-tests

Actual results:
rhts-sync-block calls never complete, console has this error:

2014-02-20 04:39:00,415 backend linfo: INFO BackendFactory: Started to connect.  
2014-02-20 04:39:00,418 backend linfo: INFO BackendFactory: Connection failed. Reason: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by other side: 111: Connection refused.  

Expected results:
rhts-sync-block waits for corresponding state to be reached on the remote hosts and then returns.

The console will have this on the local side:

2014-02-18 08:44:50,365 backend linfo: INFO BackendFactory: Connected.  Address: <twisted.internet.address.IPv4Address object at 0x24bc110>  

and a corresponding message on the remote side:

2014-02-18 08:45:08,582 beah buildProtocol: INFO BackendListener: Connected.  Address: IPv4Address(TCP, '123.123.123.123', 46047)  

Additional info:
In beah 0.6.48 the TaskListener only listens on loopback but the BackendListener listens on all interfaces.
In beah 0.7 both TaskListener and BackendListener claim to listen on loopback but are actually listening on all interfaces.
In beah 0.7.2 both TaskListener and BackendListener actually only listen on loopback as they claimed, but that is not what they should be doing.