Image pipeline tries to submit LAVA test on bootstrap tests
Affected images versions
- not relevant (explain why)
- see the table below (list the *architecture and build id of the tested images in the appropriate cells)
Deployment | Type | v2021 | v2022 | v2023 | v2024dev1 |
---|---|---|---|---|---|
apt | minimal/fixedfunction | X | |||
ostree | minimal/fixedfunction | x | |||
apt | target/hmi | x | |||
ostree | target/hmi | x | |||
apt | basesdk | ||||
apt | sdk | ||||
apt | nfs | ||||
apt | lxc | ||||
apt | image-builder | ||||
apt | package-source-builder |
To find the build id and the variant type you can:
- derive it from the image name
- for instance, with the
apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz
image the build id is 20211031.0425, the variant isfixedfunction
the deployment type isostree
- for instance, with the
- obtain it from
/etc/os-release
using theBUILD_ID
andVARIANT_ID
keys
Steps to reproduce
When running bootstrapping tests image pipelines tries to run LAVA tests.
https://gitlab.apertis.org/infrastructure/apertis-image-recipes/-/jobs/2213246
Expected result
For bootstraping tests there should not run LAVA tests
Actual result
LAVA tests are trigger but they not run since the image are not saved for this purpose.
Reproducibility
How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?
Put the
-
✅ always - often, but not always
- rarely
Impact of bug
Jobs that don't suppose to be triggered are shown causing confusion. Also tests that will fail are sent to LAVA.
Root cause
Image recipe does not handle correctly the variables that govern the LAVA test submission.
Outcomes
Management data
This section is for management only, it should be the last one in the description.
/cc @andrunko @em @sagar @sudarshan @wlozano
Phabricator link: https://phabricator.apertis.org/T9694