An OVS-DPDK task had part of its name capitalized,
presumably due to the newly added ansible linter,
but this change was not reflected in the notify
module which calls the task. This results in an
inability to deploy openstack with OVS-DPDK.
This commit fixes the name of the task in the
notify module.
Closes-Bug: #2033413
Change-Id: Iae8a937bb2c35d2eb83e2c4522d829a6cfe25f0d
Signed-off-by: Juan Pablo Suazo <jsuazo@whitestack.com>
It is useful when external network's MTU is lower then internal
geneve networks.
Host kernel needs to be in version >= 5.2 for this option to work.
All Kolla supported host operating systems have higher kernel version.
Change-Id: Id64e99b07e2bb5e6c97b784f4ffedafc7e7de188
Kolla is setting the producer tasks to None, and this
disables all producer tasks.
Starting with the next release of Designate a new task
was added to the producer named increment_serial that
is now critical path for incrementing the serial for each zone.
fb9c2da977
Closes-Bug: #1879557
Change-Id: Ief8dca4e27197c9576e215cbd960da75f6fdc20c
Currently the script only stops containers and removes services,
without disabling service or removing symlink - which renders the
service in a not-found state.
After we disable and stop - some of the services end up in failed
state (due to wrong exit codes for various reasons) - running
reset-failed fixes that.
Change-Id: I637783ce758dbf1c2a7b4b99aa6b61e2c5ca1460
Since I033c51704bfb806f6515db26b8159fae12469ba5 the DUMMY_ENVIRONMENT
environment for cron container is useless, lets drop it.
Trivial-Fix
Change-Id: Id8bf642a57b54ecafe0ee6981e044b1aba872ef7
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Sets the variable ``om_enable_rabbitmq_high_availability`` to ``true``
by default. An upgrade will therefore require some manual steps to
migrate from transient to durable queues. Note that this will be
caught by this precheck:
https://review.opendev.org/c/openstack/kolla-ansible/+/880274
Also updates the CI upgrade jobs to perform this migration. This will
need to be removed in Caracal.
Related-Bug: #2031294
Change-Id: I26a70d4722aaa4663eced5f5337840474c7b961c
Change I60162b54bc06e158534d29311d4474b34750c64d
removed the `/v3` prefix from the WEBSSO_KEYSTONE_URL
variable. However, keystone endpoints do in fact
have the `/v3` prefix, and Horizon expects the
WEBSSO_KEYSTONE_URL variable to already contain
the prefix.
This patch adds the prefix again so that SSO
works with Horizon again.
Closes-Bug: #2028921
Change-Id: I5799f7a6fa4f52c2904b14fc02ed18443f4194bd
Signed-off-by: Juan Pablo Suazo <jsuazo@whitestack.com>
Threads are the recommended way to scale CPU performance since HAProxy
1.8.
Official documentation says: « While "nbproc" historically used to be the only
way to use multiple processors, it also involved a number of shortcomings
related to the lack of synchronization between processes (health-checks, peers,
stick-tables, stats, ...) which do not affect threads. As such, any modern
configuration is strongly encouraged to migrate away from "nbproc" to
"nbthread". ».
Change-Id: I6f2e9d74e68703c8e0827e495945a75f020e1561
Since we use "sleep infinity" in kolla_toolbox container - stopping it
always ends up with exit code 143.
Let's use a wrapper script that handles signals correctly.
Closes-Bug: #2031692
Depends-On: https://review.opendev.org/c/openstack/kolla/+/891777
Change-Id: I84295b909d788ceb67bf09ef60fb0583108b111b
MariaDB bootstrap has a phase where the first MariaDB container
is running with Galera bootstrap - after a check that WSREP
is synced is successful - we restart the container.
The bootstrap container is named mariadb and running with
docker_restart_policy: "no" - the restarted container should be running
in systemd.
Before this patch the code created a systemd unit but it was initially
stopped - so stopping was always a success - and the container would be
killed with SIGKILL on removal (which obviously breaks MariaDB).
This patch also improves docker/systemd stops by waiting for real
unit/container stop and adds failing CI for containers that are
killed with signal 9.
Closes-Bug: #2029613
Change-Id: I0a03e509ce228a50e081fcab44d2b4831251190c
This change block access to the public /server-status url on all
http services exposed by HAProxy, also fixes an issue with Horizon
where 'Require all granted' open access to the /server-status in
the HAProxy-less configurations. Without this change the issue
affects only Ubuntu/Debian installations where mod_status in Apache2
enabled by default.
Closes-Bug: #1996913
Change-Id: I3ec1af6353c3ecc64589599abe375b0ae9b14d5c
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
While this section of the guide does not need to explain every command
available, ``kolla-ansible genconfig`` is a useful command for people
newer to using KA, so it seems worth mentioning in the guide.
Change-Id: I6f58bb395012b701ad349e967fb3d2f16e9373c7
The directive used has the same semantic as what is done above for nbproc > 1:
it binds each thread to a CPU. It is simpler and does not require a loop because
it uses the auto: syntax available in HAProxy 2.4.
Change-Id: I1ce124b678140f5f4737df557683bb67bc7cfc66
Threads are the recommended way to scale CPU performance since HAProxy
1.8.
Official documentation says: « While "nbproc" historically used to be the only
way to use multiple processors, it also involved a number of shortcomings
related to the lack of synchronization between processes (health-checks, peers,
stick-tables, stats, ...) which do not affect threads. As such, any modern
configuration is strongly encouraged to migrate away from "nbproc" to
"nbthread". ».
While more recent versions of HAProxy automatically detect the number of
available CPU and enable threads for them, it can be useful to explicitely set
the value.
In this patch, setting cpu-map for threads is not supported.
Change-Id: Id917c70f3dbe52f24f25d9403ba8151729e8966b
With the parameter ironic_agent_files_directory it is possible to provide
the directory for the ironic-agent.kernel and ironic-agent.initramfs
files. By default the parameter is set to the value of node_custom_config.
This corresponds to the existing behaviour.
Change-Id: I53bb0eddc5380713a967356c85897d8df8ce505f
The external_protocol variable does not exist, resulting in an error
during the venus deployment process. This commit will fix that.
Closes-Bug: #2029353
Change-Id: I2d983eecd8861689fdab7d60bdb9dd34ea0c159e
With the libvirt driver, during live migration,skip comparing guest CPU
with the destination host. When using QEMU >= 2.9 and libvirt >= 4.4.0,
libvirt will do the correct thing with respect to checking CPU
compatibility on the destination host during live migration.[1]
[1] 267a40663c
Change-Id: I947c94b59368c7a2740583bf57e407296473d75e
Currently we don't gather mon/mgr logs, which are essential for
debugging Ceph integration issues - this patch improves that.
Change-Id: I4ec34511b022707d0069d7a07f2f92b34acf0085
Labels are supposed to be strings, but prior to
https://github.com/ansible/ansible/pull/80040 Ansible
did not enforce this.
Change-Id: Iefad160be12f1b5e689a74a82714857fa867d69a
Signed-off-by: Paul Arthur <paul.arthur@flowerysong.com>
The OpenSearch Dashboards container does not have a health
check defined when created. This causes the container to always
restart when reconfigured, even if no change has been made.
Change-Id: I0b437a77aeb61bc5ae9238f900a1fa00cbc34e18
Partial-Bug: #2028362
