Comment 4 for bug 1333682

A thought, the 1.19 code is expecting Login to be able to return a list of known hosts to connect to, and is probably trying to cache those addresses (to handle HA, etc).
However, if a machine-1 agent came up as 1.19 and machine-0 was still 1.18, is it possible that 1.19 is calling Login, getting a response that doesn't have any apiHostPorts in it, and then triggering a rewrite of agent.conf and *stripping out* the data?