#1579 put the pacman cache cleanup into os-update, which site.yml does not run. site.yml therefore still failed on edge-1 with no space left on device when pulling the Alloy image (root 6.6 GB, 197 MB free, 1.7 GB in /var/cache/pacman/pkg).
New role pacman-cache:
installs the hook /etc/pacman.d/hooks/pacman-cache.hook, which empties the package cache after every install, upgrade or remove;
empties the cache on each run.
install-edge-host.yml runs the role after common and before docker-install, so the space is free before the image pull.
os-update is back to its state before #1579. common is unchanged.
#1579 put the pacman cache cleanup into `os-update`, which `site.yml` does not run. `site.yml` therefore still failed on edge-1 with `no space left on device` when pulling the Alloy image (root 6.6 GB, 197 MB free, 1.7 GB in `/var/cache/pacman/pkg`).
- New role `pacman-cache`:
- installs the hook `/etc/pacman.d/hooks/pacman-cache.hook`, which empties the package cache after every install, upgrade or remove;
- empties the cache on each run.
- `install-edge-host.yml` runs the role after `common` and before `docker-install`, so the space is free before the image pull.
- `os-update` is back to its state before #1579. `common` is unchanged.
Refs YouTrack S28-16.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The cache cleanup from #1579 sat in os-update, which site.yml does not
run, so site.yml still failed on edge-1 with "no space left on device"
when pulling the Alloy image. The hook and the cleanup move to common,
which site.yml runs on every host before install-edge-host.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot
changed title from fix(common): empty the pacman package cache in the base play to fix(pacman-cache): empty the pacman package cache before the edge image pulls2026-11-06 12:45:31 +00:00
The pacman cache policy is its own concern, not base configuration of
every host. The new role pacman-cache runs in install-edge-host after
common and before docker-install; common is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
#1579 put the pacman cache cleanup into
os-update, whichsite.ymldoes not run.site.ymltherefore still failed on edge-1 withno space left on devicewhen pulling the Alloy image (root 6.6 GB, 197 MB free, 1.7 GB in/var/cache/pacman/pkg).pacman-cache:/etc/pacman.d/hooks/pacman-cache.hook, which empties the package cache after every install, upgrade or remove;install-edge-host.ymlruns the role aftercommonand beforedocker-install, so the space is free before the image pull.os-updateis back to its state before #1579.commonis unchanged.Refs YouTrack S28-16.
🤖 Generated with Claude Code
fix(common): empty the pacman package cache in the base playto fix(pacman-cache): empty the pacman package cache before the edge image pulls