Bug 1578021

Summary:	[RFE] enable high availability when using ovirt compute resource
Product:	Red Hat Satellite	Reporter:	Satellite Program <pm-sat>
Component:	Compute Resources - RHEV	Assignee:	Shira Maximov <mshira>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	inecas, lhellebr, pcreech
Target Milestone:	6.5.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-14 12:37:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Satellite Program 2018-05-14 16:10:43 UTC

We have foreman/katello attached to ovirt. When I provision a VM, I still have to edit the VM in oVirt to set the high availability settings.

It would be nice to set this using the Host Group and maybe add a "Deploy on" field so we can choose between bare

Comment 1 Satellite Program 2018-05-14 16:10:47 UTC

Created from redmine issue http://projects.theforeman.org/issues/17136

Comment 2 Satellite Program 2018-05-14 16:10:49 UTC

Upstream bug assigned to mshira

Comment 4 Satellite Program 2018-08-08 10:08:19 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/17136 has been resolved.

Comment 6 Lukáš Hellebrandt 2019-01-02 13:27:11 UTC

Verified with Sat 6.5 snap 9.

When creating a host: it is possible to select whether it will be HA or not and it has effect on the VM in RHEV

When importing a host: the HA field is correctly pre-filled in the import dialogue based on value in VM in RHEV

When associating the host: the HA field is filled correctly for the existing host based on value in VM in RHEV

Comment 9 errata-xmlrpc 2019-05-14 12:37:19 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://access.redhat.com/errata/RHSA-2019:1222