Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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

Upstream bug assigned to mshira

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

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

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