feat(stemcell): add Ubuntu Resolute (26.04) stemcell support

Introduces Ubuntu 26.04 'Resolute Raccoon' as a supported stemcell
target, adding stage configurations, package lists, spec fixtures, and
build tooling to produce and validate a Resolute stemcell image.

Rakefile now raises an error when operating_system_version is not
specified to prevent accidental builds without an explicit OS target.

Repack helper scripts and Vagrant configuration are updated to support
the Resolute OS image layout.

Warden stage masks systemd-udevd.service, which has no function in
containerised environments.

Package fixture lists are updated to reflect Resolute package names:
libxmlsec1t64 is now libxmlsec1-1, linux-firmware-amd-misc is added,
and libpython3.13 is removed (libpython3.14 is still present).

Author: mkocher

.gitignore

@@ -13,5 +13,7 @@ acceptance-tests/syslog-release
 acceptance-tests/os-conf-release
 
 ci/docker/os-image-stemcell-builder/VMware-ovftool-*.bundle
+ci/docker/VMware-ovftool-*.bundle
+ci/docker/*/VMware-ovftool-*.bundle
 
-tmp/
+tmp/

CONTRIBUTING.md

@@ -11,3 +11,4 @@ an "Ubuntu SHORT_NAME" based stemcell will be on the branch:
 As of `2026-04-03` the following stemcell lines / branches are supported:
 - Ubuntu Jammy / `ubuntu-jammy`
 - Ubuntu Noble / `ubuntu-noble`
+- Ubuntu Resolute / `ubuntu-resolute`

README.md

@@ -3,18 +3,30 @@
 This repo contains tools for creating BOSH stemcells. A stemcell is a bootable
 disk image that is used as a template by a BOSH Director to create VMs.
 
+This branch builds stemcells for **Ubuntu 26.04 LTS (Resolute)**. For other
+Ubuntu releases, switch to the appropriate branch (for example `ubuntu-noble`
+for 24.04).
+
 ## Quick Start: Building a Stemcell Locally
 
 ```bash
-export short_name="noble"
+export short_name="resolute"
 
 git clone git@github.com:cloudfoundry/bosh-linux-stemcell-builder.git
 cd bosh-linux-stemcell-builder
 git checkout ubuntu-${short_name}
 mkdir -p tmp
 docker build \
    --platform linux/amd64 \
-   --build-arg SYFT_VERSION=v1.42.3 \
+   --build-arg BASE_IMAGE="ubuntu:${short_name}" \
+   --build-arg META4_CLI_URL="https://github.com/dpb587/metalink/releases/download/v0.5.0/meta4-0.5.0-linux-amd64" \
+   --build-arg SYFT_CLI_URL="https://github.com/anchore/syft/releases/download/v1.42.3/syft_1.42.3_linux_amd64.tar.gz" \
+   --build-arg YQ_CLI_URL="https://github.com/mikefarah/yq/releases/download/v4.52.5/yq_linux_amd64" \
+   --build-arg RUBY_INSTALL_URL="https://github.com/postmodern/ruby-install/releases/download/v0.10.2/ruby-install-0.10.2.tar.gz" \
+   --build-arg RUBY_VERSION="$(cat .ruby-version)" \
+   --build-arg GEM_HOME="/usr/local/bundle" \
+   --build-arg OVF_TOOL_INSTALLER="VMware-ovftool-4.4.3-18663434-lin.x86_64.bundle" \
+   --build-arg OVF_TOOL_INSTALLER_SHA1="6c24e473be49c961cfc3bb16774b52b48e822991" \
    -t bosh/os-image-stemcell-builder:${short_name} \
    ci/docker/os-image-stemcell-builder/
 docker run \
@@ -56,7 +68,7 @@ installed in the operating system or when making changes to the configuration
 of those packages.
 
 ```bash
-export short_name="noble"
+export short_name="resolute"
 
 bundle exec rake stemcell:build_os_image[ubuntu,${short_name},${PWD}/tmp/ubuntu_base_image.tgz]
 ```
@@ -78,7 +90,7 @@ The arguments to the `stemcell:build_os_image` rake task follow:
 Rebuild the stemcell when you are making and testing BOSH-specific changes such as a new BOSH agent.
 
 ```bash
-export short_name="noble"
+export short_name="resolute"
 export build_number="0.0.8"
 
 bundle exec rake stemcell:build[vsphere,esxi,ubuntu,${short_name},${PWD}/tmp/ubuntu_base_image.tgz,${build_number}]
@@ -95,6 +107,7 @@ The arguments to `stemcell:build` are:
     - `google` → `kvm`
     - `openstack` → `kvm`
     - `vsphere` → `esxi`
+    - `warden` → `warden`
 3. `operating_system_name` (`ubuntu`): Type of OS. Same as
    `stemcell:build_os_image`.
 4. `operating_system_version` (`<short_name>`): OS release. Same as
@@ -114,7 +127,7 @@ the stemcell would be at
 upload the stemcell to a vSphere BOSH Director:
 
 ```bash
-export short_name="noble"
+export short_name="resolute"
 
 bosh upload-stemcell tmp/bosh-stemcell-0.0.8-vsphere-esxi-ubuntu-${short_name}-go_agent.tgz
 ```
@@ -135,7 +148,6 @@ the OS image** at the `tmp/ubuntu_base_image.tgz` and you're within the Docker
 container):
 
 ```shell
-  export short_name="noble"
   cd /opt/bosh/bosh-stemcell
   bundle install
   OS_IMAGE=/opt/bosh/tmp/ubuntu_base_image.tgz bundle exec rspec -fd spec/os_image/ubuntu_spec.rb
@@ -208,7 +220,7 @@ If you find yourself debugging any of the above processes, here is what you need
    Example usage:
 
    ```shell
-   export short_name="noble"
+   export short_name="resolute"
 
    bundle exec rake stemcell:build_os_image[ubuntu,${short_name},${PWD}/tmp/ubuntu_base_image.tgz] resume_from=rsyslog_config
    ```
@@ -219,8 +231,8 @@ If you find yourself debugging any of the above processes, here is what you need
   modifications you can rerun the tests (without rebuilding OS image). Details
   in section `How to run tests for OS Images`
 * If the Stemcell has been built, and you are only updating tests, you do not
-  need to re-build the stemcell. You can simply rerun the tests - without
-  rebuilding Stemcell. Details in section `How to run tests for Stemcell`
+  need to re-build the stemcell. You can simply rerun the tests (without
+  rebuilding Stemcell). Details in section `How to run tests for Stemcell`
 * It's possible to verify OS/Stemcell changes without making a deployment using
   the stemcell. For a vSphere-specific Ubuntu stemcell, the filesystem is
   available at `/mnt/stemcells/vsphere/esxi/ubuntu/work/work/chroot`
@@ -249,7 +261,7 @@ You will need the ovftool installer present in
 Rebuild the container with:
 
 ```shell
-export short_name="noble"
+export short_name="resolute"
 
 docker build \
     --platform linux/amd64 \
@@ -280,7 +292,7 @@ gsutil cp MY_OVFTOOL_FILE gs://bosh-vmware-ovftool/MY_OS/
 Example:
 
 ```shell
-export short_name="noble"
+export short_name="resolute"
 
 gsutil cp VMware-ovftool-4.4.3-18663434-lin.x86_64.bundle gs://bosh-vmware-ovftool/${short_name}/
 ```
@@ -387,4 +399,3 @@ When switching from the old pipeline to the new one, don't forget to:
   whatever the public bucket should be
 * update the tasks YAML to point to tasks in the `os-images` directory
 * rename this directory from `new`
-

Rakefile

@@ -11,12 +11,18 @@ namespace :stemcell do
     require "bosh/stemcell/stage_collection"
     require "bosh/stemcell/stage_runner"
 
+    os_image_path = File.expand_path(args.os_image_path)
+    if args.operating_system_version.to_s.strip.empty?
+      raise "stemcell:build_os_image: operating_system_version (2nd argument) is empty. " \
+            "Set it to the Ubuntu release codename (for example export short_name=resolute per README), " \
+            "or pass it literally: rake stemcell:build_os_image[ubuntu,resolute,tmp/os.tgz]"
+    end
     definition = Bosh::Stemcell::Definition.for("null", "null", args.operating_system_name, args.operating_system_version)
     environment = Bosh::Stemcell::BuildEnvironment.new(
       ENV.to_hash,
       definition,
       "",
-      args.os_image_path
+      os_image_path
     )
     collection = Bosh::Stemcell::StageCollection.new(definition)
     runner = Bosh::Stemcell::StageRunner.new(
@@ -33,7 +39,7 @@ namespace :stemcell do
       runner: runner,
       archive_handler: archive_handler
     )
-    builder.build(args.os_image_path)
+    builder.build(os_image_path)
 
     sh(environment.os_image_rspec_command)
   rescue RuntimeError => e
@@ -52,12 +58,13 @@ namespace :stemcell do
 
     args.with_defaults(build_number: "0000")
 
+    os_image_path = File.expand_path(args.os_image_path)
     definition = Bosh::Stemcell::Definition.for(args.infrastructure_name, args.hypervisor_name, args.operating_system_name, args.operating_system_version)
     environment = Bosh::Stemcell::BuildEnvironment.new(
       ENV.to_hash,
       definition,
       args.build_number,
-      args.os_image_path
+      os_image_path
     )
 
     sh(environment.os_image_rspec_command)

bosh-stemcell/image-metalinks/ubuntu-resolute.meta4

@@ -0,0 +1,19 @@
+<metalink xmlns="urn:ietf:params:xml:ns:metalink">
+  <file name="ubuntu-resolute.tgz">
+    <hash type="sha-512">placeholder-update-when-resolute-os-image-is-published</hash>
+    <hash type="sha-256">placeholder</hash>
+    <hash type="sha-1">placeholder</hash>
+    <size>0</size>
+    <url>https://storage.googleapis.com/bosh-os-images/ubuntu-resolute/ubuntu-resolute.tgz</url>
+    <version>0.0.0</version>
+  </file>
+  <file name="usn-log.json">
+    <hash type="sha-512">placeholder</hash>
+    <hash type="sha-256">placeholder</hash>
+    <size>1</size>
+    <url>https://storage.googleapis.com/bosh-os-images/ubuntu-resolute/usn-log.json</url>
+    <version>0.0.0</version>
+  </file>
+  <generator>metalink-repository-resource/0.0.0</generator>
+  <published>1970-01-01T00:00:00Z</published>
+</metalink>

bosh-stemcell/spec/assets/dpkg-list-ubuntu-kernel.txt

@@ -1,8 +1,8 @@
 linux-generic
-linux-headers-6.8
-linux-headers-6.8-generic
+linux-headers-7.0
+linux-headers-7.0-generic
 linux-headers-generic
-linux-image-6.8-generic
+linux-image-7.0-generic
 linux-image-generic
-linux-modules-6.8-generic
-linux-modules-extra-6.8-generic
+linux-main-modules-zfs-7.0-generic
+linux-modules-7.0-generic

bosh-stemcell/spec/assets/dpkg-list-ubuntu-vsphere-additions.txt

@@ -2,8 +2,8 @@ libdrm-common
 libdrm2:amd64
 libmspack0t64:amd64
 libpci3:amd64
-libxmlsec1t64:amd64
-libxmlsec1t64-openssl:amd64
+libxmlsec1-1:amd64
+libxmlsec1-openssl1:amd64
 open-vm-tools
 pciutils
 pci.ids