Public Repository

Last pushed: a year ago
Short Description
A docker container based on Debian with Linaro LAVA Test Server built into the image.
Full Description

For more information on how this was built as well as the various parameters that have been tested, see the following github repo:
https://github.com/dbharbin/DebianLAVA-Docker-base

Docker Pull Command
Owner
arizidon

Comments (7)
brucezou
a year ago

hi thanks
Below script don't call burn image script,I don't know how to burn image into device by deploy_linaro_kernel in LAVA?Or where to configurate burn image script in LAVA environment.

"actions": [
{
"command": "deploy_linaro_kernel",
"metadata": {
"arch": "ARMv7",
"build_id": "v4.7-2546-g1b3fc0b",
"config": "arm-multi_v7_defconfig",
"machine": "d01",
"release": "v4.7-2546-g1b3fc0b",
"tree": "linux"
},
"parameters": {
"dtb": "http://builds.sirena.org.uk/v4.7-2546-g1b3fc0b/arm-multi_v7_defconfig/dtbs/hip04-d01.dtb",
"kernel": "http://builds.sirena.org.uk/v4.7-2546-g1b3fc0b/arm-multi_v7_defconfig/zImage",
"nfsrootfs": "http://releases.linaro.org/15.03/openembedded/images/lamp-armv7a/linaro-image-lamp-genericarmv7a-20150323-328.rootfs.tar.gz"
}
},

arizidon
a year ago

Hi brucezou something looks hung. What host OS are you using? I am only using Ubuntu 14.04 and 16.04 atm.

where is LAVA Browser interface and see the job submit status.
if you launched from ubuntu terminal, then should be able to bring up chrome browser, enter 172.17.0.2 on the same host, and see the LAVA Browser interface. (this browser will look identical to the Linaro LAVA interface here: https://validation.linaro.org/ ). Then can click "scheduler --> status" and track the jobs running.

Test usually takes around 200-250 seconds... last few lines of successful run below:
.....
Job Running for 195 seconds
Job Running for 200 seconds
Job Running for 205 seconds
Job Running for 210 seconds
Job Completed: 215 s (25 s in queue)
root@de2384825135:/#

One hint: Although your startup looked ok to me, prior to running /submittestjob.sh, go ahead and make sure the correct processes are running by running ps -e on container command line. Should see something like this:
root@de2384825135:/# ps -e
PID TTY TIME CMD
1 ? 00:00:00 sh
32 ? 00:00:04 postgres
34 ? 00:00:00 postgres
35 ? 00:00:01 postgres
36 ? 00:00:01 postgres
37 ? 00:00:03 postgres
38 ? 00:00:10 postgres
90 ? 00:00:08 apache2
193 ? 00:00:03 lava-daemon
227 ? 00:00:03 lava-master
262 ? 00:00:03 lava-slave
307 ? 00:04:40 lava-server
308 ? 00:00:47 lava-dispatcher
309 ? 00:02:36 lava-server
333 ? 00:00:40 postgres
336 ? 00:00:29 postgres
380 ? 00:00:00 sshd
381 ? 00:00:00 bash
382 ? 00:00:14 apache2
383 ? 00:01:18 apache2
384 ? 00:01:19 apache2
475 ? 00:00:38 postgres
8397 ? 00:00:00 ps

If looks odd, can always force a restart of them all by running /start.sh from command line.

You really have to get to the LAVA web interface and click down into the running jobs, however, to get much further on diagnosing the issues. In that interface, complete logs from the QEMU targets will be getting dumped into a console that allow you to track the progress/diagnose where getting stuck.
So a) use ubuntu, b) open chrome, c) enter 172.17.0.2 for url to get to LAVA interface. If that's not working, then first step is to figure out why not.

The apache warning is no big deal.
good luck :)

brucezou
a year ago

Is it successful or fail in below message?
Job Running for 535 seconds
Job Running for 540 seconds
unknown status

where is LAVA Browser interface and see the job submit status???????
【progress of the tests can also be monitored from the LAVA Browser interface. To execute this command from the container command line, enter /submittestjob.sh.】

is it a bug?
【Starting Apache httpd web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message】

brucezou
a year ago

hi, do you know what's wrong?

bruce@bruce-virtual-machine:~/lava/DebianLAVA-Docker-Image$ sudo docker run -it -v /boot:/boot -v /lib/modules:/lib/modules -v $PWD/fileshare:/opt/fileshare -v /dev/bus/usb:/dev/bus/usb --device=/dev/ttyUSB0 -p 8000:80 -p 2022:22 -h de2384825135 --privileged=true arizidon/debian-lavaserver:testing
Starting postgresql
[ ok ] Starting PostgreSQL 9.5 database server: main.
Starting apache2
[....] Starting Apache httpd web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
. ok
Starting lava-server
[ ok ] Starting lava-server manage scheduler : lava-daemon.
Starting lava-master
[ ok ] Starting lava-server manage dispatcher-master : lava-master.
Starting lava-slave
[ ok ] Starting lava-slave : lava-slave.
Waiting for lavaserver database to be active
..............
[ ok ] LAVA server ready
[ ok ] Reloading Apache httpd web server: apache2.
root@de2384825135:/# ./submittestjob.sh
Submit basic kvm job for v1 dispatcher device
Submitting test job to LAVA server
Submit basic qemu-aarch64 job for v1 dispatcher device
Submitting test job to LAVA server
Submit and wait for v2/pipeline device to complete
Submitting test job to LAVA server
Job polling enabled
Job waiting to run for 0 seconds
Job waiting to run for 5 seconds
Job waiting to run for 10 seconds
Job Running for 0 seconds
Job Running for 5 seconds
………………………………
Job Running for 535 seconds
Job Running for 540 seconds
unknown status
root@de2384825135:/# busybox ifconfig
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:02
inet addr:172.17.0.2 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: fe80::42:acff:fe11:2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:50053 errors:0 dropped:0 overruns:0 frame:0
TX packets:36160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:107339236 (102.3 MiB) TX bytes:2571184 (2.4 MiB)

arizidon
a year ago

Or just try the docker run command with this as the image per the github repo instructions. From command line:
sudo docker run -it -v /boot:/boot -v /lib/modules:/lib/modules -v $PWD/fileshare:/opt/fileshare -v /dev/bus/usb:/dev/bus/usb --device=/dev/ttyUSB0 -p 8000:80 -p 2022:22 -h de2384825135 --privileged=true arizidon/debian-lavaserver:testing

arizidon
a year ago

Try the tag :testing and see if that helps

brucezou
a year ago

Hi, i can't get it.

bruce@bruce-virtual-machine:~/lava$ sudo docker pull arizidon/debian-lavaserver
Using default tag: latest
Pulling repository docker.io/arizidon/debian-lavaserver
Tag latest not found in repository docker.io/arizidon/debian-lavaserver