NFS export definitions and data stored on NFS exports are not automatically
removed. You are urged to manually erase any data from old application or
database deployments before attempting to initialize a new deployment.

Troubleshooting

Failure to erase old PostgreSQL data can result in cascading errors, causing the
postgresql pod to enter a crashloopbackoff state. This blocks the
cfme
pod from ever starting. The cause of the crashloopbackoff is due to incorrect
file permissions on the database NFS export created during a previous
deployment.

To continue, erase all data from the PostgreSQL export and delete the pod (not
the deployer pod). For example, if you had the following pods:

The PostgreSQL deployer pod will try to scale up a new postgresql pod to replace the
one you deleted. After the postgresql pod is running, the
cfme
pod will stop blocking and begin application initialization.