Description of problem: When attempting to configure internal database after running 'Configure Database Replication' error message says to chose none existent option, "Reset Internal Database". Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create new appliance from template 2. > ap 3. Run `6) Configure Database Replication` option 4. Go through options to setup replication as documented https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.2/html-single/configuring_high_availability/#installation_standby_db 5. Run `5) Configure Database` 6. Run `1) Create Internal Database` 7. select unpartitioned disk 8. Select `Y` for standalone 9. enter passwords Actual results: You get an error message that you can't create an internal database because one was already created which makes sense, but the error says to run "Reset Internal Database" which isn't an option anywhere in the appliance_console. ``` Activating the configuration using the following settings... Host: localhost Username: root Database: vmdb_production An internal database already exists. Choose "Reset Internal Database" to reset the existing installation Configuration failed Press any key to continue. ``` Expected results: List a valid option to resolve this issue. Possibly `Reset Configured Database`. Additional info: 5.8 test-a-thon
Version-Release number of selected component (if applicable): 5.8.0.9-alpha2.20170404195944_1d7ece4
Created attachment 1269471 [details] error message
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1439881
So the `Reset Configured Database` option should be available under configure database (option 5) -> reset configured database (option 4). However this still does not work, we see failed to reset db like in this bz. https://bugzilla.redhat.com/show_bug.cgi?id=1392415 I believe these are really just duplicates of that bz, as once there is certain data created in vmdb reset fails to work.
*** Bug 1439881 has been marked as a duplicate of this bug. ***
@Luke, yes the `Reset Configured Database` option exists under `Configure Database` but the error message says to run "Reset Internal Database" which does not exist. I assume it is just a typo and not referencing a command that does not exist. SO I do not see Bug 1439881 as a duplicate of this bug at all. If anything Bug 1439881 is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1425327. This bug is really just about a typo in the error message, so very minor. Bug 1439881 and Bug 1425327 are the "real" issue.
https://github.com/ManageIQ/manageiq-gems-pending/pull/258
New commit detected on ManageIQ/manageiq-gems-pending/master: https://github.com/ManageIQ/manageiq-gems-pending/commit/935bc4c2a572afbcbd90687217371792d4c48ef0 commit 935bc4c2a572afbcbd90687217371792d4c48ef0 Author: Yuri Rudman <yrudman> AuthorDate: Wed Aug 9 11:09:10 2017 -0400 Commit: Yuri Rudman <yrudman> CommitDate: Wed Aug 9 11:09:10 2017 -0400 change error message to suggested valid option - Reset Configured Database https://bugzilla.redhat.com/show_bug.cgi?id=1439882 lib/gems/pending/appliance_console/internal_database_configuration.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Verified in 5.9.0.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0380