openstack/kolla-ansible.git/ansible/roles/opensearch/handlers/main.yml, branch stable/2026.1

Ensure OpenSearch waits for recovery during upgrade

2026-07-30T08:13:24+00:00

Change-Id: I8825f41a1753eb323e0fdf1bf38a679670e01ba7 Signed-off-by: Alex Welsh (cherry picked from commit 37194fcab7883b8626f2eab5a4f6a19246b85ec9)

Revert "Ensure OpenSearch waits for recovery during upgrade"

2026-07-29T07:51:21+00:00

This reverts commit 79f6f2a049bad1d3cb51ba50981a01f63503a329. Reason for revert: post-config job leaks OpenSearch secret to logs (see failed prometheus-opensearch jobs) Change-Id: I63432e19c42ac9f3eebebadb474882ccda3780ed Signed-off-by: fprzewozn

Ensure OpenSearch waits for recovery during upgrade

2026-07-27T14:22:38+00:00

There's actually two fixes here The first waits until the OpenSearch state is healthy before moving on to Dashboards. Otherwise, OpenSearch Dashboards does its internal `.kibana` index migration before OpenSearch has fully recovered. This creates a corrupted `.kibana_1` index, making Dashboard enter an infinite polling loop and fail to start. The second adds retries to the "Create OpenSearch Dashboards Index Pattern" task. Dashboards seems to take a while to start up post-upgrade, I think again, it's doing some internal migrations for the latest version. Without first checking the API is ready, it consistently fails to be ready, and throws 503s by the time we try to create index patterns. Change-Id: Ic06ccc6b7ec22fa1b0cfa2a144878672d314e93e Closes-Bug: #2161333 Signed-off-by: Alex Welsh (cherry picked from commit 79f6f2a049bad1d3cb51ba50981a01f63503a329)

ansible-lint: Fix yaml[truthy] in opensearch role

2025-11-24T15:32:11+00:00

Change-Id: I12857ee0d5f66b9c9eaa8ff9e3a4655d665eb8a8 Signed-off-by: Michal Nasiadka

Performance: Don't notify handlers during config

2024-12-01T21:16:38+00:00

This patch builds upon genconfig optimisation and it takes it further by not having genconfig ever touch the handlers! Calling the handlers and skipping them created an unnecessary slow down if only config was ran. It also depends on the config checking fix. This gets us closer to the single responsibility principle - config only generates the config, container checks only validate whether container restart is needed. And this also means that we will have single place were containers are restarted, were we can fix the ansible quirk of it restarting the whole group even when one container changed in the following patches. The only exception is the loadbalance role. As the loadbalancer services have their config altered by other roles registering their services using loadbalancer-config. This is in contrast to typical roles, which do config in one step and can then run check-containers in the next step. Fixes some handlers that were missing the necessary guard, making genconfig actually able to restart some containers. Future work: - optimise config by doing local generation and mass rsync - support for reloads - unconditional restart/reload (separate action) - make 'reconfigure' act like 'genconfig' + 'deploy-containers' - this would avoid calling bootstrapping each time but might be tricky as it would break current compatibility - could call this 'reconfigure-containers' and deprecate 'reconfigure' - fix the ansible quirk that notifies more handlers then intended Change-Id: I0ce24043ae5486b2b55489ba40abe2b96b0991a6 Partially-Implements: blueprint performance-improvements Co-Authored-By: Roman Krček

Add ca_path for module uri in opensearch role

2024-07-16T16:11:26+00:00

Fixes an deploy opensearch whith enable TLS on the internal VIP Closes-Bug: #2073224 Change-Id: I50ce48c4e3c645e2f3aeee4913a9bc9ee506040a

Fix OpenSearch upgrade tasks idempotency

2024-01-17T10:57:52+00:00

Shard allocation is disabled at the start of the OpenSearch upgrade task. This is set as a transient setting, meaning it will be removed once the containers are restarted. However, if there is not change in the OpenSearch container it will not be restarted so the cluster is left in a broken state: unable to allocate shards. This patch moves the pre-upgrade tasks to within the handlers, so shard allocation and the flush are only performed when the OpenSearch container is going to be restarted. Closes-Bug: #2049512 Change-Id: Ia03ba23bfbde7d50a88dc16e4f117dec3c98a448

Rename kolla_docker to kolla_container

2023-11-15T12:54:57+00:00

Changes name of ansible module kolla_docker to kolla_container. Change-Id: I13c676ed0378aa721a21a1300f6054658ad12bc7 Signed-off-by: Martin Hiner

Fix OpenSearch Dashboards health check

2023-07-21T15:54:34+00:00

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

Replace ElasticSearch and Kibana with OpenSearch

2022-12-01T10:27:50+00:00

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 Co-authored-by: Kyle Dean Change-Id: Iab10ce7ea5d5f21a40b1f99b28e3290b7e9ce895