Bug 1383205 - UI: 'Lifecycle' button is still alive, when no providers
Summary: UI: 'Lifecycle' button is still alive, when no providers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: Attila
QA Contact: Satyajit Bulage
URL:
Whiteboard: ui
Depends On:
Blocks: 1395898
TreeView+ depends on / blocked
 
Reported: 2016-10-10 07:51 UTC by Satyajit Bulage
Modified: 2017-06-12 17:41 UTC (History)
5 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1395898 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:41:47 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot showing actual results (63.80 KB, image/png)
2016-10-10 07:51 UTC, Satyajit Bulage 		no flags Details
View All

Description Satyajit Bulage 2016-10-10 07:51:30 UTC 
Created attachment 1208753 [details]
Screenshot showing actual results

Description of problem: In cloud as well as an infrastructure provider, on Virtual Machine or Instance page 'Lifecycle' button is enabled/alive when there is no provider present/added.


Version-Release number of selected component (if applicable):5.7.0.4-alpha1.20161005153002_cfc8a23


How reproducible:100%


Steps to Reproduce:
1.Navigate to Compute --> Infrastructure --> Virtual Machines
2.'Lifecycle' button is still alive.
3.

Actual results:'Lifecycle' is still alive/enabled on Virtual Machines/Instances page


Expected results:It should be enabled when provider is present.


Additional info:
Comment 3 Attila 2016-10-17 19:26:42 UTC 
work in progress
https://github.com/ManageIQ/manageiq/pull/11995
Comment 5 Satyajit Bulage 2017-03-08 15:07:47 UTC 
'Lifecycle' is still alive/enabled on Virtual Machines/Instances page, but options are disabled.

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.