Bug 1073860

Summary:	[webadmin] - 'Select as SPM' button should be disabled when impossible perform this operation successfully
Product:	[oVirt] ovirt-engine	Reporter:	Pavel Stehlik <pstehlik>
Component:	Frontend.WebAdmin	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED WONTFIX	QA Contact:	Aharon Canan <acanan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	acanan, amureini, bugs, gklein, rbalakri, Rhev-m-bugs, scohen, yeylon, ykaul, ylavi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-10 10:49:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Stehlik 2014-03-07 11:15:18 UTC

Description of problem:
 Button 'Select as SPM' is enabled & should be disabled when is not logical/possible to succeed with this operation. Logic should be like with other buttons. 
eg: No DC up; host is already SPM.

Version-Release number of selected component (if applicable):
rhevm-webadmin-portal-3.4.0-0.3.master.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. have DC with host & without SD
2. select host & click on 'Select as SPM' button
3.

Actual results:
Error while executing action: Cannot force select SPM: Storage Domain cannot be accessed.
-Please check that at least one Host is operational and Data Center state is up.


Expected results:


Additional info:
2014-03-07 11:14:37,230 WARN  [org.ovirt.engine.core.bll.ForceSelectSPMCommand] (ajp-/127.0.0.1:8702-8) [733c05e9] CanDoAction of action ForceSelectSPM failed. Reasons:VAR__ACTION__FORCE_SELECT,VAR__TYPE__SPM,$VdsName srh-138,ACTION_TYPE_FAILED_IMAGE_REPOSITORY_NOT_FOUND

Comment 1 Allon Mureinik 2015-01-25 16:43:29 UTC

patch is abandoned, returning to NEW.

Comment 2 Red Hat Bugzilla Rules Engine 2015-11-30 20:43:59 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Yaniv Kaul 2016-03-10 10:49:19 UTC

Closing old tickets, in medium/low severity. If you believe it should be re-opened, please do so and add justification.