Created attachment 1154096 [details] screenshot Description of problem: Version-Release number of selected component (if applicable): Version 5.6.0.5-beta2.4.20160503153816_1fb554f How reproducible: 100% Steps to Reproduce: 1.Compute->Infrastructure->Providers 2.Click on Any provider(rhevm/vsphere)->Click on Datastores 3.Select any datastore(From the checkbox) and click on Policy 4.Click on Edit Tags Actual results: Tag Assignment Form not displayed after Click on Edit tags. Expected results: Tag Assignment Form should be display after Click on Edit tags. Additional info:
James, I wonder if this is related to the new clustered datastores work.
Dan, looks like a routing error.
https://github.com/ManageIQ/manageiq/pull/8543
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/05b4689f90e7a2108da2f055757f123671584c7d commit 05b4689f90e7a2108da2f055757f123671584c7d Author: Laura Galis <lgalis> AuthorDate: Fri May 6 16:56:13 2016 -0400 Commit: Laura Galis <lgalis> CommitDate: Mon May 9 17:13:02 2016 -0400 Fix tag assignment for datastores when invoked from the provider list https://bugzilla.redhat.com/show_bug.cgi?id=1333257 app/controllers/application_controller/explorer.rb | 7 ++++++- app/controllers/application_controller/tags.rb | 1 + app/controllers/storage_controller.rb | 5 +++++ app/helpers/application_helper/toolbar/storage_center.rb | 1 - app/helpers/application_helper/toolbar/storages_center.rb | 1 - 5 files changed, 12 insertions(+), 3 deletions(-)
https://github.com/ManageIQ/manageiq/pull/7950
https://github.com/ManageIQ/manageiq/pull/8407
Tag Assignment Form is able to display after Clicking on Edit tags. Verified in 5.6.0.6-beta2.5.20160511140943_ff75fb2
https://github.com/ManageIQ/manageiq/pull/8473
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/RHBA-2016:1348