Designate containers are in the unhealthy state

Solution Verified - Updated -

Issue

  • The designate containers are in the unhealthy state after deployment.
  • When check podman ps on the Controller nodes after deployment, designate containers indicate unhealthy state like below.
# podman ps
:
f4e70dd87eed  registry.redhat.io/rhosp-rhel9/openstack-designate-backend-bind9:17.0  kolla_start           11 minutes ago  Up 11 minutes ago                          designate_backend_bind9
79bea859af8e  registry.redhat.io/rhosp-rhel9/openstack-designate-producer:17.0       kolla_start           11 minutes ago  Up 11 minutes ago (unhealthy)              designate_producer
59d1423eb557  registry.redhat.io/rhosp-rhel9/openstack-designate-mdns:17.0           kolla_start           11 minutes ago  Up 11 minutes ago (unhealthy)              designate_mdns
6397fcfabb95  registry.redhat.io/rhosp-rhel9/openstack-designate-central:17.0        kolla_start           11 minutes ago  Up 11 minutes ago (unhealthy)              designate_central
77da01001d5b  registry.redhat.io/rhosp-rhel9/openstack-designate-worker:17.0         kolla_start           11 minutes ago  Up 11 minutes ago (unhealthy)              designate_worker
:
cca74d49806e  registry.redhat.io/rhosp-rhel9/openstack-designate-api:17.0            kolla_start           10 minutes ago  Up 10 minutes ago                          designate_api

Environment

  • Red Hat OpenStack Platform 17.0
  • Red Hat OpenStack Platform 17.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content