Hi,
I had a boot issue and it was because of using SPACE to stop the autoboot. A quick fix for this was to add a \" to a variable declaration such as "setenv dummy variable\"". Do you know of any other fix for this? It seems the default for lava is "Hit any key to stop autoboot" and just send a "b" to stop it. In my case, I had to change the device configuration file to look for "Press SPACE to abort autoboot in 2 seconds" and then send a " ". The device configuration looks as follows http://pastebin.ubuntu.com/18790420/.
Now I have another issue where the job keeps going even though the image booted successfully. I want it to stop once it sees "am335x-evm login:". Is there a way to do this? I changed the master_str = am335x-evm login:.
This is my complete log http://pastebin.ubuntu.com/18790288/.
Thanks,
Josue
Dear Lava team,
We're deploying Lava V2. So far we've been working on old servers to prototype our installation. We're now almost ready to order our definitive PCs.
We have assessed some key features for our Lava server. Still, we're not 100% sure on how powerful it should be.
Is it possible for you to share the main characteristics of your current Lava servers (Number of cores, RAM, size of disk)? That would be helpful.
Thanks and best regards,
Denis Humeau
Hi,
I'm currently trying to configure a Switched Rack PDU to the lava instance.
How do I know if the driver for my PDU APC AP7901 is supported in the framework?
I got it connected both via serial and telnet. My /etc/lavapdu/lavapdu.conf file is attached.
Also, when I restart the lavapdu-runner it fails with the error that is attached.
As for the beaglebone black support, I have a device dictionary but where should I save it so lava can access it? I've seen that the pdu hostname is always similar to pdu05. How do I know my pdu's hostname?
I appreciate the help, thanks.
Regards,
Josue Albarran
Hello,
I have a lava setup and right now running two single instance servers.
These are pretty high end servers are handling 4-5 Android devices over USB
I need to expand that to multi node setup with maximum DUTs connected to
one dispatcher.
The target is only to have android DUTs so that implies a very stable USB
hub and stack on the dispatcher machines.
I used a couple of off the shelf desktops in the past and the USB stack
could not handle more than 1 device at a time.
Any suggestions for hardware that is proven to be solid for dispatchers.
Thanks
Sandeep
Hello,
For the 2016.4 release I had created a custom LAVA extension to add 2
commands and 2 xmlrpc methods. The extension mechanism was very
convenient. All I had to do was install an egg on the system and restart
the lava service. When I upgraded to 2016.6 the extension did not work
due to commit b6fd045cc2b320ed34a6fefd713cd0574ed7b376 "Remove the need
for extensions".
I was not able to find a way to add my extension to INSTALLED_APPS and
register the xmlrpc methods without modifying settings/common.py and
urls.py. I looked through common.py and distro.py and could not find
support in settings.conf for extensions. I also looked for a
local_settings import which is referenced on the Internet as a common
way to extend django, but did not find it. If there is a way to extend
LAVA without modifying the LAVA python code, please let me know and I
will be happy to send in a documentation patch.
It would have been nice if functionality such as the extension
mechanism, which is part of the external interface of LAVA, had gone
through a deprecation cycle. A reworked demo app showing how the new
extension mechanism works would have also been helpful.
Thank you for your time.
--
Konrad Scherer, MTS, Linux Products Group, Wind River
---------- Forwarded message ----------
From: Steve McIntyre <steve.mcintyre(a)linaro.org>
Date: 31 May 2016 at 16:46
Subject: Re: pipeline vland help
To: Christian Ziethén <christian.ziethen(a)linaro.org>
Cc: neil.williams(a)linaro.org
On Tue, May 31, 2016 at 03:29:45PM +0200, Christian Ziethén wrote:
>Hi,
Hi Christian,
You'd be much better asking on the lava-users mailing list rather than
just directly to me, I'll be honest.
>Been struggling with setting up a vland between two arndale targets. I have
>managed to create a multinode job that uses the pipeline model:
>https://lng.validation.linaro.org/scheduler/job/9702/multinode_definition
>Have also managed to create valid yaml that seems to conform to the code in
>lava-server/lava_scheduler_app/schema.py
>https://lng.validation.linaro.org/scheduler/job/9743/multinode_definition
>This one does however not do anything after being submitted, I tried
putting
>100M in the tags for the vland, I also tried requiring that the arndale
targets
>in the multinode protocol had the 100M tag, but that didn't work.
According to
>the device dictionary for lng-arndale-01, it should have a 100M tag on
iface1.
Hmmm, OK. I can see that it's sat waiting for devices to be
assigned. Looking at the definition, you've got one group (role)
defined with 2 entries. I believe that for VLANd jobs you need to have
individual roles for each machine. Neil can confirm.
>Also have this job (v1):
>https://lng.validation.linaro.org/scheduler/job/9118/multinode_definition
>Which runs my test using iface1 (I think) but it doesn't use vland.
Right, v1 doesn't do vland.
>I am unsure how to debug this.
>
>It was my assumption that I could create a vlan with the vland protocol and
>then query which interface is on that vlan in my test-definition. That
would be
>my end goal for this exercise.
Sure, that's what we expect to have working for you.
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi,
For the last couple of days I’ve been trying to setup a device in our lab for deployment and installation of a Linux OS.
However, I’ve came across a few issues and lots of questions and hopefully I can get some answers here.
Considerations:
1. I’ve decided to give it a go with LAVA v2 and try using the pipeline model
2. I’m not testing any “boards”, so it’s hard to find a similar example
3. I am not deploying any Linaro images (not even debian based)
4. My team develops and supports a reference Linux OS, based on RHEL, so that means we have total control of our images, kickstarter scripts, etc.
5. We already have a PXE server in our network, which is where our servers (the targets in this context) get booted from by default
6. Once booted from PXE, we get a PXE menu, where we can either select an option, or press ESC and add a custom command (at this syslinux is running)
7. We have access to the serial console of every device via serial port server (telnet <ipaddr> <port>)
8. We have power control over every device via IPMI
Issues:
1. I couldn’t find the documentation for how to add devices and device types to the server (which location to add the file, which format - yaml/conf)
2. In the above described environment, I suppose we would skip the deployment phase, since the devices already boot into syslinux from PXE (is this correct?). Either way, it would be nice to be able to run ‘ipmitool chassis booted pxe’ before rebooting the system.
3. Either way (via boot or deploy), how can I make sure to detect the PXE (syslinux) menu, send the ESC key, and send the command I need to trigger the kickstart installation?
To sum-up, the Workflow I’m trying to achieve after having completed the whole setup sort of goes like this:
1. Reboot target device into PXE (the PXE itself will download and start syslinux here)
2. Wait for PXE menu (expect some sort of string)
3. Send ESC key (to get into the boot shell)
4. Send command (this will trigger our kickstarter script and the installation will take around 5 minutes). The images that are needed are fetched automatically from our sftp server.
5. Wait for boot prompt after system installation succeeds
6. Login using credentials (username, password)
7. Run whatever tests we need from here
Any help here would be much appreciated.
Thanks in advance!
--
matallui
Hello,
I just started to set up a lava server to test custom devices and I've some questions about testing custom or third party boards.
Does someone know a good documentation or tutorial for the integration of custom boards? It seems that there isn't much documented for this topic.
Is there any documentation for setting up a custom device configuration file and the commands that can be used, like client_type?
Thank you and best regards
Stefan
[cid:b073c64a8131462290b626cc30430be3]<http://www.facebook.com/WagoKontakttechnik> [cid:00cd0405ac4344fbb39caf677313ca6c] <http://www.youtube.com/WagoKontakttechnik> [cid:3139f430e8f940bb956be9ff06d8d5c2] <https://www.xing.com/companies/wagokontakttechnikgmbh&co.kg> [cid:614f801bb8f64c1d8a9dbfd711f2a29a] <http://twitter.com/WAGOKontakttech> [cid:69804606bdd6406aa66c78bf7dae6c2a] <http://www.linkedin.com/company/wago-kontakttechnik>
[cid:711e500a31984a6a959819fb46ba7f2d]
________________________________________________________________________________________
Diese E-Mail einschlie?lich ihrer Anh?nge ist vertraulich und daher allein f?r den Gebrauch durch den vorgesehenen Empf?nger bestimmt. Dritten ist das Lesen, Verteilen oder Weiterleiten dieser E-Mail sowie jedwedes Vertrauen auf deren Inhalt untersagt. Wir bitten, eine fehlgeleitete E-Mail unverz?glich vollst?ndig zu l?schen und uns eine Nachricht zukommen zu lassen.
This email may contain material that is confidential and/or privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
WAGO Kontakttechnik GmbH (nach Schweizer Recht) & Co. KG; Rechtsform: Kommanditgesellschaft; Sitz: Minden; Registergericht: Bad Oeynhausen, HRA 6218; Pers?nlich haftender Gesellschafter: WAGO Kontakttechnik Beteiligungs GmbH; Sitz: Domdidier (Schweiz); Handelsregisteramt CH-217-3533291-9; Gesch?ftsf?hrung: Dipl.-Wirtsch. Ing. (FH) Sven Michael Hohorst; Dipl. Betriebsw. Axel Christian B?rner; Dipl.-Ing. (FH) Ulrich Bohling.
Hi there,
When I run LAVA hacking session on Juno but found sometimes Juno
cannot be allocated IP properly:
- I created multinode definition for Juno:
https://validation.linaro.org/scheduler/job/845471.0: this
definition is to launch kvm so I can run testing suits on it;
https://validation.linaro.org/scheduler/job/845471.1: this
definition is to launch "deploy_linaro_image" on Juno board;
- After launched these two images, the kvm usually can work well and I
can smoothly log in it with ssh;
- But for juno board, it will have below log for ssh:
395.1 ./setup_session_oe: line 38: /etc/init.d/ssh: No such file or directory
395.2 <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=sshd-restart RESULT=fail>
395.3 sshd re-start failed
395.4 Target's Gateway: 10.0.0.1
395.5 ip: RTNETLINK answers: Network is unreachable
395.6
395.7
395.8 *********************************************************************************************
395.9 Please connect to: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@ (juno-07)
395.10 *********************************************************************************************
395.11
So finally I cannot get the info for Juno's IP and cannot log in it
with ssh. It's not everytime I can reproduce this failure, so sometimes
it's lucky so I can get a correct IP.
- As a workaroud, I found if I create two saperated definitions for
Juno and kvm independently, then Juno's IP issue can be resolved:
https://validation.linaro.org/scheduler/job/845552https://validation.linaro.org/scheduler/job/845561
So could you help give suggestions for this?
Thanks,
Leo Yan
Hi,
I have made a test setup with LAVA to run some test cases on my AM335X
based platform. I want to execute some simple test cases like testing
the status of "ifconfig eth0" command. I don't want to deploy any image
and my goal is to execute only this test directly(target is booted with
root file system mounted).I have the below job submitted to the lava
worker. ethernet.yaml contains the shell script which actually performs
the ifconfig test.
=============================================================================================
{
"actions": [
{
"command": "dummy_deploy",
"parameters": {
"target_type": "oe"
}
},
{
"command": "lava_test_shell",
"parameters": {
"testdef_repos": [
{
"testdef": "/root/lava_tests/yaml/ethernet.yaml"
}
],
"timeout": 60
}
},
{
"command": "submit_results_on_host",
"parameters": {
"server": "http://10.24.252.13:81/RPC2/",
"stream": "/anonymous/lavaserver/"
}
}
],
"device_type": "ELIN",
"health_check": false,
"job_name": "elin-ethernet-test",
"logging_level": "DEBUG",
"timeout": 60
}
=======================================================================================================
Lava dispatcher is able to connect to the target and start the job. But
finally I am getting a timeout. Please find the attached log for
details. I can see that after connecting with the target the dispatcher
is checking/finding some information related to the file system, and
looks like it is getting timed out there. How can I avoid this and make
the dispatcher to directly perform the test on the target platform?
Any help any help would be appreciated.
Best Regards,
Pradeepkumar Soman
