Collisions in bzr-version-info.py when running two app servers from the same tree

[Tom Haddon]

If you are running two instances of the app server out of the same tree, the fact that they both use bzr-version-info,py and make start/make stop deletes and recreates this can mean that there are collisions between them. If we appended ${LPCONFIG} to the filename this would be avoided.

Attached is a patch that would do this for the Makefile, but I'm not sure what other portions of code look for this filename and would need to be changed accordingly.

[Tom Haddon (mthaddon)]

Promoting to "high" importance because this is blocking the LOSAs from moving to a new deployment model where we push code to a new location, build it, then stop the service, rename the new code to replace the old code, and then start the service. In the latest rollout to production this triggered the problem on all 4 application servers, presumably because with this method, the gap between services being started is so much smaller.

[Christian Reis (kiko)]

If you think not updating the file would work, then can you give https://pastebin.canonical.com/10155/ a spin to see if it fixes the problem on staging?

[Tom Haddon (mthaddon)]

Fixed in RF 7180

[Tom Haddon (mthaddon)]

Released with 2.1.10