If we had premium support we wouldn't be asking for help in here. I was under the impression that this is the place to come for help in case you don't have a paid support plan.
Could you answer why is the "\master" user not able to delete the indices I mentioned? If we'd get those deleted then we'd probably be able to carry on with the upgrade.
Also this site does not allow posting the word "\master".
When the cluster is in processing state, the cluster will try to complete the blue/green deployment change for a limited number of times before getting stuck. Once the cluster has failed the maximum number of retries possible, the cluster will remain in processing state until intervened by AWS internal team. Please reach out to the premium support with the ARN of the cluster to get the cluster back to the active state.
Other recommendation is to please follow the best practices for Amazon OpenSearch Service: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/bp.html
openSearch cannot be deleted as it stuck in "Being Deleted"asked 9 months ago
OpenSearch cluster stuck in creationAccepted Answerasked 5 months ago
AWS ElasticSearch Stuck Upgrade processing after 3.5 hoursasked 2 years ago
EKS Cluster stuck in updatingasked 6 months ago
Upgrading Aurora MySQL 5.6 to 5.7 on cross region replica stuck in pre-upgrade checks and reboots every 30 minutesasked 6 months ago
Opensearch upgrade stuckasked 6 months ago
OpenSearch upgrade Stuck at "Check eligibility" for multiple hoursasked 8 months ago
Upgrade ElasticSearch to Opensearch taking 2 monthsasked 7 months ago
Redshift cluster stuck at "Modifying"asked 4 days ago
Upgrade ES 6.3 to 6.4 seems stuckasked 4 years ago