CSEC_PUBLIC/securityonion
1
0
Fork 0
mirror of https://github.com/Security-Onion-Solutions/securityonion.git synced 2026-07-15 21:34:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

soup: require green Elasticsearch cluster before upgrading

Browse Source 
Change the pre-flight cluster-health gate to wait_for_status=green instead of
yellow, so soup only proceeds when the cluster is fully green.
This commit is contained in:
Mike Reeves
2026-07-15 12:14:18 -04:00
parent bd70dd53fb
commit 186bf86e99
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
salt/manager/tools/sbin/soup
+5 -6
View File
@@ -329,13 +329,12 @@ check_pillar_items() {
check_cluster_health() {
echo "Checking Elasticsearch cluster health."
# Block only if the cluster cannot reach at least 'yellow' status (i.e. it is red or
# unreachable); 'yellow' is normal for many Security Onion deployments. Modeled on the
# wait used in so-elasticsearch-roles-load.
if so-elasticsearch-query "_cluster/health?wait_for_status=yellow&timeout=120s" --fail > /dev/null 2>&1; then
printf "\nThe Elasticsearch cluster is healthy. We can proceed with SOUP.\n\n"
# Require a 'green' cluster before upgrading; anything less (yellow, red, or
# unreachable) blocks. Modeled on the wait used in so-elasticsearch-roles-load.
if so-elasticsearch-query "_cluster/health?wait_for_status=green&timeout=120s" --fail > /dev/null 2>&1; then
printf "\nThe Elasticsearch cluster is healthy (green). We can proceed with SOUP.\n\n"
else
printf "\nThe Elasticsearch cluster is not healthy (it did not reach at least 'yellow' status). Please resolve the cluster health issue before running SOUP again.\n\n"
printf "\nThe Elasticsearch cluster is not green. Please resolve the cluster health issue so the cluster is green before running SOUP again.\n\n"
exit 0
fi
}