Optimize backup fails with ElasticsearchStatusException when retrieving snapshots

[PHWaechtler]

Environment (Required on creation)

Observed in SaaS, but affects 7 and CCSM too. Using most recent Optimize snapshot (/master).

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

When trying to check if a given backup exists, Optimize fails as it encounters an ES exception. It is quite possible that this is related to the recent ES client migration.

Steps to reproduce (Required on creation)

1. Follow this guide to setup an environment for snapshot creation.
2. Once everything is set up, attempt to take a backup and check logs

Observed Behavior (Required on creation)

When Optimize checks if a backup with the given ID exists, it encounters an ES exception that prevents it from proceeding with the snapshot taking.

Expected behavior (Required on creation)

Backup process should work without errors.

Root Cause (Required on prioritization)

Solution Ideas

Hints

Links

Slack thread here

### Pull Requests
- [ ] https://github.com/camunda/camunda-optimize/pull/14277

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[tasso94]

Hey @PHWaechtler,

This went into the 3.14.0 release, right? Can you add the respective version label when you work on issues in the future? We use them to generate release notes and inform other stakeholders, like support or DevEx, what's included in new releases.

Best, Tassilo

[PHWaechtler]

Hey @PHWaechtler,

This went into the 3.14.0 release, right? Can you add the respective version label when you work on issues in the future? We use them to generate release notes and inform other stakeholders, like support or DevEx, what's included in new releases.

Best, Tassilo

Hey @tasso94 , thanks - do you always add the labels before QA? Once QA has confirmed the fix works I would consider this part of the upcoming release 🤞

[tasso94]

Hey @PHWaechtler, I see. The AP7 team assumes it will be part of a release before assigning it to QA, thus prematurely adding the version label. In practice, we rarely have to remove the version label again.

I added this topic as an open point to our Get ready for Optimize 7 document.

[PHWaechtler]

Hey @PHWaechtler, I see. The AP7 team assumes it will be part of a release before assigning it to QA, thus prematurely adding the version label. In practice, we rarely have to remove the version label again.

I added this topic as an open point to our Get ready for Optimize 7 document.

Noted, thanks!