Before reporting an issue

• I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

core

Describe the bug

During fresh intitialization for keycloak with mysql DB, quite a lot migrations are invoked and the keycloak liveness probe does not serve. The pod is restarted due to liveness failure and the subsequent restarted container fails due database inconsistence.

Version

26.0.6

Regression

• The issue is a regression

Expected behavior

The liveness probe should be UP while db migration are in progress

Actual behavior

The failed liveness proble causes container restart

How to Reproduce?

Give the pod little CPU resources and set liveness probe /health/live with startupDelay e.g. 60s.

Anything else?

Thank you for great work!