Bug 1016440

Summary:	Moving a Host to other cluster does not check PM agent support
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Eli Mesika <emesika>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED NOTABUG	QA Contact:	sefi litmanovich <slitmano>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aberezin, acathrow, bazulay, emesika, iheim, lpeer, mpastern, pstehlik, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-07 11:04:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Eli Mesika 2013-10-08 07:52:13 UTC

Description of problem:

Moving a Host to other cluster does not check PM agent support


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


How reproducible:
Always

Steps to Reproduce:
1.Add a Host to the system with apc_snmp PM card definitions and assign it to 3.3 cluster 

2. Move the Host to a 3.2 cluster
3. No alert is generated on that the cluster version is not supporting the agent (apc_snmp support was added in 3.3)

Actual results:
No alert is generated on that the cluster version is not supporting the agent

Expected results:

An Alert should be generated saying that PM definitions has an unsupported agent when moving the Host from a 3.3 cluster to a 3.2 cluster

Additional info:

Comment 1 Arthur Berezin 2013-10-27 12:06:02 UTC

We should prompt a message asking the user to change to valid 3.2 PM or disable PM for this host, and bring up PM configuration tab. 

Barak, how can a user determine which PM is supported in which cluster level ? (Currently Only Docs?)

Comment 2 Barak 2013-10-27 13:34:35 UTC

IIRC, a recent fix was added to allow the per cluster level PMs when adding a new host to a cluster.
But basically it can be viewed in the configuration (vdc_options), but this is not friendly.

Eli ?

Comment 3 Eli Mesika 2013-10-30 09:18:38 UTC


(In reply to Arthur Berezin from comment #1)
> We should prompt a message asking the user to change to valid 3.2 PM or
> disable PM for this host, and bring up PM configuration tab. 
> 
> Barak, how can a user determine which PM is supported in which cluster level
> ? (Currently Only Docs?)

If you are fencing the Host from UI , your PM agent drop down list will include only agents supported by the Host Cluster level.

From API it is more complex , you should know what is the value of VdsFenceType for the reusted version.

I think that maybe this can be exposed by the API Features mechanism 

Michael , what do you think ???

Comment 4 Barak 2013-10-30 09:47:27 UTC

The API already supports that in the capabilities part.
Under each cluster version one can find the <power_managers> element that contains the supported fencing devices.

Arthur, as far as I'm concerned this is not a bug anymore.