Description of problem: ----------------------- This flash error message is displayed on running Database garbage collection from the UI. Edit aborted! CFME does not support the browser's back button or access from multiple tabs or windows of the same browser. Please close any duplicate sessions before proceeding. Version-Release number of selected component (if applicable): ------------------- 5.4.0.0.26 How reproducible: ---------------- Always Steps to Reproduce: ------------------ 1.Navigate to Configure->Diagnostics. 2.Under the Database tab,hit Submit under 'Run Database Garbage Collection Now' Actual results: -------------- Expected results: --------------- Database garbage collection should be initiated and an appropriate message should be displayed on the screen. Additional info: ----------------
From the log files,it doesn't look like the VACUUM command was issued.
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/58620a58e7dcd71ae5b8b6ecc1e51a0b7606cad1 commit 58620a58e7dcd71ae5b8b6ecc1e51a0b7606cad1 Author: Aparna Karve <akarve> AuthorDate: Thu May 21 10:46:56 2015 -0700 Commit: Aparna Karve <akarve> CommitDate: Thu May 21 10:46:56 2015 -0700 Removed load_edit in garbage collection called from db diagnostics form db diagnostics form has been converted to angular with all instances of @edit removed. load_edit is not relevant anymore https://bugzilla.redhat.com/show_bug.cgi?id=1223114 vmdb/app/controllers/ops_controller/diagnostics.rb | 1 - 1 file changed, 1 deletion(-)
1)Verified in master.20150915141925_58436ca 2)Verified that and an appropriate flash message is displayed on the screen and that the database garbage collection is initiated(based on evm.log). Snippet from evm.log: [----] I, [2015-09-15T16:39:58.310086 #13112:54d990] INFO -- : MIQ(PostgresAdmin.runcmd_with_logging) Running command... vacuumdb --no-password --dbname vmdb_production --username root
Verified in 5.5.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-2015:2551