Hi all,
Can anyone help Dean at ARM out here?
Thanks
Dave
On 2 Oct 2013, at 15:49, Dean Arnold <Dean.Arnold(a)arm.com> wrote:
> Hi Dave/Matt,
>
> I have recently installed a remote worker on a new server, but I am unable to get it to talk to the master properly. I just wanted to check if what I have done is correct and if I had missed anything.
>
> Here are the steps I followed..
>
> My master server (pdsw-lava) is running a "production" instance of LAVA. I have updated the LAVA version to the latest using the git lava-deployement-tool.
>
> On new dispatcher (pdsw-lava-dispatcher01), using the latest git lava-deployement-tool, I installed the remote worker in the following way:
> $ lava-deployment-tool setup
> $ lava-deployment-tool installworker production
>
> Giving the IP address, hostname etc of the master when prompted along with the database info.
>
> When instructed to do the following..
>
> Running installation step remote_fs
> Configuring remote fileystem access production
> Please add the following public key into your master node's
> /srv/lava/instances/production/home/.ssh/authorized_keys file
>
> -------- WORKER NODE PUBLIC KEY STARTS HERE --------
> ssh-rsa .... ssh key used by LAVA for sshfs
> -------- WORKER NODE PUBLIC KEY ENDS HERE --------
>
> I had to create the /home/.ssh/authorized_keys file and directories under /srv/lava/instances/production/ on the master as they never existed.
>
> On pdsw-lava-dispatcher01 I created these directories:
> /srv/lava/instances/production/etc/lava-dispatcher/devices
> /srv/lava/instances/production/etc/lava-dispatcher/device-types
>
> and SCP'd the contents of /srv/lava/instances/production/etc/lava-dispatcher/device-types over from my master server.
>
> I removed the device config file pdswlava-vetc2-06.conf from /srv/lava/instances/production/etc/lava-dispatcher/devices on the master and added this to the same directory on the remote worker.
>
> I then restarted lava on both servers (just in case it was needed).
>
> I submitted a job on the master using pdswlava-vetc2-06 and this stayed in the "submitted" state but never did anything.
>
> After a while I removed the pdswlava-vetc2-06.conf file from /srv/lava/instances/production/etc/lava-dispatcher/devices on the remote worker and added this back into the same directory on the master. Instantly the job ran as expected.
>
> Can you think of anything I have missed in my setup which would prevent the master and worker from talking to each other? Is there anything I should be seeing in the web UI of the master to indicate it is connected to a remote worker, or is there an easy way to test the connection between the two?
>
> Apologies if I have just done something really dumb, it wouldn't be the first time :)
>
> Cheers
> Dean
>
> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
>
CC'ing LAVA guys
On 26 September 2013 15:46, Maxim Uvarov <maxim.uvarov(a)linaro.org> wrote:
> As I understand this log right:
> https://validation.linaro.org/scheduler/job/74753/log_file
>
> Arndale booted with standard LE rootfs. Then there is wget rootfs and chroot
> to it.
> And of course any commands under chroot will fail.
>
> So I think for now it's impossible to run BE in lava boards unless we will
> set up any board with
> BE env or remove chroot from set up scripts.
>
> Is chroot really needed for this? :
> chroot /mnt/root ln -sf /bin/true /usr/sbin/flash-kernel
>
> Thank you,
> Maxim.
Sorry I have an error at the end.
May some one help me?
BEST REGARDS
NOVELLO G.
The file is not there I THINK THAT IT PRESENT IN THE TARGER
WE HAVE TO MOVE IT.
umount /mnt
bash-4.2 [rc=0]# <LAVA_DISPATCHER>2013-10-05 01:15:33 PM INFO: General
Exception: [Errno 2] No such file or directory:
u'/srv/lava/instances/dev/var/www/lava-server/images/tmpqF0IvL/1380971716.73/lava/results/swcontext/build.txt'
<LAVA_DISPATCHER>2013-10-05 01:15:33 PM DEBUG: finally status fail
<LAVA_DISPATCHER>2013-10-05 01:15:33 PM WARNING: [ACTION-E]
lava_test_shell is finished with error ([Errno 2] No such file or
directory:
u'/srv/lava/instances/dev/var/www/lava-server/images/tmpqF0IvL/1380971716.73/lava/results/swcontext/build.txt').
ErrorMessage: [Errno 2] No such file or directory:
u'/srv/lava/instances/dev/var/www/lava-server/images/tmpqF0IvL/1380971716.73/lava/results/swcontext/build.txt'
Lava failed at action lava_test_shell with error:[Errno 2] No such file
or directory:
u'/srv/lava/instances/dev/var/www/lava-server/images/tmpqF0IvL/1380971716.73/lava/results/swcontext/build.txt'
Traceback (most recent call last):
File
"/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-09-23-224cd02/lava_dispatcher/job.py",
line 254, in run
action.run(**params)
File
"/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-09-23-224cd02/lava_dispatcher/actions/lava_test_shell.py",
line 566, in run
self._bundle_results(target, signal_director, testdefs_by_uuid)
File
"/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-09-23-224cd02/lava_dispatcher/actions/lava_test_shell.py",
line 716, in _bundle_results
bundle = lava_test_shell.get_bundle(results_dir, testdefs_by_uuid)
File
"/srv/lava/.cache/git-cache/exports/lava-dispatcher/2013-09-23-224cd02/lava_dispatcher/lava_test_shell.py",
line 369, in get_bundle
build = _read_content(os.path.join(results_dir, 'swcontext/build.txt'))
File "/srv/lava/.cache/git-cache/exports/lava-dispatche
