Hello,
I tried upgrading from lava-server 2023.03 to 2023.06 on Debian 11 and got the following error:
Setting up lava-server (2023.06+11+bullseye) ...
/var/run/postgresql:5432 - accepting connections Updating configuration:
* generate SECRET_KEY [SKIP]
* generate DATABASES [SKIP]
Run fixups:
* fix permissions:
- /var/lib/lava-server/home/
- /var/lib/lava-server/default/
- /var/lib/lava-server/default/media/
- /var/lib/lava-server/default/media/job-output/
- /etc/lava-server/dispatcher-config/
- /etc/lava-server/dispatcher.d/
- /var/lib/lava-server/default/media/job-output/2017/
- /etc/lava-server/dispatcher-config/devices/
- /etc/lava-server/dispatcher-config/devices/*
- /etc/lava-server/dispatcher-config/device-types/
- /etc/lava-server/dispatcher-config/device-types/*
- /etc/lava-server/dispatcher-config/health-checks/
- /etc/lava-server/dispatcher-config/health-checks/*
* drop duplicated templates:
* fix permissions:
- /etc/lava-server/settings.conf
- /etc/lava-server/instance.conf
- /var/log/lava-server/
- /var/log/lava-server/*
- /etc/lava-server/secret_key.conf
Create database:
psql -q
NOTICE: not creating role lavaserver -- it already exists
NOTICE: not creating role devel -- it already exists lava-server manage migrate --noinput --fake-initial Operations to perform:
Apply all migrations: admin, auth, authtoken, contenttypes, lava_results_app, lava_scheduler_app, linaro_django_xmlrpc, sessions, sites Running migrations:
Applying lava_results_app.0019_auto_20230307_1545...Traceback (most recent call last):
File "/usr/bin/lava-server", line 55, in <module>
main()
File "/usr/bin/lava-server", line 51, in main
execute_from_command_line([sys.argv[0]] + options.command)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", line 232, in handle
post_migrate_state = executor.migrate(
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 245, in apply_migration
state = migration.apply(state, schema_editor)
File "/usr/lib/python3/dist-packages/django/db/migrations/migration.py", line 114, in apply
operation.state_forwards(self.app_label, project_state)
File "/usr/lib/python3/dist-packages/django/db/migrations/operations/models.py", line 256, in state_forwards
state.remove_model(app_label, self.name_lower)
File "/usr/lib/python3/dist-packages/django/db/migrations/state.py", line 100, in remove_model
del self.models[app_label, model_name]
KeyError: ('lava_results_app', 'actiondata') migration
dpkg: error processing package lava-server (--configure):
installed lava-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing:
lava-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
Does anybody know what I can do in this case?
Uninstalling lava-server and installing it again does not resolve the issue.
Kind regards,
Tim
--
Tim Jaacks
SOFTWARE DEVELOPER
SECO Northern Europe GmbH
Schlachthofstrasse 20
21079 Hamburg
Germany
T: +49 40 791899-183
E: tim.jaacks(a)seco.com
Register: Amtsgericht Hamburg, HRB 148893 Represented by: Dirk Finstel, Marc-Michael Braun, Massimo Mauri
Hi,
is it possible to show "Total count of test cases listed in Test
Definition" to the Results GUI page.
Right now it shows only executed test cases (either PASS/FAIL) but does not
show to be executed (yet to be executed) cases count.
Regards,
Koti
Hello,
I am trying to understand how the result levels are constructed for example when I run "lavacli results <job-id>"
I get an output looking like so :
Results:
* lava.git-repo-action [pass]
* lava.test-overlay [pass]
* lava.test-install-overlay [pass]
* lava.test-runscript-overlay [pass]
* lava.my_test_case_1 [pass]
* lava.my_test_case_2[pass]
what I want to do is to have a test categories, for example
* lava.category1.my_test_case_1[pass]
* lava.category3.my_test_case_3[pass]
and so on. I tried adding tags and namespaces but the results are not impacted,
Can someone please guide me through this or mention part of the documentation that might be helpful ?
Thanks in advance.
Hi Team,
Is there any provision that LAVA provides for passing the uuid for qemu platforms ? Because I am getting an error while mounting the rootfs like "Can't find the root device with the matching UUID!". Does LAVA provide any provision to pass the uuid along with the "image_arg" for qemu ? Or is it something I am missing in the job definition file ?
- deploy:
timeout:
minutes: 5
to: tmpfs
images:
kernel:
image_arg: -kernel {kernel} -append "console=ttyS0,115200 root=/dev/sda vga=0x305
rw"
url: <URL_to_vmlinuz>/vmlinuz
type: zimage
ramdisk:
image_arg: -initrd {ramdisk}
url: <URL_to_initrd>/initrd.img
compression: gz
rootfs:
image_arg: -drive file={rootfs},format=raw "
url: <URL_to_rootfs>/rootfs-qemu-amd64.squashfs
os: debian
root_partition: 1
[cid:image002.png@01D99A39.9F6574A0]
Regards ,
Sarath P T
Hi Team,
Is there any implementation in LAVA for reboot mechanism of USB booted devices ? basically x86 architecture. I found there are options in sd card booted devices using "uuu" , but is there a similar way approach for USB booted devices ?
Ideally LAVA does not have a provision to identify the "login prompt" without any "boot" method.
Regards,
Sarath P T
Hello Team,
Good Day to you!
I have a requirement to pass "enter" key after u-boot process completion,
to enter into the system.
Without pressing any key cannot enter into prompt and it stays stagnant.
Please let me know how to pass "enter" press key at the end of u-boot log.
Thanks
Pavan kumar
Hi, team,
I remember I once saw a video about how to use docker in lava to test zephyr, by kumar gala or someone else I'm not sure? But I forget the detail, can you kindly share something about that? Sample job, video or how others test zephyr with lava are highly appreciated, thanks in advance.
Hello,
I have 2 versions of a device which are identical in terms of the deploy and boot and DUT control command,
but they need different images to boot, I differentiate between them with tags,
how can I have the same health-check job running on both of them, but use different images ?
or shall I create 2 device-types for them ? ( doesn't sound like a clean solution )
Thanks
Vote +1, we have same requirements. Either LAVA could support different health check for different chip versions, or take one step back, just can disable health check on old version device, enable health on newest version only. Currently to avoid too many variants, we disable all healthy check for chipV1, chipV2, chipV3 etc.
------------------------------------------------------------------
Sender:lava-users-request <lava-users-request(a)lists.lavasoftware.org>
Sent At:2023 May 13 (Sat.) 08:00
Recipient:lava-users <lava-users(a)lists.lavasoftware.org>
Subject:Lava-users Digest, Vol 56, Issue 4
Send Lava-users mailing list submissions to
lava-users(a)lists.lavasoftware.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
lava-users-request(a)lists.lavasoftware.org
You can reach the person managing the list at
lava-users-owner(a)lists.lavasoftware.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-users digest..."
Today's Topics:
1. Design decision help reagrding device-types and health-check
(gemad(a)outlook.com)
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 May 2023 14:31:22 -0000
From: gemad(a)outlook.com
Subject: [Lava-users] Design decision help reagrding device-types and
health-check
To: lava-users(a)lists.lavasoftware.org
Message-ID:
<168390188210.1209.11677411661920883493(a)op-lists.linaro.org>
Content-Type: text/plain; charset="utf-8"
Hello,
I have 2 versions of a device which are identical in terms of the deploy and boot and DUT control command,
but they need different images to boot, I differentiate between them with tags,
how can I have the same health-check job running on both of them, but use different images ?
or shall I create 2 device-types for them ? ( doesn't sound like a clean solution )
Thanks
------------------------------
Subject: Digest Footer
_______________________________________________
Lava-users mailing list -- lava-users(a)lists.lavasoftware.org
To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
------------------------------
End of Lava-users Digest, Vol 56, Issue 4
*****************************************
Hello,
I am using the deploy action to:download to download a file from http server and decompress it,
I want to pass the path of which the file is decompressed to a user defined function in the device.jinja2,
Is there a way to do do so ? I this variable exposed somehow to the environment ?
Thanks
