Description of problem:Create database.yml when creating a dedicated database to allow local migrations when upgrading Version-Release number of selected component (if applicable):5.8.1.5 How reproducible:100% Steps to Reproduce: 1.provision 2 pre 5.8 cfme appliances 2.setup one dedicated db 3.create external database with secondary appliance 4.add update.repo to /ect/yum.repo.d/ on both appliances 5.stop evm on non database appliance 6.run yum update 7.run vmdb on database appliance 8.run db:migrate on dedicated db appliance Actual results:Fails due to none existent database.yml Expected results:Migration completes successfully Additional info: In order to run migration of external db it is necessary to run rake tasks from the external cfme appliance (non-database appliance)
This was fixed in https://github.com/ManageIQ/manageiq-appliance_console/pull/38 as a part of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1561075 Moving this to POST.
Verified in 5.10