Skip to content

Synchronise 2026.1 with upstream#559

Open
github-actions[bot] wants to merge 2 commits into
stackhpc/2026.1from
upstream/2026.1-2026-06-22
Open

Synchronise 2026.1 with upstream#559
github-actions[bot] wants to merge 2 commits into
stackhpc/2026.1from
upstream/2026.1-2026-06-22

Conversation

@github-actions

Copy link
Copy Markdown

This PR contains a snapshot of 2026.1 from upstream stable/2026.1.

mikalstill and others added 2 commits June 15, 2026 23:02
Due to implementation choices in qemu and libvirt, standard log
rotate does not work on these console files, and instead the usual
approach is to have libvirt's virtlogd rotate the contents of the
console log file when it gets a bit big. OpenStack Compute knows
how to read data from more than one rotated console log file if
required to service a REST API request.

OpenStack Kolla and Kolla-Ansible deploy OpenStack components in
docker or podman containers. An error in the startup configuration
for the nova_libvirt container results in the libvirt virtlogd
daemon not being run, which results in this console log rotation
not occurring.

This opens up the risk of a disk usage denial of service attack
on a hypervisor. The console log is stored on the same filesystem
as ephemeral disks, and OpenStack Nova will take a hypervisor out
of service if disk space becomes constrained. There is some
protection from the instance console not being able to write data
particularly quickly, but it is definitely still possible to fill
the hypervisor file system -- especially if multiple instances are used.

This misconfiguration appears to exist in all versions of
Kolla / Kolla-Ansible as best as I can tell.

Partial-Bug: 2155214

Change-Id: Ib62191e3022e5bcff781c12f662c9800fb210eb9
Signed-off-by: Michael Still <mikal@stillhq.com>
(cherry picked from commit 97d1352)
OpenDev does not have enough aarch64 node capacity at this point and the
backlog has grown to several days, which is also blocking non-arm64
periodic jobs. This means new Kolla images are not published to Quay.io.

Switch arm64 publish jobs to periodic-weekly so they stop blocking other
publish jobs.

Change-Id: Iffa7e2908c1beb083a9535e7328dcab687248c06
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
(cherry picked from commit c2a33b1)
@github-actions github-actions Bot requested a review from a team as a code owner June 22, 2026 08:26
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants