Bug 1396725 - SSUI : No Action on clicking console or cockpit Icon
Summary: SSUI : No Action on clicking console or cockpit Icon
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - Service
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Martin Povolny
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-19 11:22 UTC by Shveta
Modified: 2016-12-09 18:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-01 15:38:13 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shveta 2016-11-19 11:22:38 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
5.7.0.11-rc1.20161115160629_46cf4f1 

How reproducible:


Steps to Reproduce:
1. Create a service. VM should be in ON state
2. SSUI , click on that service , click on console or cockpit icon
3.

Actual results: Nothing happens. No error in logs


Expected results:


Additional info:
Comment 3 Chris Kacerguis 2016-12-01 15:01:27 UTC 
Hi Martin,

Could you please help out with this issue?  Everyone on the team is doing other issues.
Comment 4 Chris Hale 2016-12-01 15:21:32 UTC 
Hi,
  I took a look at the dates on this reported issue and it is very possible this issue is no longer a problem.  We submitted a PR a few days ago that reworked how those buttons operate.  https://github.com/ManageIQ/manageiq-ui-service/pull/359   .  This PR was submitted after this ticket was created.  Please reload the latest version of the SUI and retest to see if this is still a problem.  

Thank you
Comment 5 Chris Hale 2016-12-01 15:38:13 UTC 
Martin, I will go ahead and close this one since we believe it has been addressed by my PR earlier in the week.
Note You need to log in before you can comment on or make changes to this bug.