| Age | Commit message (Collapse) | Author | Files | Lines |
|
It was ommitted in the original influxdb removal patch [1].
[1]: https://review.opendev.org/c/openstack/kolla/+/973051
Change-Id: Ie28d1cc615cc09f013438285b4dcbc2dbab0f4b5
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
(cherry picked from commit 83b8161b12bb1a32b8b872c46533cfa6a2fe9d7f)
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/986483
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/986352
Change-Id: Ia66dde09bbbad2a5a9e67a8c642f3223ca38be43
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Change-Id: I3f0dab4b7d612d3e3f3057c1db8c36e3905cec75
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
This matches the version used by Ubuntu images since Flamingo [1][2].
Debian Trixie still uses 25.03 [3].
Support for 25.03 has ended on 7 March, 2026 [4] while 25.09 is
supported until 5 September, 2026 [5].
[1] https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/flamingo_versions.html
[2] https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/gazpacho_versions.html
[3] https://packages.debian.org/source/trixie/ovn
[4] https://www.ovn.org/en/releases/25.03/
[5] https://www.ovn.org/en/releases/25.09/
Change-Id: I323ea4e7dabecfcf20fa890e028eeb1c3766be0b
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
|
|
According to https://www.influxdata.com/blog/package-signing-key-rotation
the preferred signing key for influxdata package repositories
changed in early 2026. Update to the new preferred key.
Closes-Bug: #2138095
Change-Id: I77d38e713678ea653ded3b14fd0541d3ec0ebee6
Signed-off-by: Michael Still <mikal@stillhq.com>
|
|
Change-Id: I8156e2c2a57d820afdee0b76cd5a050ad682fb38
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Change-Id: I60de8ef452adad4a9b0d974a2678264b91eb6e3b
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
RabbitMQ announced some time ago that the package archives were moving:
https://www.rabbitmq.com/blog/2025/07/16/debian-apt-repositories-are-moving
The old location is no longer working, so this patch transitions to
the new one.
Closes-Bug: #2131736
Change-Id: I6ef0ed9cc40be42a0d98c6a4c83c5c5c26d9cdbf
Signed-off-by: Michael Still <mikal@stillhq.com>
|
|
Fluent Package v5 LTS will reach end of support at
the end of 2025.
Fluent Package v6 LTS will be supported until at least
the end of 2027.
This change updates the apt repository configuration and package version
to use Fluent Package v6 LTS for Ubuntu, Debian and RHEL.
No changes to existing Fluentd configuration files are required.
Change-Id: Iaf3c4de859986629f9768563a319fe0385acff6a
Signed-off-by: Piotr Milewski <vurmil@gmail.com>
|
|
|
|
Add the ability to configure repositories in the same
way as we do Debuntu ones - via repos.yaml.
Removes .repo files from base - since these are not
needed there anymore.
gpgcheck = 1 is default in docker/base/dnf.conf
Change-Id: I7df7d452c45c57c434d5b4ad15a87963e4d6d0d4
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/961237
Change-Id: Idd809f5efd2d308c1565d7635e67af0a431d18f7
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Change-Id: I5e89a9a241f746a2cbab723ea5fc57ea65ad5ee5
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
RDO has staffing problems and has decided to only
support SLURP releases - let's drop reliance on that
repository.
Change-Id: I56f86a1c5262e3ee2bcbb52cae53c3b2655ed87f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Known missing packages:
- mod_auth_mellon - missing SAML support in Keystone/Horizon - built in Kolla COPR
- glusterfs-fuse in manila-share - built in Kolla COPR
- collectd/telegraf - no opstools repository
- redis - needs a switch to valkey
- python3-ethtool - not required for neutron-mlnx-agent since 6 years [1]
Building packages in Kolla COPR is a temporary solution until these show up
in EPEL10.
[1]: Id2cae3ac9ff049e9fc8225551f99e1e99a87fc65
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/951751
Change-Id: I7074fabcf95184fcfd2561648ae1e05acfb0bc11
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/949478
Change-Id: I4507fb60d361ea504459a4b502d6f6c42a327064
|
|
This patch bump proxysql 2.7.x to 3.0.x
Change-Id: I30d5093c1997b1ac99a762983248b8d29e677ba3
|
|
Change-Id: I1ba004df309667460aa152928f789aaf6be6051f
|
|
Ubuntu images were occasionally failing to build due to
unavailability or slowness of the official Ubuntu security
repositories. Although Kolla uses `mirror://` URLs to
leverage Ubuntu mirror infrastructure, the original
`/etc/apt/sources.list.d/ubuntu.sources` file was still
present, causing the system to fallback to default sources.
This commit aligns Ubuntu behavior with Debian by
explicitly removing the distro `.sources` file and relying
solely on the sources configured by Kolla. This ensures
consistent and reproducible builds both in CI and
on local environments.
Closes-Bug: #2112140
Change-Id: I00bcb30662bb12ed8711b28a64ef1941dcce893a
|
|
|
|
|
|
Docker does not support running a container in a given
network namespace (netns) so we need a client installed
in the Neutron container images.
Related-Bug: #1891469
Change-Id: I5349449183dbb7f4ec2042a21526076fb42591b3
|
|
Change-Id: I954106dc32b4c08604d5c40e00fe53e5bb18b266
|
|
Users can override the upper-constraints.txt by setting the source of
openstack-base in kolla-build.conf.
However, bifrost-base Dockerfile so far doesn't pass overridden
upper-constraints file to Bifrost install playbook resulting the
playbook not acknowledging it and just use upstream one.
This change sets the source of Bifrost upper-constraints to use
upper-constraints of openstack-base for consistency among all Kolla
images
With this, change the environment variable UPPER_CONSTRAINTS_FILE is
only affecting kolla-toolbox image.
Therefore, moved UPPER_CONSTRATINS_FILE variable example to the
``kolla_toolbox_pip_conf`` block of kolla-toolbox Dockerfile.
Additionally, updated 'Python packages build options' section of
documentation to represent latest method of changing Python package
related options (including this change).
Change-Id: I0a9c782ca1177ef84e4323cb1e5bfac0fb3f383c
|
|
|
|
(Dalmatian)""
|
|
Python3-pip installs the dependent package tzdata
and blocks the mount of the /etc/localtime file in docker.
After deleting the symbolic link docker correctly mounts
the external localtime file.
Applies only to ubuntu 24.04, in previous versions
of ubuntu there was no such problem
Closes-Bug: #2091161
Change-Id: I733a50b5ca455cfa4b248dc324500d78c17c817b
|
|
This reverts commit db0f87d3c8e1e7eccdeb1ea46216d530711680d3.
Reason for revert: Epoxy cycle is on
Change-Id: Ie2a747223b33039684650bede8863af0c8906d2f
|
|
This patch adds a way to patch files in a Docker
image built by Kolla. This is very useful for several
reasons, specifically:
- Custom modifications
- The stable branch of some library has a fix but no pip
package has been released
- Eliminates the need to package your own pip packages
- Eliminates the need to invent your own versioning to prevent
upstream versioning
- Eliminates the need to manage a pip server
- In other words, it eliminates the need to get a wheel into
the image and install it manually using any method not
previously mentioned
It is also highly desirable because, although Kolla can replace
the source for a service with a custom URL for a tarball or its
own Git repo, it cannot do this for dependencies pulled from pip.
I would also like to point out that this is a feature with its own
code path and works only if the user "inserts" a patch into the folder
patches/docker-image/something.patch and creates an analogous series
file for patch source code.
Simply said, this code will never interfere with the upstream build process
since this feature is not intended for use in upstream.
It is rather meant for downstream users who know what they are doing.
Now they just have an option to patch their images.
Everything works on all layers of the Docker image and stores a report
of applied patches which can then be seen in /etc.
This mechanism is similar as debian patch quilt.
Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/933312
Change-Id: I0ce9e907594fd160a08ad7929d5bc4bca9abf536
|
|
|
|
|
|
Change-Id: I219418411470bdeae9af84277f5150a623c05e69
|
|
This patch bump proxysql 2.6.x to 2.7.x
Change-Id: I6e726d8ebf9dbc6d019dd72d6d0be9d9957a3f22
|
|
This package provides a standalone sysusers binary with
minimal dependencies, designed for use in non-systemd
environments.
This package simply ensures that all packages that want
to install systemd as dependency will have to settle for
this one because the systemd package breaks
systemd-standalone-sysusers, as it is an alternative.
[1] https://packages.debian.org/bookworm/systemd-standalone-sysusers
[2] https://packages.ubuntu.com/noble/systemd-standalone-sysusers
Change-Id: I3ba85069c265844bd2f8b5e6d2b14f32e4898cfd
|
|
This commit removes the hardcoded KOLLA_DISTRO_PYTHON_VERSION
and replaces it with dynamic Python version detection during
container images build. Dockerfiles and scripts now use general
python3 references, simplifying maintenance and ensuring
compatibility with future Python versions.
Test cases relying on distro_python_version were also cleaned up.
Change-Id: I891749598247a5e951ed4a873b16acfd0566f59c
|
|
Provides mechanism for future work to fix bug where when package file
manifest changes, the changes were not reflected in to devmode-enabled
container.
It changes the strategy of installing projects in dev mode in containers.
Instead of bind mounting the project's git repository to the venv
of the container, the repository is bind mounted to
/dev-mode/<project_name> from which the it is installed using pip
on every startup of the container using kolla_install_projects script.
Related-bug: #1814515
Change-Id: Ia1bdff87cba73587a03124ab78a56b21c6176373
Signed-off-by: Roman Krček <roman.krcek@tietoevry.com>
|
|
Change-Id: Id1c028e0650c1fd3aa4c0a7b311a61b26057179c
|
|
This patch bump proxysql 2.5.x to 2.6.x
Change-Id: I26e6c04ad0ba15ad4aa90f95259dc41cad439e73
|
|
Change-Id: I736fcfd766a378783dbfe06ab8ac58858e84aba7
|
|
(Bobcat)""
|
|
This reverts commit 2ed66effa6e4a102919cb53a4b0737f852eb8674.
Reason for revert: Let's use RDO trunk
Change-Id: I3945fe5fd0aef2e12a7f6c60d714e69ea496083b
|
|
Since change I1bc19f8198da3f9ab2ae2a8864c3349b21b0249e we install the
centos-release-ceph-reef package as a dependency, but some code was
still expecting the quincy package.
Change-Id: I8ebcf815d80f3bead25e0078d69b34e17ad013bd
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/900536
Change-Id: I1bc19f8198da3f9ab2ae2a8864c3349b21b0249e
|
|
|
|
Change-Id: Ife390597433fcededf15ecc09db626983e1b8cfd
|
|
This reverts commit 881e3925c7aa8c3bbe6897ea8790f109dc0a7fb8.
Reason for revert: switch back to master, to be followed by switch to bobcat when available
Change-Id: Ib8fdad41a669fc8404b8de2de5361db9547c4ea2
|
|
Launchpad is not traffic constrained, so let's better use that,
instead of the community mirror.
Change-Id: Ie9e0f574c8e3a61e67736caa3faedb8602a5adde
|
|
CloudSmith is over budget, see [1].
As mentionedin in [2] - we're using amd64 packages on aarch64,
since the community mirror does not mirror aarch64 - and the packages
should be really marked as noarch.
[1]: https://github.com/rabbitmq/rabbitmq-server/discussions/9526
[2]: https://github.com/rabbitmq/rabbitmq-server/discussions/9553
Closes-Bug: #2037469
Change-Id: I83179ce5d53fed6cfe7f5fcbf6fdecd7199baa36
|
|
Change-Id: I1967202e23405ad713fd0d54337754d46566156d
Signed-off-by: Sven Kieske <kieske@osism.tech>
|