capi-release 1.47.0 is marked as having downtime issues,
so we rolled back to capi-release 1.46.0 in cf-deployment.
Teams that have been using the
release-candidate branch of cf-deployment may notice problems in their pipelines,
caused by the fact that capi-release 1.47.0 included a database migration that got rolled back as well.
Steps provided here should help teams resolve this issue.
To un-bork your environment based on
you can take the following steps:
- SSH to the API VM so that you can target the database node: