[HTCondor-users] CCB private address

[Raphael KleinemÃhl <kleinemuehl@xxxxxxxxxxxxxxxx>]

Hi all,

I'm currently building a test setup where the central manager runs in a 
docker container and a schedd runs in a separate container (potentially 
on a different machine).
The workers are running somewhere else, where incoming connections won't 
be allowed. So using a CCB seemed like the way to go. I'm using version 
9.0.15.

I'm still a bit new to HTCondor, so I'm not sure if I understand it 
correctly. But I think the problem is that the private address of the 
CCB is not advertised.



The collector and negotiator advertise their addresses correctly:
$ condor_status -collector -l
MyAddress = 
"<192.168.56.1:9618?PrivAddr=%3c172.20.0.2:9618%3fsock%3dcollector%3e&PrivNet=docker_cm&addrs=192.168.56.1-9618&alias=cm.cobaldtardis&noUDP&sock=collector>"

$ condor_status -negotiator -l
MyAddress = 
"<192.168.56.1:9618?PrivAddr=%3c172.20.0.2:9618%3fsock%3dnegotiator_11_1fa1%3e&PrivNet=docker_cm&addrs=192.168.56.1-9618&alias=cm.cobaldtardis&noUDP&sock=negotiator_11_1fa1>"

And the scheduler advertises the CCB, but not the private address:
$ condor_status -schedd -l
MyAddress = 
"<192.168.56.3:9619?CCBID=192.168.56.1:9618%3fPrivNet%3ddocker_cm%26addrs%3d192.168.56.1-9618%26alias%3dcm.cobaldtardis%26noUDP%26sock%3dcollector#111&PrivAddr=%3c172.18.0.2:9619%3fsock%3dschedd_11_1fa1%3e&PrivNet=docker&addrs=192.168.56.3-9619&alias=sub.cobaldtardis&noUDP&sock=schedd_11_1fa1>"

This leads to the negotiator being unable to connect to the schedd:
$ cat /var/log/condor/NegotiatorLog
08/03/22 10:42:30 Failed to reverse connect to schedd 
cobald@cobaldtardis via CCB.
08/03/22 10:42:30     Failed to connect to cobald@cobaldtardis 
(<192.168.56.3:9619?CCBID=192.168.56.1:9618%3fPrivNet%3ddocker_cm%26addrs%3d192.168.56.1-9618%26alias%3dcm.cobaldtardis%26noUDP%26sock%3dcollector#111&PrivAddr=%3c172.18.0.2:9619%3fsock%3dschedd_11_1fa1%3e&PrivNet=docker&addrs=192.168.56.3-9619&alias=sub.cobaldtardis&noUDP&sock=schedd_11_1fa1>)



On my test setup I can allow incoming connections and leave out the CCB. 
If I do that, everything works perfectly. Just adding the CCB breaks the 
setup.
So, my question is: shouldn't the private address of the CCB be advertised?
And if this behavior is intended, why is 'PrivNet' included at all?

Thanks for the help,
  Raphael