Bug 1172629

Summary:	[RFE] Add support for configuring more than 2 power management cards for a host via API
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Eli Mesika <emesika>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED ERRATA	QA Contact:	movciari
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aburden, gklein, iheim, lpeer, lsurette, mperina, oourfali, rbalakri, Rhev-m-bugs, sherold, yeylon, ykaul
Target Milestone:	ovirt-3.6.0-rc	Keywords:	FutureFeature
Target Release:	3.6.0	Flags:	sherold: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	first 3.6.0 build	Doc Type:	Enhancement
Doc Text:	Hosts now support more than two power management cards through the use of sequential and concurrent card configurations.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-09 20:52:57 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1148393

Description Eli Mesika 2014-12-10 13:28:23 UTC

Description of problem:
After the PM re-factoring for 3.6 we will support as a by product more than two agents per host.

For example, till 3.6 if you have a host with IPMI PM plus dual concurrent APC you are able to configure only one of those (or IPMI or APC)

After the PM re-factoring you will be able to set both (from API only) for example the IPMI and the APC as sequential PM devices while the APC itself is dual concurrent


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
No option to add more than 2 PM cards per host

Expected results:
More than 2 PM cards can be configured per host 

Additional info:

Supporting that from UI will require further work....

Comment 2 errata-xmlrpc 2016-03-09 20:52:57 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html