@simaishi During upgrades or redeployment we need to ensure we restore the DB v2_key along with database.yml in the check_deployment_status function from the persistent volumes.

In the current implementation, check_deployment_status, when it executes an upgrade/redeployment case, relies on the DB v2_key that comes with the upstream image instead of ensuring is using the v2_key from the PV. This logic breaks redeployments/upgrades on builds that actually create a legitimate/unique v2_key during first deployment such as downstream.

The root issue comes from the fact that we actually supply a dev v2_key during image building for upstream, this bug has been silently hidden by the docker layer that runs the bin/setup script.

As a different PR, we need to address bin/setup in our container builds, this is a script for development purposes, we should not supply images with the v2_dev_key installed.



taken from PR: https://github.com/ManageIQ/manageiq-pods/pull/74