| 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: Id63c035fafaa68a9004c65161c5a3a3ad5544f02
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>
|
|
Change-Id: Iee851c09e63817cd03b780163392517bf35cdfef
Signed-off-by: Bartosz Bezak <bartosz@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: Ib7f551d4a7c6ffe95786853d6899e704de4747b8
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.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>
|
|
Fedora COPR build system cannot handle storing multiple package
versions in one repo.
Change-Id: I3ff95aa75f1f1cccfa40f3ab7f216cb221a6af29
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.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>
|
|
|
|
Change-Id: I92f3095b2d51bd6ac7ff48b0c7d79852eccc9803
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
Switch the RHEL repo to the stable channel as per [1]. Use new GPG.
Telegraf arm64 builds are enabled again, as binaries exists.
[1] https://repos.influxdata.com/stable/x86_64/
Change-Id: Ie4f6f15404f6965df51f3214506ae9f8bb9b61e7
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
This reverts commit e478adcbe63d81faa44bc09f72461fd6a7fcdf94.
Reason for revert: mariabackup fixed
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/957087
Change-Id: Ib694d3be0d2a199469690a01ba17a3349f3802b1
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Closes-Bug: #2119954
Change-Id: I1e334b47c6ab16eb032458141faae55cf39e3eb4
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
|
|
centos stream diverged too much
nothing provides libcrypto.so.3(OPENSSL_3.4.0)(64bit)
needed by erlang-26.2.5.14-1.el9.aarch64
Change-Id: I3a0aa82d0903b341156c2fce68393cc4031e7728
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
Enabling repo should be handled by enable_extra_repos macro
Closes-bug: #2117249
Change-Id: I92af980a4fd63540297b6bde0d52b2dfd02f72ce
Signed-off-by: Grzegorz Koper <grzegorzk@stackhpc.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>
|
|
If a configuration file is tracked in the state file
but no longer appears in config.json, it should either be
restored or removed.
This patch introduces a new exception StateMismatch and
updates execute_config_check() to detect such cases. If
any destination path is present in the defaults state but
missing from config.json, we now raise StateMismatch.
A dedicated unit test has been added to verify
this behavior.
Closes-Bug: #2114173
Signed-off-by: Michal Arbet <michal.arbet@ultimum.io>
Change-Id: I6e0b4aaa5722990e3ac647578023f474db3d4381
|
|
Closes-Bug: #2113874
Change-Id: I71003e0d454deaf75f8e2ad2080077a1118af12c
|
|
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
|
|
This reverts commit 535b2f270faf24cfa30b9aa1a896a62c5090f1aa.
Reason for revert: 10.11.12 is revoked upstream
Change-Id: I0a8cdc232e5b46cb47e4a3e1b0af7b2402103690
|
|
Temporarily disable upgrade jobs to get epoxy rc1
branched this week.
Closes-Bug: #2110122
Change-Id: If301b9ebd7d0dc38bea4d60467e8e80a7a49825d
|
|
|
|
|
|
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
|
|
Change-Id: I6c15cf0fd7b8f1cc3339936c58ad8a8581cfc570
|
|
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
|
|
So far, the certificates were not part of config.json
files for containers. With future patches that will remove
container restarts based on triggers from config and
service-copy-cert, it is important that all files that change
during config are specified in config.json so that
kolla-set-configs --check can detect those changes and based
on that restart the container. This patch provides prerequisite
for future patch in kolla-ansible.
Comments from kevko:
The script also takes into account whether review [1] is
merged or not, ensuring that it will function correctly in
both cases thanks to review [2], because using the state
file, we can effectively verify whether the config.json that
copies CA certs to /var/lib/kolla/share is being used or not.
If we didn’t handle it this way, we would have to rely on
checking whether the directory /var/lib/kolla/share exists or
some another magic, which is insufficient because various
states and combinations of Kolla image and Kolla-Ansible
versions could result in certificates always being copied.
This method provides a clear and definitive distinction.
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/924651
[2] https://review.opendev.org/c/openstack/kolla/+/915440
Change-Id: I5120f1874f25a9ca8326e6db8b12dee4c81feb56
Signed-off-by: Roman Krček <roman.krcek@tietoevry.com>
Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/924651
|
|
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
|
|
This commit restructures the handling of configuration
files in set_configs.py, introducing functions for managing
default configuration files first.
Closes-Bug: #2060855
Change-Id: If91e0330dc149143c82d2183b8ddf6fa9f68d80e
|
|
Added timestamp with milliseconds, log level, and custom
date format to improve clarity and make logs more useful
for debugging.
Change-Id: Ice2d601eddb54bbb0e7e3be6f03ba6db58256c1f
|