Description of problem: Setting up Standby server (Option 6: Configuring Database Replication) before configuring the DB disk, still creates local DB on /var disk which is 2G in size. When you go to configure the DB with the correct disk you fail with error not allowing you to re-configure postgresql (Configuration fails) when going through the appliance_console. Once you are in this state it is unrecoverable. * This will also cause a problem as you will have the Ansible Database on as well that won't move when configuring the DB* List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------------+----------+----------+-------------+-------------+----------------------- awx | awx | UTF8 | en_US.UTF-8 | en_US.UTF-8 | postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres vmdb_production | root | UTF8 | en_US.UTF-8 | en_US.UTF-8 | Version-Release number of selected component (if applicable): 5.8.0.9-alpha2
I was able to reproduce this as well.
Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1439882
This i related to https://bugzilla.redhat.com/show_bug.cgi?id=1412940
This maybe a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1425327
*** This bug has been marked as a duplicate of bug 1439882 ***
@Luke This should not be a dup of Bug 1439882, if anything it is a dup of Bug 1425327.
Ian, I understand what you are saying but this bz has multiple issues. There is an issue of not being able to specify a disk which is a dup of 1425327 I agree, but there is also a reset issue which is covered by 1439882 and 1392415. I will change it to 1425327 if that makes more sense. Thanks, Luke *** This bug has been marked as a duplicate of bug 1425327 ***