# Incompatible index on upgrade to v3.0.0

**URL:** <https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373>\
**Category:** OpenSearch\
**Tags:** upgrade\
**Created:** [May 13, 2025, 9:05am UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373 "2025-05-13T09:05:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![joelp](https://avatars.discourse-cdn.com/v4/letter/j/65b543/32.png) [@joelp](https://forum.opensearch.org/u/joelp)\
**Post date:** [May 13, 2025, 9:05am UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373/1 "2025-05-13T09:05:43Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):  
OpenSearch 3.0.0

**Describe the issue** :  
I’m trying to upgrade to version 3.0. But getting this error:

```auto
org.opensearch.bootstrap.StartupException: java.lang.IllegalStateException: The index [[.apm-agent-configuration/4B6dvFusQZWVO66YoKQ2Vw]] was created with version [7.10.0] but the minimum compatible version is [2.0.0]. It should be re-indexed in OpenSearch 2.x before upgrading to 3.0.0.

```

When I try to list indices, I don’t see any such index. Even if I try to delete it ( DELETE .apm\*), I’m getting same error

---

<div class="post-metadata">

**Author:** ![jasonrojas](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/jasonrojas/32/4902_2.png) [@jasonrojas](https://forum.opensearch.org/u/jasonrojas)\
**Post date:** [May 13, 2025, 6:23pm UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373/2 "2025-05-13T18:23:00Z")

</div>

You’ll need to do something like this:

```auto
#!/bin/bash

INDEX=$1

curl -k --cert ./admin.pem --key ./admin-key.pem -XPOST 'https://localhost:9200/_reindex?wait_for_completion=true' -H "Content-type:application/json" -d '{"source":{"index":"'${INDEX}'"}, "dest":{"index":"'${INDEX}'-re"}}'
curl -k --cert ./admin.pem --key ./admin-key.pem -XDELETE "https://localhost:9200/${INDEX}"
curl -k --cert ./admin.pem --key ./admin-key.pem -XPOST 'https://localhost:9200/_reindex?wait_for_completion=true' -H "Content-type:application/json" -d '{"source":{"index":"'${INDEX}'-re"}, "dest":{"index":"'${INDEX}'"}}'

```

---

<div class="post-metadata">

**Author:** ![joelp](https://avatars.discourse-cdn.com/v4/letter/j/65b543/32.png) [@joelp](https://forum.opensearch.org/u/joelp)\
**Post date:** [May 15, 2025, 4:42am UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373/3 "2025-05-15T04:42:10Z")

</div>

The solution was to remove the data from `/usr/share/opensearch/data` and start the pod again.

Reindex, even reading was impossible.

---

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [May 15, 2025, 4:26pm UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373/4 "2025-05-15T16:26:05Z")

</div>

@joelp I’m just curious, did you follow the curl commands shared by @jasonrojas ?  
It is important to use superadmin certificate, as most of the hidden indices (.\<index\_name\>) are accessible by a superadmin defined in the admin\_dn of opensearch.yml

---

<div class="post-metadata">

**Author:** ![joelp](https://avatars.discourse-cdn.com/v4/letter/j/65b543/32.png) [@joelp](https://forum.opensearch.org/u/joelp)\
**Post date:** [August 25, 2026, 6:52am UTC](https://forum.opensearch.org/t/incompatible-index-on-upgrade-to-v3-0-0/24373/5 "2026-08-25T06:52:05Z")

</div>

Yes, I perform all such system interventions using an admin account authenticated by a certificate configured as plugins.security.authcz.admin\_dn