# Readiness probe failed waiting for cluster to become ready

**URL:** <https://discuss.elastic.co/t/readiness-probe-failed-waiting-for-cluster-to-become-ready/297192>\
**Category:** Elasticsearch\
**Created:** [February 14, 2022, 9:02pm UTC](https://discuss.elastic.co/t/readiness-probe-failed-waiting-for-cluster-to-become-ready/297192 "2022-02-14T21:02:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloudnative](https://avatars.discourse-cdn.com/v4/letter/c/e9bcb4/32.png) [@cloudnative](https://discuss.elastic.co/u/cloudnative)\
**Post date:** [February 14, 2022, 9:02pm UTC](https://discuss.elastic.co/t/readiness-probe-failed-waiting-for-cluster-to-become-ready/297192/1 "2022-02-14T21:02:20Z")

</div>

Hi, I am currently experiencing the above error after initially experiencing a crashloopbackup error due to a wrong container repo. We were trying to create an a new user account with "bin/Elasticsearch-user ". While this enabled us to create into Elasticsearch with the new user role, the es master pods are not stuck in waiting to be ready state after executing a rollout restart sts command to restart the statefulset. Please image of the error here

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/c/fc79282ec7313ebda2dfc3436d5448eb3e46ba5c.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 14, 2022, 9:02pm UTC](https://discuss.elastic.co/t/readiness-probe-failed-waiting-for-cluster-to-become-ready/297192/2 "2022-03-14T21:02:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.