Bug 1380707 - Link to specific datastore in provider relationships links to all datastores
Summary: Link to specific datastore in provider relationships links to all datastores
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: Martin Hradil
QA Contact: Satyajit Bulage
URL:
Whiteboard: datastore
Depends On:
Blocks: 1388154
TreeView+ depends on / blocked
 
Reported: 2016-09-30 11:55 UTC by Oleksii Tsuman
Modified: 2017-06-12 17:02 UTC (History)
7 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1388154 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:02:41 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
otsuman: automate_bug+


Attachments (Terms of Use)

Description Oleksii Tsuman 2016-09-30 11:55:20 UTC
Description of problem:
If navigate thru Compute->Infrastructure->Providers->"Some provider(for ex. vsphere) -> Relationships -> Datastores and click link of specific datastore(not quadicon, click link with datastore name) it  will redirect to "all datastores" tab ( Compute->Infrastructure-> Datastores)

I think it is problem with JS. Because its happens only one time for each session( if you will repeat it after this steps again it successfully redirect you to selected datastore). And if you close current browser tab and try again - it will reproduced( also once per session) 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Go to Compute->Infrastructure->Providers->"Some provider(for ex. vsphere) -> Relationships -> Datastores
2. Click linked name of specific datastore(not quadicon, field under quadicon)


Actual results:
"all datastores" tab ( Compute->Infrastructure-> Datastores) opened 

Expected results:
Selected datastore details page opened

Comment 4 CFME Bot 2016-10-20 18:31:37 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/9291c3227fee5bbabda697e6bdb59cd30b96b119

commit 9291c3227fee5bbabda697e6bdb59cd30b96b119
Author:     Martin Hradil <mhradil>
AuthorDate: Tue Oct 18 12:32:08 2016 +0000
Commit:     Martin Hradil <mhradil>
CommitDate: Thu Oct 20 17:52:46 2016 +0000

    StorageController#show - set x_node when called with an id
    
    going to a specific datastore from lists that live outside of `storage_controller` - for example from `/ems_infra/123?display=storages` - works by linking to /storage/show/456
    
    However, that path updates x_node before the trees are build and so before the right tree is selected. Forcing to :storage_tree in such a case.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1380707

 app/controllers/storage_controller.rb | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

Comment 5 CFME Bot 2016-10-21 20:05:55 UTC
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/8da31adb214f3698d9186cbe06647fa487bdc3b0

commit 8da31adb214f3698d9186cbe06647fa487bdc3b0
Author:     Dan Clarizio <dclarizi>
AuthorDate: Thu Oct 20 08:29:49 2016 -1000
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Fri Oct 21 15:59:51 2016 -0400

    Merge pull request #12026 from himdel/bz1380707-storage
    
    StorageController#show - set x_node for the right tree, when called with an id
    (cherry picked from commit 6e3d058c223f3d741445b2393724c1bef027e554)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1380707

 app/controllers/storage_controller.rb       |  7 +++----
 spec/controllers/storage_controller_spec.rb | 13 +++++++++++++
 2 files changed, 16 insertions(+), 4 deletions(-)

Comment 7 Satyajit Bulage 2017-03-08 15:46:59 UTC
Navigating to All Datastore's page through provider's summary page. Clicking on the specific Datastore (not quadicon), it is navigating to selected Datastore details/summary page.

Verified Version: 5.8.0.4.20170307183144_745a3d9


Note You need to log in before you can comment on or make changes to this bug.