Red Hat Bugzilla – Bug 1394887
Editing tags of more cloud volumes accessed from providers summary results in error
Last modified: 2017-03-09 12:04:12 EST
Created attachment 1220473 [details] production.log Description of problem: Version-Release number of selected component (if applicable): 5.6.3.0 How reproducible: Always Steps to Reproduce: 1. Add a cloud provider with cloud volumes 2. Go to cloud providers summary -> Cloud Volumes 3. Check more cloud volumes and Edit Tags Actual results: Nothing happened and production.log error log attached Expected results: Additional info:
Rich you are correct. The user can go through the Cinder Storage Manager to the cloud volumes and do everything requested above in the description of the issue.
This is not an issue on Upstream or on Euwe. I have not verified whether this is actually an issue on Darga.
https://github.com/ManageIQ/manageiq/pull/13251
New commit detected on ManageIQ/manageiq/darga: https://github.com/ManageIQ/manageiq/commit/1e4f9f2878168c3fefb1cd69aecd9efb8c510e24 commit 1e4f9f2878168c3fefb1cd69aecd9efb8c510e24 Author: Harpreet Kataria <hkataria@redhat.com> AuthorDate: Mon Dec 19 13:38:01 2016 -0500 Commit: Harpreet Kataria <hkataria@redhat.com> CommitDate: Mon Dec 19 14:05:29 2016 -0500 Fixed button method to handle tagging button for missing entities. Code was throwing "Render and/or redirect were called multiple times" error when tagging button was pressed from list of cloud_volumes thru Cloud provider relationship. https://bugzilla.redhat.com/show_bug.cgi?id=1394887 app/controllers/ems_common.rb | 13 ++++++------- spec/controllers/ems_common_controller_spec.rb | 16 ++++++++++++++++ 2 files changed, 22 insertions(+), 7 deletions(-)
Verified in 5.6.4.0. I can edit tags for multiple volumes when accessed from providers summary.
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://rhn.redhat.com/errata/RHBA-2017-0474.html