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
  • #325
Closed
Open
Issue created May 25, 2023 by ABHINISH KUMAR@zbu1korDeveloper

Not Tested status for manual testcases should be changed to N/A, for Fixed function ARM64 (rpi64) images

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 20230517.0219
ostree minimal/fixedfunction 20230517.0219
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_v2022-fixedfunction-arm64-rpi64_v2022.5rc1.img.gz image the build id is 20230517.0219, the variant is fixedfunction the deployment type is apt and ostree
  • obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

  • N/A
  • not relevant (explain why)
  • v2021 (explain why)
  • v2022 (explain why)

Testcase

https://qa.apertis.org/testcases/v2022/fixedfunction-webserver.html https://qa.apertis.org/testcases/v2022/image-bootable.html https://qa.apertis.org/testcases/v2022/licensing-summary-availability.html https://qa.apertis.org/testcases/v2022/sanity-check-manual.html https://qa.apertis.org/testcases/v2022/apertis-update-manager-ota-api-switch-network.html https://qa.apertis.org/testcases/v2022/apertis-update-manager-ota-check-network-failure.html https://qa.apertis.org/testcases/v2022/apertis-update-manager-ota-rollback.html https://qa.apertis.org/testcases/v2022/apertis-update-manager-rollback.html https://qa.apertis.org/testcases/v2022/apertis-update-manager-usb-unplug.html

Steps to reproduce

N/A

Expected result

Above mentioned test cases status should be changed from Not Tested to N/A.

Actual result

N/A

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

Impact of bug

high

Attachments

https://qa.apertis.org/report/v2022/20230517.0219/apt

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

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

Edited May 25, 2023 by Apertis CI robot
Assignee
Assign to
Time tracking
Apertis Website Terms of Use Privacy Policy