Bzr talks to edge to translate lp:foo type urls

[Tom Haddon]

Bzr talks to edge to translate lp:foo type urls into bzr+ssh://bazaar.launchpad.net/~user/foo/trunk or http://bazaar.launchpad.net/~user/foo/trunk URLs.

To quote Michael Hudson from an RT ticket:

"Historically it's something to do with Python's XML-RPC client library not handling redirects well, and the prod -> edge redirect occasionally screwed things up. I don't know if these recollections are right and even less if the reasons still apply."

It seems to be a bad thing to be using edge for a production service like this.

[Aaron Bentley (abentley)]

I thought we did it because on a particular release, production was broken, but edge worked.

[Tom Haddon (mthaddon)]

That's possible, but it's not a good reason to keep it there.

[Francis J. Lacoste (flacoste)]

In the meantime, the env variable BZR_LP_XMLRPC_URL=http://xmlrpc.launchpad.net/bazaar/ can be set to work around the default.

[Данило Шеган (danilo)]

We should probably use the work-around in translations if it doesn't get fixed soon enough.

[Jonathan Lange (jml)]

Danilo, why don't you just fix it?

[Данило Шеган (danilo)]

Because I have a million things to deal with right now, and this is a very low priorty for us compared to the other stuff we are dealing with.

[Martin Packman (gz)]

Submitted a branch with the swap over done for the bzr launchpad plugin, not sure if there's other changes needed elsewhere.

[Martin Packman (gz)]

Change moving launchpad plugin over to production landed in r5244. One part had to be backed out due to bug 583667 Robert encountered with lp-propose, but that's unrelated to xml rpc.

This bug is filed against three projects, is there any further work here that needs doing?

[Robert Collins (lifeless)]

translations probably wants to cherrypick the two commits we made for this (5244 + 5247) because it was filed to address a production issue they are having with lp: resolution.

[Данило Шеган (danilo)]

Next steps for deploying the fix:
 * make sure ports are open in the firewall between cesium and xmlrpc.lp.net
 * get bzrlib revisions which fix this onto cesium
 * close out ports between cesium and xmlrpc.edge.lp.net
 * test everything that might be trying to access bzr branches from cesium

FWIW, this could be affecting daily builds stuff as well, though I don't really know for sure. At the very least, it'd have to be tested properly before a fix is rolled out.

[Данило Шеган (danilo)]

I am expecting bzr update for Launchpad early next cycle.