DNM: 2026.1 test branch#2371
Conversation
Adds Ubuntu Noble apt repo config for building Gazpacho container images.
There was a problem hiding this comment.
Code Review
This pull request removes support for Rocky 9 and introduces repository configurations and definitions for Rocky 10 and Ubuntu Noble across several files, including kolla-build.conf, repos.yaml, and stackhpc.yml. Feedback on these changes includes updating an outdated comment in kolla-build.conf that still references Rocky 9, removing repository definitions for CentOS Stream 10 and EL10 since they are not yet officially supported, and converting a multi-line gpgkey string in repos.yaml to a single-line format to avoid potential parsing errors.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
a5816ec to
801d341
Compare
This change splits the ci-aio environment into two envs. "aio" is a new environment, designed to be deployed manually. "ci-aio" now inherits from the "aio" env and overrides some variables with CI-specific changes. This allows cleaner separation between what is "aio" and what is "ci". It makes it much easier for customers to now deploy their own AIO instancs. (cherry picked from commit ca555fc)
They were removed from release train [1]. [1] stackhpc/stackhpc-release-train#534 (cherry picked from commit b08fca8)
Running tempest with the ``automated-setup.sh`` for ``aio`` environment fails because it can't locate tempest override configuration for ``aio``. Since ``ci-aio`` Kayobe environment inherits ``aio`` environment, Renamed ``tempest-ci-aio.overrides.conf`` to ``tempest-aio.overrides.conf`` then made symlink to ``tempest-ci-aio.oerrides.conf`` to make them sync. (cherry picked from commit 478eb6b)
This reverts commit 24e2d27.
This reverts commit 3dbf9e4.
K-A bug LP#2160235 is causing service upgrade to fail. Working around by pulling container images in advance. See [1]. [1] https://bugs.launchpad.net/kolla-ansible/+bug/2160235
and updating CIS auditd variables. Unlike RHEL9 CIS, RHEL10 and Ubuntu24 variables for auditd are not dict formatted. Updated them to comply the pinned version of each CIS roles.
K-A patch [1] introduced a new variable ``docker_image_url`` to avoid repeating ``docker_image_name_prefix`` variable. Updating kolla-images.py accordingly. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/951747
Using different playbook path was only needed between 2024.1 and 2025.1 release. Removing as it's now breaking the upgrade path from 2025.1 to 2026.1.
No need to restore kolla/globals.yml anymore.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Added httpd image at ``stackhpc_pulp_images_kolla``. Removed following images from ``stackhpc_pulp_images_kolla``. - mariadb-clustercheck - proxysql-3 (2026.1 K-A default proxysql is version 3.0.x) - influxdb - ironic-inspector - letsencrypt-webserver - rabbitmq-4-1 - redis - redis-sentinel Added containers that uses httpd image to ``IMAGE_TO_CONTAINERS_EXCEPTIONS``. Removed valkey-sentinel from ``CONTAINER_TO_PREFIX_VAR_EXCEPTIONS``.
This image was missed from initial image build because of Kayobe bug LP#2161615 [1]. [1] https://launchpad.net/bugs/2161615
Creating this PR for discussion only right now.
The way kolla configures package repos has changed a lot in the latest release and I need to work out the best way to do it. That might require some changes to kayobe or kolla iself to expose the right variables and make this easier than it has been in previous releases.