# StatefulSet not updating if current version of application has warnings

**URL:** <https://discuss.kubernetes.io/t/statefulset-not-updating-if-current-version-of-application-has-warnings/22449>\
**Category:** General Discussions\
**Tags:** docs, development\
**Created:** [December 27, 2022, 10:58am UTC](https://discuss.kubernetes.io/t/statefulset-not-updating-if-current-version-of-application-has-warnings/22449 "2022-12-27T10:58:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gvencadze](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/gvencadze/32/11459_2.png) [@gvencadze](https://discuss.kubernetes.io/u/gvencadze)\
**Post date:** [December 27, 2022, 10:58am UTC](https://discuss.kubernetes.io/t/statefulset-not-updating-if-current-version-of-application-has-warnings/22449/1 "2022-12-27T10:58:07Z")

</div>

Hey, I’ve StatefulSet in which I set updateStrategy to rollingUpdate, but if current version of my application in cluster have warnings (e.g. image pull backoff error or readiness probe failure), than new version of application won’t be deployed until I delete pod manually.

I’ve read the docs, but didn’t find is it expected behavior or not?