admin/0pt
5
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

ci(integration): rensa OpenSearch read-only-block (inte bara vattenmärket) #454

Merged
admin merged 1 commits from fix/ci-opensearch-clear-readonly into main 2026-11-02 19:41:49 +00:00
Conversation 0 Commits 1 Files Changed 1
+14 -4
admin commented 2026-11-02 19:29:40 +00:00
Owner
Copy Link
Copy Source

Föregående fix räckte inte: att stänga av disk-vattenmärket rensar inte ett kluster som redan gått i flood stage — cluster.blocks.read_only_allow_delete ligger kvar och varje skrivning ger 403 index_create_block_exception (run 389046 var fortfarande röd).

Nu:

  • sätts tröskeln av redan vid boot (cluster.routing.allocation.disk.threshold_enabled: "false"),
  • rensas read-only-blocket explicit varje försök (read_only_allow_delete: null),
  • skrivs svarskropparna ut vid fel för framtida triage.

Verifierat lokalt mot opensearch:2.11.1: read-only → 403, därefter PUT {read_only_allow_delete: null} → indexskapande 200.

Föregående fix räckte inte: att stänga av disk-vattenmärket **rensar inte** ett kluster som redan gått i flood stage — `cluster.blocks.read_only_allow_delete` ligger kvar och varje skrivning ger `403 index_create_block_exception` (run 389046 var fortfarande röd). Nu: - sätts tröskeln av redan vid boot (`cluster.routing.allocation.disk.threshold_enabled: "false"`), - rensas read-only-blocket explicit varje försök (`read_only_allow_delete: null`), - skrivs svarskropparna ut vid fel för framtida triage. Verifierat lokalt mot `opensearch:2.11.1`: read-only → 403, därefter `PUT {read_only_allow_delete: null}` → indexskapande 200.
admin added 1 commit 2026-11-02 19:29:40 +00:00
ci(integration): clear the OpenSearch read-only block, not just the watermark
masterplan-lock / check (push) Successful in 4s
Details
CI (SIAX Cloud) / sonar (pull_request) Skipped
Details
masterplan-lock / check (pull_request) Successful in 3s
Details
CI (SIAX Cloud) / security (pull_request) Successful in 17s
Details
Security Scan (SIAX Cloud) / security (pull_request) Successful in 18s
Details
CI (SIAX Cloud) / integration (pull_request) Successful in 59s
Details
CI (SIAX Cloud) / quality (pull_request) Successful in 10m24s
Details
f29d2876a1 
Disabling cluster.routing.allocation.disk.threshold_enabled does not clear a
cluster already in flood stage: it keeps cluster.blocks.read_only_allow_delete
and every write returns 403 index_create_block_exception (run 389046, still red
after the previous fix). Clear that block explicitly on every attempt, set the
threshold off at boot, and print the probe/settings bodies for future triage.

Verified locally against opensearch:2.11.1: read-only block -> 403, then
PUT {... read_only_allow_delete: null} -> index creation 200.
CODEOWNERS rules requested review from sax3l 2026-11-02 19:29:40 +00:00
admin merged commit 6a4a45a480 into main 2026-11-02 19:41:49 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
sax3l
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
siax-bot siax-ci siax-healer (siax-healer (CI self-healing agent)) admin (Simon Axelsson)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/0pt#454