Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A apertis-issues
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

🔴 v2022.5 entered Hard Code Freeze, changes will not be accepted • schedule

🔴 v2023.1 entered Hard Code Freeze, changes will not be accepted • schedule

🟠 v2024dev2 entered Soft Code Freeze/Hard Feature Freeze, only bug fixes will be accepted • schedule

  • infrastructure
  • apertis-issues
  • Issues
  • #314
Closed
Open
Issue created Apr 26, 2023 by Walter Lozano@wlozanoMaintainer

QA Report App: Invalid links to images on Test Report pages

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
ostree minimal/fixedfunction
apt target/hmi
ostree target/hmi
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 is fixedfunction the deployment type is ostree
  • obtain it from /etc/os-release using the BUILD_ID and VARIANT_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)
  • v2021 (explain why)
  • v2022 (explain why)

Testcase

The link to the testcase on https://qa.apertis.org/ if the bug was found during a testing round

Steps to reproduce

Ordered list detailing every step so other developers can reproduce the issue. Include hardware which you used.

  • ...

Expected result

Explain (at least briefly) what result you expected.

Actual result

Explain the actual result observed after the execution steps. Paste any error output here between code block back-quotes. For long text contents (over 1000 lines) it is better to attach a file by using the button in the right corner. If adding comments on the log is required create a new snippet and add the link to it here.

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

  1. always
  2. ✅ often, but not always
  3. 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

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Affected component

Actual QA Report app on https://qa.apertis.org/

Testcase

Manual Test /steps to reproduce see below

Steps to reproduce

  • Open https://qa.apertis.org/
  • Click for example on the apt (a) link of Releases v2023.0-1 to open https://qa.apertis.org/report/v2023/20230322.1745/apt
  • Click on any of the Links behind "Images:" (for example [[ https://images.apertis.org/daily/v2023/20230322.1745/amd64/basesdk/apertis_v2023-basesdk-amd64-sdk_20230322.1745.img.gz| BaseSDK AMD64 ]])

Expected result

  • Image is downloaded from the image server

Actual result

  • Links are invalid and the image server returns 404 Not Found error

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

  1. ✅ always
  2. often, but not always
  3. rarely

Impact of bug

  • Not possible to directly download images from the Test Report page
  • Bad user experience when links are not working

Attachments

Root cause

Outcomes

Management data

This section is for management only, it should be the last one in the description

apertis:lava:suite: traprain

Phabricator link: https://phabricator.apertis.org/T9682

Assignee
Assign to
Time tracking
Apertis Website Terms of Use Privacy Policy