Description of problem: RHVM 4.2 requires PostgreSQL 9.5 from Software Collections, which means: 1. Local database installed on RHVM host will be upgraded automatically from PG 9.2 to SCL PG 9.5 2. Remote databases has to be upgraded manually so upgrade to 4.2 could finish successfully We need to update RHVM 4.2 documentation to work only with SCL PG 9.5 for both engine and DWH. I've found following sections mentioning PG, but there may be more of them: [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/installation_guide/appe-Preparing_a_Remote_PostgreSQL_Database_for_Use_with_the_Red_Hat_Enterprise_Virtualization_Manager [2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/installation_guide/appe-preparing_a_local_manually-configured_postgresql_database_for_use_with_the_red_hat_enterprise_virtualization_manager [3] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/data_warehouse_guide/installing_and_configuring_data_warehouse_on_a_separate_machine [4] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/data_warehouse_guide/sect-migrating_data_warehouse_to_a_separate_machine [5] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/chap-backups_and_migration [6] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/chap-upgrading_to_red_hat_virtualization_4.1 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 1490273 has been marked as a duplicate of this bug. ***
Reviewed and merged.