[CI] FullClusterRestartIT testSnapshotRestore {cluster=UPGRADED} failing about elasticsearch HOT 7 OPEN

This has been muted on branch main

Mute Reasons:

• [main] 2 consecutive failures in test testSnapshotRestore {cluster=UPGRADED}
• [main] 2 consecutive failures in step 7.17.24_bwc-snapshots
• [main] 2 consecutive failures in pipeline elasticsearch-intake
• [main] 2 failures in test testSnapshotRestore {cluster=UPGRADED} (0.6% fail rate in 358 executions)
• [main] 2 failures in step 7.17.24_bwc-snapshots (8.7% fail rate in 23 executions)
• [main] 2 failures in pipeline elasticsearch-intake (20.0% fail rate in 10 executions)

Build Scans:

• elasticsearch-intake #8871 / 7.17.24_bwc-snapshots
• elasticsearch-intake #8870 / 7.17.24_bwc-snapshots

from elasticsearch.

Pinging @elastic/es-core-infra (Team:Core/Infra)

from elasticsearch.

Pinging @elastic/es-distributed (Team:Distributed)

from elasticsearch.

I think this is a consequence of #111775 and #111777 being muted, suppressing the OLD test executions that set things up ready for the UPGRADED cluster. As this seems to be a bug in the test-muting automation I'm relabelling it for the delivery team.

from elasticsearch.

Pinging @elastic/es-delivery (Team:Delivery)

from elasticsearch.

Yes, this is fallout from #111775

from elasticsearch.

@brianseeders we might need to be smarter about muting parameterized tests. For these we should be muting the base test case, not the parameterized one.

from elasticsearch.