Dear LAVA-Team,
I'm writing you again, because we are still struggling to get our LAVA infrastructure running. Since the last time we have switched from the more advanced Board to a set of three Raspberry Pis, which we want to test with different Operating Systems to gain more experience in using LAVA.
For the configuration of our Raspberry Pi, running Rasbian, we can't quite get past the login and reboot phase. It is connected via serial and integrated with Ser2Net, the device dictionary looks like this now:
{% extends 'bcm2711-rpi-4-b.jinja2' %} {% set soft_reboot_command = 'sudo reboot' %} {% set auto_login_prompt = "raspberrypi login:" %} {% set auto_login_username = "pi" %} {% set ssh_host = '192.168.1.11' %} {% set connection_list = ['uart0'] %} {% set connection_commands = {'uart0': 'telnet <HOST IP> 7102'} %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %}
In the health check we just want to pull some standard images and deploy them with tftp, then login and run smoke tests by Linaro. The current health job looks like this:
device_type: bcm2711-rpi-4-b
job_name: RPI-01 (Raspbian) Health Check timeouts: job: minutes: 10 connection: minutes: 2 action: minutes: 10 priority: medium visibility: public
actions: - deploy: timeout: minutes: 10 to: tftp kernel: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/... type: image ramdisk: url: https://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05/arm64/base/... compression: gz modules: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/... compression: xz dtb: url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/... os: oe - boot: timeout: minutes: 2 method: u-boot commands: ramdisk prompts: - 'pi@raspberrypi:~$' auto_login: login_prompt: 'raspberrypi login:' username: pi password_prompt: 'Password:' password: 1234567890 login_commands: - sudo su - test: definitions: - {from: git, name: smoke-tests, path: lava-test-shell/smoke-tests-basic.yaml, repository: 'http://git.linaro.org/lava-team/lava-functional-tests.git%27%7D timeout: {minutes: 5}
But with this we are having issues when the DUT is supposed to reboot because we get stuck at the login prompt. First problem is probably the auto_login, we have defined username and password, but for the password definition we get this problem:
[cid:image001.png@01D711E1.6A14C9A0]
Can you explain, what we are doing wrong?
Then LAVA is sending the reboot commands but those always seem to fail at the login. The Error looks somewhat like this:
[cid:image002.png@01D711E1.6A14C9A0]
Does this have to do with the deployment through tftp or is it the autologin? Also the login and password prompts won't get recognized and are not filled in.
Can you tell us, what we are doing wrong?
Regards Marcel
_____________________________________________________________________________________
Expleo Germany GmbH Sitz der Gesellschaft | Corporate Headquarters: M?nchen Handelsregister | Commercial Register: Amtsgericht M?nchen HRB 83252 Gesch?ftsf?hrung | Management: Ralph Gillessen, Marcus Ganguin
This message contains information that may be privileged or confidential. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. _________________________________________________________
EMAIL LEGAL MENTION / DISCLAIMER
This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.
Hello,
Le ven. 5 mars 2021 à 17:06, Marcel Trattner < marcel.trattner@expleogroup.com> a écrit :
Dear LAVA-Team,
I’m writing you again, because we are still struggling to get our LAVA infrastructure running. Since the last time we have switched from the more advanced Board to a set of three Raspberry Pis, which we want to test with different Operating Systems to gain more experience in using LAVA.
For the configuration of our Raspberry Pi, running Rasbian, we can’t quite get past the login and reboot phase. It is connected via serial and integrated with Ser2Net, the device dictionary looks like this now:
{% extends 'bcm2711-rpi-4-b.jinja2' %}
{% set soft_reboot_command = 'sudo reboot' %}
{% set auto_login_prompt = "raspberrypi login:" %}
{% set auto_login_username = "pi" %}
{% set ssh_host = '192.168.1.11' %}
{% set connection_list = ['uart0'] %}
{% set connection_commands = {'uart0': 'telnet <HOST IP> 7102'} %}
{% set connection_tags = {'uart0': ['primary', 'telnet']} %}
You don't have any PDU to power on/off your board? And add something like this to the device dictionary: https://validation.linaro.org/scheduler/device/beaglebone-black03/devicedict...
In the health check we just want to pull some standard images and deploy them with tftp, then login and run smoke tests by Linaro. The current health job looks like this:
device_type: bcm2711-rpi-4-b
job_name: RPI-01 (Raspbian) Health Check
timeouts:
job:
minutes: 10
connection:
minutes: 2
action:
minutes: 10
priority: medium
visibility: public
actions:
deploy:
timeout:
minutes: 10
to: tftp
kernel:
url:
https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/...
type: image ramdisk: url:
https://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05/arm64/base/...
compression: gz modules: url:
https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/...
compression: xz dtb: url:
https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/...
os: oe
boot:
timeout:
minutes: 2
method: u-boot
commands: ramdisk
prompts:
- 'pi@raspberrypi:~$'
auto_login:
login_prompt: 'raspberrypi login:' username: pi password_prompt: 'Password:' password: 1234567890 login_commands: - sudo su
test:
definitions:
- {from: git, name: smoke-tests, path:
lava-test-shell/smoke-tests-basic.yaml,
repository: '
http://git.linaro.org/lava-team/lava-functional-tests.git%27%7D
timeout: {minutes: 5}
But with this we are having issues when the DUT is supposed to reboot because we get stuck at the login prompt. First problem is probably the auto_login, we
have defined username and password, but for the password definition we get this problem:
Can you explain, what we are doing wrong?
In YAML; "password: 12345" will be interpreted as {"password": 12345} (an integer), while lava is expecting a string.
You should use: password: "12345"
Then LAVA is sending the reboot commands but those always seem to fail at the login. The Error looks somewhat like this:
Does this have to do with the deployment through tftp or is it the autologin? Also the login and password prompts won’t get recognized
and are not filled in.
That's because you don't have any DUT controlling the board power.
Rgds
Hi Marcel,
On Fri, 5 Mar 2021 at 17:06, Marcel Trattner < marcel.trattner@expleogroup.com> wrote:
Dear LAVA-Team,
I’m writing you again, because we are still struggling to get our LAVA infrastructure running. Since the last time we have switched from the more advanced Board to a set of three Raspberry Pis, which we want to test with different Operating Systems to gain more experience in using LAVA.
For the configuration of our Raspberry Pi, running Rasbian, we can’t quite get past the login and reboot phase. It is connected via serial and integrated with Ser2Net, the device dictionary looks like this now:
Have you first tried to access the device manually from the worker using telnet? just to be sure the 'connection' is working and to check if you get a prompt.
Regards, Loic
lava-users@lists.lavasoftware.org