Hide Forgot
Description of problem:after upgrading 5.6 appliance to 5.7.0.4 I can create pg_dump (backups) but can not restore to them using appliance_console Version-Release number of selected component (if applicable):5.7.0.4 How reproducible:100% Steps to Reproduce: 1.provision 5.6 appliance 2.add latest 5.7 repos 3.run yum update 4.log out and in to reload new ruby 5.run 'rake db:migrate' 6.run 'rake evm:automate:reset' 7.start evm 8.check ui login and add provider 9.create backup using 'pg_dump' 10.stop evm 11. use appliance_console option '7' to restore db from backup Actual results:'Failed to restore backup' Expected results: Restore should complete successfully Additional info: appliance_console.log:http://pastebin.test.redhat.com/420181 If I run pg_restore manually it seems to complete with the exception of 'WARNING: errors ignored on restore: 1' however starting evm again and checking the ui it all seems to be working.
Heres a pastbin of the error in manual pg_restore unrecognized configuration parameter "row_security" http://pastebin.test.redhat.com/420360
Yuri, please investigate. Thanks!
'row_security' configuration setting is new in 9.5, and that error indicates that 'pg_dump' used to create dump is version 9.5 but database dump restore into is still older one and need to be upgraded ( https://github.com/ManageIQ/manageiq-appliance/blob/master/LINK/usr/bin/miq_postgres_upgrade.sh)
Hi Yuri, so the issue I was having was after migrating to latest build I was no longer able to restore to new backups I created from said build. I can retest this with running the postgres upgrade script before creating and restoring backups if you suspect this is the issue here? At the point of testing this we didnt have the upgrade script in place. I was of the assumption that it would continue to use postgres94 until I run the upgrade script, but perhaps this is wrong.
Hi Luke, Yes, you need to run postgres upgrade script after upgrading appliance and before using pg_dump/restore.
Hi Yuri, Just tested this on 5.7.0.9 and you are correct it works correctly after running the postgres upgrade, feel free to close this bz. Thanks, Luke
Thank you Luke for update !