Upgrade to Zammad 7, with "zammad-docker-compose": old ES-index

[sgw]

Infos:

• Used Zammad version: 7
• Used Zammad installation type: docker-compose
• Operating system: Debian 13.4
• Browser + version: FF

I am trying to upgrade a docker-compose-stack from v14.1.5, trying to upgrade to v15.2.1 (using GitHub - zammad/zammad-docker-compose: Zammad Docker images for docker-compose & Kubernetes · GitHub).

Yes, I already filed an issue there also: elasticsearch-9 doesn't upgrade when going to Release v15.2.1 · Issue #560 · zammad/zammad-docker-compose · GitHub

The upgrade of ElasticSearch fails because of an old index.
I don’t know where this index is coming from, the container is only used with Zammad.

pls advise how to upgrade or remove this specific index, in a docker-compose environment (I’d prefer some commands executable with docker-compose exec, for example.

Expected behavior:

Upgrade runs through, new elasticsearch is available.

Actual behavior:

error in ElasticSearch:

“java.lang.IllegalStateException: The index [.geoip_databases/q_z68kWKQDK5NpAmGF890w] created in version [7.17.3] with current compatibility version [7.17.3] must be marked as read-only using the setting [index.blocks.write] set to [true] before upgrading to 9.3.2.”

Steps to reproduce the behavior:

• trying to start the new stack

workaround now

I pinned es to the former version (8.19.9) and run the stack with Zammad-7 and ES-8 … seems to work for now.

[sgw]

I try to list all the indices via:

# docker compose run --rm zammad-railsserver curl -k -XGET 'http://zammad-elasticsearch:9200/_cat/indices?v'

and that geoip-stuff isn’t shown at all.

I get around 20 indexes listed, all starting with zammad_production_ … maybe the rebuild already removed something.

I can only check by trying the upgrade again later today … (I assume)

[sgw]

SOLVED:

I disabled geoip while running the ES-8 container (using a specific overlay-config-file for ES).
This removed the old index, after that I could upgrade ES … etc