| Age | Commit message (Collapse) | Author | Files | Lines |
|
Skydive versions prior to 0.28.0 panic on newer versions of libc.
Fixed upstream in 0.28, see: https://github.com/skydive-project/skydive/issues/2329
This should be backported to at least xena and yoga, as skydive is
currently not working with centos 8 on these releases.
Closes-Bug: #1940862
Change-Id: I177949b9319a977c9cd9121eb28b710256b72a5a
|
|
They do not change often and take space in config.py ;D
Change-Id: I4b15602d53e027470a4b93a8d897f996df684a8d
|
|
|
|
Cap openstacksdk in kolla-toolbox to avoid ansible-openstack-collection
from failing.
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/844905
Change-Id: I4d7dcc413cd9ab0b9db550e1aed7d2229b04c5d1
|
|
|
|
This change fixes an issue with 'apt-get update' command and stop
container building with erroneous source repositories.
Change-Id: I5ce2eb66a647e1805f086aa37942bf5d13eb4106
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
We kept CS8 jobs while waiting to get CentOS Stream 9 support ready.
But we have situations where OpenStack projects fail due to lack of new
enough (3.8+) Python in CS8.
Time to make CS8 go away.
Change-Id: I32bef531896777bfb463bb401ebba1d488a16bf9
|
|
Add a reference on how the release tooling can be used.
Add a bullet point to the meeting agenda.
Drop reference to milestones on launchpad, which are no longer being
used.
Change-Id: I66492a7c74a05849b35a157f7782a6596887427f
|
|
|
|
We still documented some of binary images details. While we do not have
them anymore.
Change-Id: I49148ed788cd35ed9f5606d8b69c5e75230433f3
|
|
Several people use Kolla behind firewall/proxy. Internal mirrors are
often in use then. We do not provide a way to replace repos.yaml file in
an easy way which may lead to complicated solutions or template
overrides.
This patch adds a way to provide own copy of repos.yaml file.
Change-Id: I0b07da22fea27e0ff4e90aaad19e50d84ff9a121
|
|
Replaces Certbot with Lego for certificate retrieval and renewal.
Lego includes support for DNS ACME Challenges.
Adds ssh-client to LetsEncrypt and ssh-server to HAProxy to allow both
the transfer of Let's Encrypt certificates to the HAProxy container and
to enable live updating of HAProxy certifices using the HAProxy API
exposed on the local HAProxy socket.
Implements: blueprint letsencrypt-https
Change-Id: I737e1ce5bfc37d0703879c8272a9e915084c5ca6
|
|
Adds a relevant reno to inform users about the change and the
possibility to customise the prefix.
Additionally, this patch includes the fix to Ubuntu image builds
regarding rabbitmq and erlang.
Both the changes are required to fix master CI.
Change-Id: I6bc8b489a810849744c8bead6b9e350c5d3e36b7
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/843752
|
|
|
|
The original patch did not insert dashes as promised in the commit
message. [1]
[1] https://review.opendev.org/c/openstack/kolla/+/840164
Change-Id: Ibd6e06502ce56f5e0b44dea604ffee2fd9b7b8be
|
|
Following up on [1], Bifrost also needs to use correct u-c and,
surprise-surprise, this is set via a third variable, this time
environment one for the bash script. Oh well. Let's do it.
This has the added benefit of not requiring additional
download of u-c as it reuses the already existing one.
[1] https://review.opendev.org/c/openstack/kolla/+/842276
Change-Id: I2cc79c476d089977b57006dd4ce2e9a8c6206aa1
|
|
This is I2cbf1f539880d512aa223c3ef3a4b19ee18854ac extended to fix
the case when a git repository is used with a git repo.
This is probably a rarer use case but, still, we use it in CI
for in-review changes testing.
Change-Id: I77b0dcd2e9dfd8ea8390a471b80c8954b67ef91b
|
|
The CONFIG REWRITE command rewrites the redis.conf
file the server was started with, applying the minimal
changes needed to make it reflect the configuration
currently used by the server, which may be different
compared to the original one because of the use of
the CONFIG SET command.
https://redis.io/commands/config-rewrite/
Because of above behaviour it's needed to
hack kolla's CMD.
Without this hack container's
/usr/local/bin/kolla_set_configs --check
is always reporting changed state even if
config is not changed.
Therefore redis containers are always restarted
by kolla-ansible. This patch is fixing this.
Change-Id: I8245b9e753fa4175dacfa679a078f63876b0d327
Partial-Bug: #1967664
|
|
Per [1].
[1] http://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html
Change-Id: I46f03329853a2025bff20b7b60e35c06aba619eb
|
|
Bifrost decides on the branches to use by itself.
Early in the cycle, they are often not set correctly and may
break our CI.
This patch ensures we force Bifrost to use the expected branches,
making us independent of Bifrost getting fixed.
Change-Id: I33dbca927062284fd7a06ab6db732dd5e2219c40
|
|
|
|
|
|
Change-Id: Ifa487c077f1feae19e3b021b2ba5dca2dd6d8a99
|
|
I have no idea how Go works. This change make build happen.
Change-Id: I09ea136c7354143f45f856d5e8d8ed1192879622
|
|
This change switches published images names from the current
format <base_distro>-<image_name>:<openstack_release>-<arch_suffix>
to a preciser and image-oriented (for better variant listing) format
<image_name>:<openstack_release>-<base_distro>-<base_distro_version>-<arch_suffix>
Change-Id: I6a4b5c2087b94f96f72aa9d0d0781ff14d3ee6bb
|
|
|
|
|
|
Using cp will leave removed files in kayobe-config.
Change-Id: I39ab4afa4b713ab1a573e2ad9922b4c847ad35ef
|
|
Cinder-volume container can operate on multipath devices but
fails to do so due to absent multipath package for several images.
This fix explicitely adds multipath to the image.
Closes-Bug: #1970541
Change-Id: I14af40078508b06e46866b77ab200228ec827a0d
|
|
Change-Id: I793e35ef347c9d44b4e870cd3ca1bd459e557623
|
|
|
|
|
|
|
|
|
|
Tim Shearer started it in 1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae.
Since all extend_start files are sourced rather than executed, the executable
bits are now cleared throughout the project.
Change-Id: Ia1797c32fc6a35f9f077c673abf4d8e16e51a760
|
|
|
|
|
|
|
|
There is proposed change in kolla-ansible below
which is changing the way how central-logging
works and adding native fluent logging.
Because of this, it's needed to add python
fluent library to openstack images.
Proposed Change:
- https://review.opendev.org/#/c/755775/
Change-Id: Iedc782a3317c93a2af0da4696fd71c05e0e4a55e
|
|
Bug mentioned in Dockerfile was fixed about 4 years ago.
Change-Id: I6d90e6673b01756e7de7c8eeb29423cee0cce6f7
|
|
Kolla supports only AArch64 and x86-64 so there is no need to check for
other architectures.
Change-Id: I44e45492bcbdd56a5c985ba84bad66202c9fde55
|
|
As we have one type of images now some RUN calls could be merged so we
will have less layers in resulting images.
Change-Id: I5178c58fbd8c65efe825dc249c0f1368ef0fe8e0
|
|
These were not available at the time we switched everything else. Venus
remains unavailable.
Change-Id: Ic9e54568a2844991b12e04ebfb1444b5cf286dbb
|
|
We can drop temporary 'use-short-names' argument and make short
(kolla/debian-nova-libvirt:master) image names default.
Kolla Ansible is using short names now.
Change-Id: I153355353cd12aa25adaa9c87438a478748dfb28
|
|
This patch is changing the way how keepalived
checks daemons liveness.
Check_alive.sh will find checks for daemons
which are copied by kolla-ansible and return 0/1
if alive/down.
This patch is required for proxysql HA.
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/770215
Change-Id: I68836918466beb572e42ffedce127747290ad481
|
|
--use-short-names argument drops 'install_type' from image names:
kolla/debian-openstack-base:14.1.0
This should allow to get rid of '-source' in image names without
disrupting CI jobs.
Switch publish jobs to use short names so k-a tests will have ready to
use images for both long and short names.
Change-Id: I29c9d51f4b518a4e2d3157ab5d6cc434fb83f2ef
|
|
We have 'quiet' mode where only minimal data is printed to the console.
But there were no logs at all then.
This change generates log files (if 'logs-dir' argument is used) during
quiet build.
Also enables 'quiet' mode for CI so Zuul will not have to parse 29MB
JSON file each time.
Change-Id: If7d5c2807f0947a8bbbc1ceb8531c9b9c9287c1f
|
|
This reverts commit 09c890b12463a4b2c8767231189e7016f337fbc3.
Reason for revert: That change caused all Kolla's work items to be
transferred. This includes tarballs, their extracted contents, cloned
git repositories, etc. to also be transferred to swift which takes
extra time, pollutes logs and decreases the stability of jobs slightly
(the mechanism is not designed for this kind of load).
The collection of templated Dockerfiles in CI has to be reimplemented
if it is wanted.
Change-Id: Ideaf66ce18c993802f4d20f490caa47cec0dde5e
|
|
The only place where it stays is argument parsing where it gets ignored.
Hardcoded to 'source' to make merging both kolla and kolla-ansible
changes easier.
Change-Id: I6890a7ec7baf507f8acd75b42bbd0fb17c2e4511
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/837620
|
|
A recent change to git [1] introduced a new behaviour to work around a
CVE [2] that disallows any git operations in directories not owned by
the current user.
This may seem unrelated to installation, but it plays havoc with PBR,
which calls out to git to get to get revision history. So if you are
"pip install"-ing from a source tree you don't own, the PBR git calls
in that tree now fail and the install blows up.
When using type=source, kolla clones the repository, then creates a
tarball from it, which is ADDed to the image. The ownership of the files
in the tarball is preserved, which in this case will be the user running
kolla-build. Since the Docker build runs as root, we hit the PBR issue.
Our solution is to make sure that any tarball we generate from git
sources have all files owned by root:root so that the root user is able
to use git commands when building container images.
[1] https://github.com/git/git/commit/8959555cee7ec045958f9b6dd62e541affb7e7d9
[2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24765.
Closes-Bug: #1969096
Related-Bug: #1968877
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Change-Id: I2cbf1f539880d512aa223c3ef3a4b19ee18854ac
|