Cluster enters inconsistent state when standing up with existing DB

[braunsonm]

Describe the bug

When standing up a cluster with an existing DB created from cf-for-k8s with the same version will result in a lot of strange errors coming from CAPI. It breaks cf apps sometimes, fails to restage apps, etc.

To Reproduce*

Steps to reproduce the behavior:

1. Deploy cf-for-k8s with an external DB
2. Deploy an app like spring-music
3. Tear down the cluster leaving the DB up
4. Stand up a cluster using the same DB
5. See error

Logs: https://gist.github.com/braunsonm/beebef23a90df054f13aaef12469b549

Expected behavior

The cluster should become consistent with the DB state. No errors should be generated and all the apps should stage again.

Additional context

cf-for-k8s SHA

v2.1.1

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/177275956

The labels on this github issue will be updated when the story is started.