The version that we were capping to is no longer compatible with latest
upper-constraints.txt, so let us free float again.
The resulting linting errors are included for now to unblock the gate,
these will still need to be discussed or fixed later.
NOTE(kevko): Temporarily disabling horizon deployment, as it's not
possible to unblock gates without it
Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Change-Id: Ib7f72b2663199ef80844a412bc436c6ef09322cc
This allows us to share variables between jobs without inheriting any
of the pre-run, post-run or cleanup playbooks of the parent job. These
run due to the zuul inheritance rules, see:
https://zuul-ci.org/docs/zuul/latest/config/job.html#job
Signed-off-by: Will Szumski <will@stackhpc.com>
Change-Id: Id0a34778accafdc62ebe916e81d69f31c6274d4c
When the kolla-ansible project has a cross dependency on
the kolla project, CI have to build an image from that change
locally. However, Podman refuses to push to localhost, so it is
necessary to set the local repo as insecure for the test.
Change-Id: I786b22ff0cd581f90ba4bec08842651a6509a745
It seems latest ansible-core 2.14 and 2.15 breaks a filter
in kolla-ansible - let's pin for now and fix the issue in a
separate patchset.
Change-Id: I200ad775094230e4bf8bb40988c12ea03471008f
Currently we don't really know what is the OVN cluster status
when test-core-openstack fails on Neutron operations.
Change-Id: Id8ca7c7cd6d741e406f609527016edff592352d7
Up till now the ARA plugin has been pinned to a very old version,
and is no longer functional.
This installs a much newer version of ARA and adds a README file
to guide developers on how to view the sqlite file.
The ARA plugin is installed by default, but not activated. This
is intended to catch a small amount of regressions and
integration failures.
Developers can enable the plugin by adding the string `#ara`
to their commit message. This avoids extra load on the CI.
Change-Id: Id8328e374c9590b1363026fa2b2b24e191183987
Ansible 2.14.3 introduced a change that broke the method used for
restarting MariaDB and RabbitMQ serially [1][2]. In
I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8 we limited to 2.14.2 to work
around this. Ansible upstream claim this behaviour was unintentional,
and will not fix it.
This change moves to a different approach where we use separate plays
with a 'serial' keyword to execute the restart.
This change also removes the restriction on the maximum supported
version of 2.14.2 on ansible-core - any 2.14 release is now supported.
[1] 65366f663d
[2] https://github.com/ansible/ansible/issues/80848
Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208
Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff
The kolla-genpwd, kolla-mergepwd, kolla-readpwd and kolla-writepwd
commands now creates or updates passwords.yml with correct
permissions. Also they display warning message about incorrect
permissions.
Closes-Bug: #2018338
Change-Id: I4b50053ced9150499d1d09fd4a0ec2e243cf938b
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
We limit to 2.14.2 due to a regression in ansible-core [1] that breaks
conditional include_task loops in handlers. This is used for controlled
restarts of MariaDB and RabbitMQ.
[1]: 65366f663d
Change-Id: I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8
Co-Authored-By: Michal Nasiadka <michal@stackhpc.com>
This patch add a way to choose container engine inside tool and test
scripts. This is in preparation for Podman introduction but still
leaves Docker as default container engine.
Signed-off-by: Martin Hiner <m.hiner@partner.samsung.com>
Change-Id: I395d2bdb0dfb4b325b6ad197c8893c8a0f768324
Adds a flag ``kolla-ansible octavia-certificates --check-expiry <days>``
to the ``octavia-certificates`` command to check if the certificates
will expire within a given number of days.
Change-Id: I869b8afd85fe282d823ecf3593aa22f94a61b2a0
This change replaces ElasticSearch with OpenSearch, and Kibana
with OpenSearch Dashboards. It migrates the data from ElasticSearch
to OpenSearch upon upgrade.
No TLS support is in this patch (will be a followup).
A replacement for ElasticSearch Curator will be added as a followup.
Depends-On: https://review.opendev.org/c/openstack/kolla/+/830373
Co-authored-by: Doug Szumski <doug@stackhpc.com>
Co-authored-by: Kyle Dean <kyle@stackhpc.com>
Change-Id: Iab10ce7ea5d5f21a40b1f99b28e3290b7e9ce895
Kolla Ansible is switching to OpenSearch and is dropping support for
deploying ElasticSearch. This is because the final OSS release of
ElasticSearch has exceeded its end of life.
Monasca is affected because it uses both Logstash and ElasticSearch.
Whilst it may continue to work with OpenSearch, Logstash remains an
issue.
In the absence of any renewed interest in the project, we remove
support for deploying it. This helps to reduce the complexity
of log processing configuration in Kolla Ansible, freeing up
development time.
Change-Id: I6fc7842bcda18e417a3fd21c11e28979a470f1cf
This patch follows upstream and disables linuxbridge testing.
Users are notified of the situation via the release note.
Change-Id: I524682ceb5287c14ef0ba99baae0c081850f4c5e
R-17: Switch source images to current release
Disable rocky8 and openeuler jobs as master no longer works with
python3.6.
Change-Id: I89dd99b5f25502f5ebe15a9e90ccecc4bd6feafa
Depending on the way the testing script is called, it may sense
stdin being available and not being a tty [1]. The logic in the
Glance part of the client is then broken [2] as it detects both
volume and stdin as sources of the image and fails.
The proposed approach uses the script module for these tests.
This fixes the cephadm upgrade jobs where this script was called
using the shell module which causes this behaviour. The script
module is not affected. FWIW, the command module is affected
the same as shell because shell extends the command module.
[1] 6810414e45/openstackclient/image/v2/image.py (L114-L120)
[2] 6810414e45/openstackclient/image/v2/image.py (L414)
Change-Id: I3ce4059063e3a51eb1c5b42bda79893b56bd85f0
Story: 2006294
Zuul