AUM out of space tests fail on UP Squared 6000 board
Affected images versions
- not relevant (explain why)
- see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)
Type | Arch | v2021 | v2022 | v2023pre |
---|---|---|---|---|
minimal/fixedfunction | amd64 | x | x | x |
minimal/fixedfunction | armhf | |||
minimal/fixedfunction | arm64 | |||
target/hmi | amd64 | |||
target/hmi | armhf | |||
target/hmi | arm64 | |||
basesdk | amd64 | |||
sdk | amd64 | |||
nfs | amd64 | |||
nfs | armhf | |||
nfs | arm64 | |||
lxc | amd64 | |||
lxc | armhf | |||
lxc | arm64 | |||
image-builder | ||||
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
Unaffected images versions
- all versions up to XXX (replace XXX with the build id of the most recent Apertis images where this bug cannot be reproduced)
- not relevant (explain why)
- v2020 (explain why)
- v2021 (explain why)
- v2022 (explain why)
Testcase
See
Steps to reproduce
Expected result
Test should pass
Actual result
Sporadically the tests fails
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
How severe is the bug? Does it render an image unbootable? Is it a security issue? Does it prevent specific applications from working? What is the impact? Does this bug affect a critical component? Does it cause something else to not work? How often is the bug likely to be found by a user? For example, every boot or once per year?
Attachments
Add further information about the environment in the form of attachments here. Attach plain text files from log output (from
journalctl
,systemctl
, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.
Screenshots and videos are usually useful for graphic issues.
Root cause
describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not
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/T9342