microsoft / microsoft/azure-linux-dev-tools

Image Customizer scenario tests failing

Open
#71 0 comments 0 reactions 1 assignee View on GitHub

@reubeno is already working on this.

Since Sep 1, 2026.

bug
Dominant language
Go
Stars
18
Forks
27
Avg merge
4d 33m
Merged PRs (30d)
24

Description

Example: https://github.com/microsoft/azure-linux-dev-tools/actions/runs/24060810107/job/70176515882?pr=70

Excerpt from log:

```
ℹ️ mageScenarioCommon: DEBU[0006][main] Executing: [tdnf -v check-update --refresh --assumeyes --setopt=reposdir=/_localrpms]
ℹ️ mageScenarioCommon: DEBU[0006][main] azurelinux-official-base 100% 1574
ℹ️ mageScenarioCommon: DEBU[0017][main] Exiting Chroot: '/build/work/imageroot'
ℹ️ mageScenarioCommon: INFO[0017][main] Installing packages: [jq]
ℹ️ mageScenarioCommon: INFO[0017][main] Installing packages (1): [jq]
ℹ️ mageScenarioCommon: DEBU[0017][main] Entering Chroot: '/build/work/imageroot'
ℹ️ mageScenarioCommon: DEBU[0017][main] Executing: [tdnf -v install --assumeyes --cacheonly --setopt=reposdir=/_localrpms jq]
ℹ️ mageScenarioCommon: DEBU[0023][main] Error(1036) : Insufficient disk space at cache directory /var/cache/tdnf (unless specified differently in config). Try freeing space first.
ℹ️ mageScenarioCommon: DEBU[0023][main] Exiting Chroot: '/build/work/imageroot'
ℹ️ mageScenarioCommon: DEBU[0023][main] Checking disk space
ℹ️ mageScenarioCommon: DEBU[0023][main] Disk space 92% (409/443 MiB) on (/)
ℹ️ mageScenarioCommon: DEBU[0023][main] Disk space 39% (3/8 MiB) on (/boot/efi)
ℹ️ mageScenarioCommon: DEBU[0023][main] Disk space 43% (62/144 GiB) on (host:/build/work)
ℹ️ mageScenarioCommon: DEBU[0023][main] Executing: [lsof -v]
ℹ️ mageScenarioCommon: DEBU[0023][main] Executing: [lsof -Q -F pcn -- /build/work/imageroot]
ℹ️ mageScenarioCommon: DEBU[0023][main] Unmounting (/build/work/imageroot/boot/efi)
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.