Skip to content

Weekly images are not linked properly

Background

Weekly images are promoted from daily by creating a link. The script picks the most recent image as the one to be promoted. Unfortunately, this is not always true.

Daily image are triggered but orchestrator, which will trigger pipelines for all the repos involved. However, after merging a MR, a new pipeline on the main branch is created, generating a new daily image, but only for the repo with the MR. Under this situation, a new daily is detected by the script, but it is incomplete, as it only includes one repo.

As example: https://images.apertis.org/weekly/v2024dev3/20230823.0116/

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

Management data

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

/cc @andrunko @em @Balasubramanian @sudarshan @wlozano

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

Edited by Dylan Aïssi