Description of problem:
On CFME-5.8/5.9, there seem to be a problem of performing Reset DB configuration.
On CFME-5.9 it is failing eventually on existing DB connections.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Not sure if this is a regression.
Can you be more specific about the steps to reproduce and provide logs/screenshots (if applicable)?
Have a CFME-18.104.22.168, connected to RHV-4.1 provider.
Run the following commands:
4)Reset Configured Database
Enter database region number:-> Enter the region number that was entered when DB was configured
Getting in response:
Checking for connections to the database...
Warning: There are 19 existing connections to the database preventing the setup of a database region.
Press any key to continue.
* Couldn't find any relevant log, that document this failure.
Created attachment 1351909 [details]
Execute "15) Stop EVM Server Processes" from appliance_console first - it should close open connections to DB.
Thanks a lot for the tip!
Just tried it on CFME-22.214.171.124, and was able to Reset the configured DB.
I am aware of at least 4 people, that met this problem, recently,
but weren't aware to this solution.
IMO, If we could have this tip displayed,
when trying to reset the configured DB,
aside to the "Warning: There are 19 existing connections...",
it would be very helpful.
What do you think, can we add it please?
btw, do you know if this flow is documented in the CFME docs?
Found another related problem.
After running reset configured DB successfully.
I then tried to run Configure the Database,
and I chose same region number that was set, before the reset.
The Configure Database failed as follows:
Activating the configuration using the following settings...
An internal database already exists.
Choose "Reset Internal Database" to reset the existing installation
Press any key to continue.
Can you please advise?
In continue to comment 7,
Running 16) Start EVM Server Processes, allowed to connect to the UI, without Configuring the Database, as mentioned above, as it failed.
Ilanit, I guess taht last sentence "Configuration failed" slightly confusing and may be need to be deleted since there is no any changes made to existing configuration.
(In reply to Yuri Rudman from comment #9)
> Ilanit, I guess taht last sentence "Configuration failed" slightly
> confusing and may be need to be deleted since there is no any changes made
> to existing configuration.
This and good hint for reset external db is not difficult to fix. But for internal one in Comment 7, is that by intention? Thanks
Bo, the best fix for Comment 7 is to find-out that internal DB already exists and show appropriate message without asking many question (user, password, etc..) and after that saying sorry, db already exists
New commit detected on ManageIQ/manageiq-appliance_console/master:
Author: Bo Yao <email@example.com>
AuthorDate: Wed Nov 15 09:55:02 2017 -0500
Commit: Bo Yao <firstname.lastname@example.org>
CommitDate: Fri Nov 17 08:58:24 2017 -0500
hint for reset db with appliances connected
lib/manageiq/appliance_console/database_configuration.rb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
PR to bump manageiq-appliance_console version: https://github.com/ManageIQ/manageiq-appliance/pull/163
Verified in 5.10