Skip to content

Synchronise master with upstream#569

Merged
Alex-Welsh merged 16 commits into
stackhpc/masterfrom
upstream/master-2026-07-13
Jul 13, 2026
Merged

Synchronise master with upstream#569
Alex-Welsh merged 16 commits into
stackhpc/masterfrom
upstream/master-2026-07-13

Conversation

@github-actions

Copy link
Copy Markdown

This PR contains a snapshot of master from upstream master.

mnasiadka and others added 16 commits June 24, 2026 13:00
The reset_userinfo tar filter used when creating plugins and
additions archives normalized uid/gid but left mtime untouched.

Since archives are created after set_time() has already run, and
the default working directory is a fresh temp dir per invocation,
the embedded directory mtime was always the current time.

Docker computes a content checksum for ADD instructions, so a
different mtime in the tar produced a different checksum on every
run.

Fix by setting tarinfo.mtime = 0 in both reset_userinfo filters and
calling os.utime(arc_path, (0, 0)) on the archive file after
creation, making the archives binary-identical across runs for the
same content.

Change-Id: I205dab2c4a74fb9e3cb15c421d5c025849f5632a
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
From the experience we have made so far, a lot of AI based contributions
tend to cause more work rather than they bring benefit. So we caution
people to avoid this when possible.

The wording of the policy was adapted from the Zuul project [0].

[0] https://review.opendev.org/c/zuul/zuul/+/993998

Co-Authored-By: James E. Blair <jim@acmegating.com>
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I5fcd5bea33c4f4c87b6f6cf0a96514e8d2da3af3
RHEL9 dropped SPICE support from qemu-kvm, and Rocky Linux followed
suit. Up until now the documented guidance has been to use the Debian
or Ubuntu container images if you want to serve the ``spice-direct``
console type, because the stock Rocky nova-libvirt image will simply
fail to start any SPICE-enabled instance.

This change adds a second version of the nova-libvirt container image
called nova-libvirt-spice. It is always built, but is identical for
all supported container base distributions except for Rocky Linux.
In the Rocky Linux case, this container adds the community
maintained ligenix/enterprise-qemu-spice COPR repository that provides
a rebuild of ``qemu-kvm`` with SPICE support re-enabled for both
EPEL 9 and EPEL 10.

Which nova-libvirt container should be used in a given deployment is
delegated to logic in kolla-ansible, based on the deployer's settings
in globals.yml.

The COPR is a third-party rebuild with no vendor support contract.
The release note and support matrix are updated to describe the
opt-in path and call this caveat out explicitly. The earlier
"you must use Debian or Ubuntu" wording in the support matrix is
softened here, rather than by retroactively editing the kerbside
container-build patch that introduced it, so that this feature can
land (or not land) independently of the earlier change.

Partial-Bug: #2131793 (spice-direct consoles)

Prompt: I am interested in seeing how we would go about using
https://copr.fedorainfracloud.org/coprs/ligenix/enterprise-qemu-spice/
to add SPICE support back to the Kolla build Rocky Linux containers
as a new patch in the kolla/ORDER list. Could you please investigate
options here?

Assisted-By: Claude Code
Co-Authored-By: Claude Opus 4.7 (1M context, medium effort) <noreply@anthropic.com>

Change-Id: I410b87b7f8cdd541c48d9a749b3fea634a5f4e6c
Signed-off-by: Michael Still <mikal@stillhq.com>
The nova-libvirt-spice image is a kerbside fork of the upstream
nova-libvirt image, and is what kolla-ansible deploys for the
nova_libvirt container when kerbside is enabled. Mirror the virtlogd
changes made to the upstream image: install libvirt-daemon-log where
it is a separate package, and add the start script which runs
virtlogd as a sidecar of libvirtd so that nova instance console logs
are rotated.

Change-Id: Ifdcd3ae34e62fc484d1a25ef6f6c68c467745fda
Depends-On: https://review.opendev.org/c/openstack/kolla/+/993065
Signed-off-by: Michael Still <mikal@stillhq.com>
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.

Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.

Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
BaseOS and AppStream for CentOS/Rocky
ubuntu, ubuntu-security for Ubuntu
debian, debian-security for Debian

ubuntu-cloud-archive is not really a base repo - so
removing it from ubuntu.sources

Change-Id: Iab98de963f2e8532389b7563bb572d8aa20c7aa6
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Ic088f5a85f3c033b0c5024d0b2e1bc889c52648d
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
We don't use npm anywhere

Change-Id: Ibc1b213d575775f79fd5b7b6b8c6e21685fdb0b0
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Change-Id: Icb27b676ae686fe57f894e8da103da8641ed8eb2
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
@github-actions github-actions Bot requested a review from a team as a code owner July 13, 2026 07:22
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Jul 13, 2026
@Alex-Welsh Alex-Welsh merged commit 7cb12fd into stackhpc/master Jul 13, 2026
3 checks passed
@Alex-Welsh Alex-Welsh deleted the upstream/master-2026-07-13 branch July 13, 2026 09:35
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.

4 participants