New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/d3cb71cead6dc896e9df788427d8787f7bb0b31e commit d3cb71cead6dc896e9df788427d8787f7bb0b31e Author: Gregg Tanzillo <gtanzill> AuthorDate: Wed Jan 24 09:03:33 2018 -0500 Commit: Gregg Tanzillo <gtanzill> CommitDate: Wed Jan 24 09:03:33 2018 -0500 Merge pull request #16792 from hstastna/Default_Container_Image_Rate_delete_description Add condition to fix deletion of Default Container Image Rate (cherry picked from commit 164cd082924e89a20acd810cdb9b3f383a2f01a9) https://bugzilla.redhat.com/show_bug.cgi?id=1568084 app/models/chargeback_rate.rb | 2 +- spec/models/chargeback_rate_spec.rb | 8 + 2 files changed, 9 insertions(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq-ui-classic/fine: https://github.com/ManageIQ/manageiq-ui-classic/commit/26cd4f7da686ca9ad212c4e66bca8b7902c20641 commit 26cd4f7da686ca9ad212c4e66bca8b7902c20641 Author: Harpreet Kataria <hkataria> AuthorDate: Fri Feb 9 11:17:10 2018 -0500 Commit: Harpreet Kataria <hkataria> CommitDate: Fri Feb 9 11:17:10 2018 -0500 Merge pull request #3215 from hstastna/Default_Container_Image_Rate_delete Fix deletion of Default Container Image Rate (cherry picked from commit 8806d612ebba610d3319575fd42f4866fcb37808) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568084 app/controllers/chargeback_controller.rb | 23 +- spec/controllers/chargeback_controller_spec.rb | 53 + 2 files changed, 63 insertions(+), 13 deletions(-)
Created attachment 1429738 [details] fixed_proof.png On Tasos's query (refer attached image) - Since custom chargeback report 'rate_gce1' was already there in table, we are not getting 'Remove selected Chargeback Rates from the VMDB' disable in toolbar which is clearly expected from my end. Fixed! Getting expected error while deleting default chargeback. "Chargeback Rate "default_chargeback_name": Error during delete: default rate cannot be deleted" Verified on - 5.8.4.2.20180424224202_be9b69f
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:1972