Bug 907792 - [RHSC] 'Maintenance' button not required when a host is in the 'Install Failed' state
Summary: [RHSC] 'Maintenance' button not required when a host is in the 'Install Faile...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Shireesh
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 10:05 UTC by Shruti Sampat
Modified: 2013-07-03 06:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-15 07:05:44 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (137.19 KB, image/png)
2013-02-05 10:05 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2013-02-05 10:05:24 UTC
Created attachment 693295 [details]
screenshot

Description of problem:
---------------------------------------
When a host is in the 'Install Failed' state, the 'Maintenance' button should be seen as active, as it can be removed simply by clicking on the 'Remove' button. Also, any other maintenance activity cannot be performed on the host as it has not been added to the system because installation failed.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.qa5.el6rhs 

How reproducible:

Steps to Reproduce:
1. Click on a host that is in the 'Install Failed' state.

  
Actual results:
The 'Maintenance' button is seen as enabled.

Expected results:
Maintenance button should be disabled for a host that is in the 'Install Failed' state as it not required to move it to maintenance.

Additional info:

Comment 3 Scott Haines 2013-02-06 20:49:28 UTC
Per Feb-06 bug triage meeting, targeting for 2.1.0.

Comment 4 Shireesh 2013-02-15 07:05:44 UTC
On 02/05/2013 04:06 PM, Itamar Heim wrote:
> On 05/02/2013 12:25, Shireesh Anjal wrote:
>> Do RHEV-M folks agree with this? 
>
> not sure.
> also falls into don't nanny the user.
> if should be blocked, then should be at CanDoAction so REST will fail as well, not just a UI validation.
>
> one flow i can think of:
> 1. install failed.
> 2. i manually fix the problem.
> 3. i move host to maint, then activate it, expecting engine to try and reconnect to it, even though install failed?
>
> TBH - not critical enough to fix and may be useful in some flows


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