As in Kolla - we can not support CS8 anymore due to Python 3.8+
requirement.

Change-Id: Id5567fdedf52e8808400c181e90243fee7f3e136

Masakari-hostmonitor needs to have
corosync/pacemaker deployed.

This patch is just changing default enable_hacluter: "no"
to "yes" if masakari-hostmonitor is enabled.

Closes-Bug: #1934149
Change-Id: I979d1d6d08ca0cc0a748f175da77f68bcecc2d1a

This patch is removing nova configuration
options, this was probably caused by migration
from nova-placement to placement.

Change-Id: Ib54b26428b79d5c4f554928b8634a0bb4e884a90

Even on moderately sized clouds, openstack-exporter can easily take more
than 10 seconds to return, causing Prometheus to fail to scrape data.

Since the default scrape internal is 60 seconds, we can increase the
default timeout to 45 seconds.

Change-Id: Id8dffc425ff057b1e45103eb53734543bca8be80
Closes-Bug: #1976629

This patch is removing api related configuration
from service's config files as we are using
apache mod_wsgi and this configuration is not
used.

Change-Id: I69a1542a6f24214fbf6e703782aefb566de4fb26

CPU model "max" fails to boot CirrOS and some other images when QEMU 7.0
is used.

Change-Id: Ie34a883ac7ae989d7f74c19b9c9ee9f08a82a35f

We need this to be stop-start as haproxy and proxysql need to be
reconfigured simultaneously when switching between them.

This change also introduces checks for service enablement.

Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
Change-Id: I2e10f490305f3d8b1b7abbc66ddb40df65c37fe7

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] https://opendev.org/openstack/python-openstackclient/src/commit/6810414e45a32dd44263dff47fec161989508ef0/openstackclient/image/v2/image.py#L114-L120
[2] https://opendev.org/openstack/python-openstackclient/src/commit/6810414e45a32dd44263dff47fec161989508ef0/openstackclient/image/v2/image.py#L414

Change-Id: I3ce4059063e3a51eb1c5b42bda79893b56bd85f0
Story: 2006294

Follow-up to [1].
This unbreaks CI which was broken by a recent change to
master upper-constraints. [2]

[1] I82c4ff3b246c7db65ac8660b096d4a9a15dda8d7
[2] https://review.opendev.org/c/openstack/requirements/+/843722/3/upper-constraints.txt#b244

Change-Id: Idc7a893f53c6975cc4a3f6090020d973fa2288bb

Change-Id: Id8573ad6727c62e355923b787c51766bc27ed848

Following up on [1].
The 3 variables are only introducing noise after we removed
the reliance on Keystone's admin port.

[1] I5099b08953789b280c915a6b7a22bdd4e3404076

Change-Id: I3f9dab93042799eda9174257e604fd1844684c1c

Per Clark Boylan's feedback [1], retries cause a retry not only
for pre playbook failures but also for cases where Ansible detects
network connectivity issues and they are caused by disks getting
filled to their fullest. This is an issue we experience that
sometimes results in a POST_FAILURE but certain FAILUREs are
retried which wastes CI resources.
The problematic jobs are ceph jobs. They are to be looked into.
Backport to all branches.
We can adjust retries for the core jobs that do not exhibit the
nasty behaviour but first we can try running without retries
to measure the troublesomeness.

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/843536

Change-Id: I32fc296083b4881e8f457f4235a32f94ed819d9f

Docs and reno included.

Change-Id: I5099b08953789b280c915a6b7a22bdd4e3404076

Change-Id: I44c8a059918918f5bdc1c0190110a05d8d7f8f2d

Add a switches to enable/disable deploy of the Masakari monitors.

Change-Id: I3ab603f7cab7946ea8f2e063fe91190d6592066a
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

Closes-Bug: #1975598
Change-Id: If4c85f8e960141d08a89accdc11a3271f31974c1

From:

(kolla) 13:11 (s) marcin@puchatek:kolla-ansible$ kolla-genpwd
Traceback (most recent call last):
  File "/home/marcin/.virtualenvs/kolla/bin/kolla-genpwd", line 8, in <module>
    sys.exit(main())
  File "/home/marcin/.virtualenvs/kolla/lib/python3.10/site-packages/kolla_ansible/cmd/genpwd.py", line 135, in main
    genpwd(passwords_file, length, uuid_keys, ssh_keys, blank_keys,
  File "/home/marcin/.virtualenvs/kolla/lib/python3.10/site-packages/kolla_ansible/cmd/genpwd.py", line 59, in genpwd
    with open(passwords_file, 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/etc/kolla/passwords.yml'

To:

(kolla) 13:17 (s) marcin@puchatek:kolla-ansible$ kolla-genpwd
ERROR: Passwords file "/etc/kolla/passwords.yml" is missing

Change-Id: I18a9559daeb3d124a03dcb735ebb01a2cf24f617

Change-Id: Ic55a7384c298ef517aa4b7f0eaa67d53b5d70df0

Change-Id: Ib4b15ed4feac82d8492b1c0f0238a752eac668e6

Since enabling libvirt SASL authentication, the masakari instance
monitor fails to connect to libvirt. We see the following error in logs:

    libvirt.libvirtError: authentication failed: Failed to start SASL
    negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs
    found)

This change adds support for SASL authentication in Masakari instance
monitor.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/834456
Closes-Bug: #1965754
Change-Id: I974046662b383a12ac6281b725523760a96657bd

It was removed as part of improvements in [1]. But it seems it's
a different type/class of errors and should still be filtered
out here.
This time for all the services to avoid extra copies.

[1] Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1

Change-Id: If7c5b938dc7417831a90f360d6e3655d1ad4084e

The projects started dropping support for Python 3.6 and thus
CentOS Stream 8 which K-A tests against, resulting in broken CI.
This change ensures that we keep upper-contraints also on Yoga as
we do for the images we deploy.

Change-Id: I82c4ff3b246c7db65ac8660b096d4a9a15dda8d7