What does the dispatcher use LAVA_SERVER_IP for in a standalone setup

Asked by Mustafa Faraj on 2012-02-23

I am trying to run job in a standalone environment through lava-dispatch using the following command:

(one)gumstix@hwlab:/srv/lava/instances/one/bin$ sudo ./lava-dispatch /srv/lava/instances/one/job/overo-job.json --config-dir=/srv/lava/instances/one/lib/python2.7/site-packages/lava_dispatcher/default-config/lava-dispatcher/devices/overo.conf

and that is currently getting stuck in the deploy_linaro_image phase of the job. It gets stuck in pinging the LAVA_SERVER_IP specified in the lava-dispatcher.conf file. I am not sure why it is trying to contact the server, especially since I am running this in a standalone setup. Is there something I am missing, or is there a workaround to this issue?

Thanks.

Last login: Thu Feb 23 17:59:02 UTC 2012 on tty1
Welcome to Linaro 11.09 (GNU/Linux 3.0.0-1006-linaro-omap armv7l)

 * Documentation: https://wiki.linaro.org/
root@master:~# export PS1="$PS1 [rc=$(echo \$?)]: "
export PS1="$PS1 [rc=$(echo \$?)]: "
root@master:~# <LAVA_DISPATCHER>2012-02-23 10:56:09 AM INFO: System is in master image now

[rc=0]:
root@master:~# [<LAVA_DISPATCHER>2012-02-23 10:56:11 AM INFO: Format testboot and testrootfs partitions
rc=0]: umount /dev/disk/by-label/testrootfs
umount /dev/disk/by-label/testrootfs
umount: /dev/disk/by-label/testrootfs: not mounted
root@master:~# [rc=1]: mkfs -t ext3 -q /dev/disk/by-label/testrootfs -L testrootfs
tfss -t ext3 -q /dev/disk/by-label/testrootfs -L testroo
root@master:~# [rc=0]: umount /dev/disk/by-label/testboot
umount /dev/disk/by-label/testboot
umount: /dev/disk/by-label/testboot: not mounted
root@master:~# [rc=1]: mkfs.vfat /dev/disk/by-label/testboot -n testboot
mkfs.vfat /dev/disk/by-label/testboot -n testboot
mkfs.vfat 3.0.9 (31 Jan 2010)
root@master:~# [rc=0]: <LAVA_DISPATCHER>2012-02-23 10:57:12 AM INFO: Waiting for network to come up
LC_ALL=C ping -W4 -c1 192.168.1.11
LC_ALL=C ping -W4 -c1 192.168.1.11
PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.

--- 192.168.1.11 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

root@master:~# [rc=1]: LC_ALL=C ping -W4 -c1 192.168.1.11
LC_ALL=C ping -W4 -c1 192.168.1.11
PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.

--- 192.168.1.11 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Question information

Language:
English Edit question
Status:
Answered
For:
LAVA Dispatcher Edit question
Assignee:
No assignee Edit question
Last query:
2012-02-23
Last reply:
2012-02-23
Paul Larson (pwlars) said : #1

The way deployment currently works, the image you are trying to deploy is downloaded onto the server, it runs linaro-media-create (or not if you give it the whole image) then extracts the root and boot images as tarballs. Those are then downloaded from the device you are trying to test. So your device needs to know the server, and base url to download those things from, which are specified in the lava-dispatcher.conf file under your instance etc. directory.

Can you help with this problem?

Provide an answer of your own, or ask Mustafa Faraj for more information if necessary.

To post a message you must log in.