Liveness check should probe the storage backend for OpenShift - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

registry is stuck in a non-usable state
There's a liveness check in the registry, but it only checks the API, not the underlying storage, so it doesn't restart automatically

Environment

OpenShift Container Platform 3.6
integrated OpenShift registry is using glusterfs (CNS).
after a loss of connection from the registry to the glusterfs storage with the connection to glusterfs is restored.
Connecting to the pod reveals a broken mount point from the registry pod to the glusterfs.
In DR scenarios when glusterfs nodes are moved to a different host, or moved back.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)