On Thu, Oct 10, 2013 at 05:27:03PM +0100, Dean Arnold wrote:
Hi Neil,
Earlier today I configured two new virtual machines to test the master/worker setup and I have managed to get this to work now. For this I installed a the master and slave from scratch with the LAVA_DB_ALLOWREMOTE variable set on the master, and all went well. I was able to do a couple of qemu runs on the worker with no issues.
It looks as though the problem I was seeing on our production LAVA setup, was down to my master configuration, which wasn't correct. When doing an upgrade of a master instance, the deployment tool doesn't carry out the steps for enabling remote workers, even with the LAVA_DB_ALLOWREMOTE variable set. I had then corrected some of the steps manually, but had missed a couple of bits, which is why I ended up with a *kind of* working setup.
When I did fresh install on my test setup today, the lava-deployment-tool handled the extra steps perfectly.
Thanks for your help with this, now I have a working setup to diff my production version against, I can apply the missing bits of config to the master. Alternatively I'll just do a fresh install and restore the database from a backup :)
I don't know if this is something you guys would like to be automated by the lava-deployment-tool during upgrades, or whether some steps on the wiki for the extra bit of config would be enough? If you need me to raise a ticket/bug for this I can do?
Yes, please open a bug against lava-deployment-tool. It should be able to handle upgrades from older versions without losing the setup for allowing access to the remote workers.