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#defline3

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/Image

      type: image

    ramdisk:

      url: https://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05/arm64/base/rootfs.cpio.gz

      compression: gz

    modules:

      url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/modules.tar.xz

      compression: xz

    dtb:

      url: https://storage.kernelci.org/mainline/master/v5.11/arm64/defconfig/clang-10/dtbs/broadcom/bcm2711-rpi-4-b.dtb

    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'}

    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

Rémi Duraffort

LAVA Architect

Linaro