The requirement is for to leverage the Foreman provider in order to see information about bare-metal hosts, and provision.
*** Bug 1081371 has been marked as a duplicate of this bug. ***
Verified with: satellite 6.0.6, foreman-1.6.0.49-1.el6sat.noarch, ruby193-rubygem-ovirt_provision_plugin-1.0.1-1.el6.noarch. engine: rhevm-3.5.0-0.26.el6ev.noarch the ovirt provisioning plugin is functional. it was tested on a closed environment with a host serving as dhcp/dns/tftp/satellite server and as gateway from the inner network to outside network. another host served as engine and a third host as the host to be provisioned and installed on rhevm. if network is configured in the correct manner and satellite is configured according to feature wiki page (we might have to add/change some entries on the wiki page) + ovirt provisioning and foreman-discovery plugins are set then flow works: 1. reboot a host on the network and run from pxe. 2. choose foreman-discovery in the pxe menu. 3. host is discovered by foreman. 4. add foreman as an external provider in rhevm. 5. in rhevm, add host choosing 'Use Foreman Hosts Providers', and choose the host from the discovered hosts list. 6. choose a working host group to use for the host provisioning. 7. host state is OS_INSTALLATION and foreman's provisioning template installs os on the host. 8. after os installation is complete and successful host state in rhevm moves to installing as normal. 9. host is up. The flow was tested with rhel 6.6 and rhel 7 provisioned on the host two bugs are still opened but aren't blockers: https://bugzilla.redhat.com/show_bug.cgi?id=1177126 https://bugzilla.redhat.com/show_bug.cgi?id=1177139
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/RHSA-2015-0158.html