Description of problem: Finding it hard to get a testing environment for the foreman-integration feature with rhevm and sat6. I'll try to describe the environment and the current end result: 1. Configured few hosts in a vlan, one of which serves as dhcp and satellite. host is gateway to our internal network and the other hosts communication with out network is routed through that host. 2. installed katello and ran installation foreman installation defining the host as capsule of TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp. installed the foreman-discovery plugin. 3. in satellite - configured all the templates required for host discovery and host provisioning to work. added the ovirtpk puppet class which should invoke the foreman-integration plugin according to http://www.ovirt.org/Features/AdvancedForemanIntegration. 4. on the same host running sat, created a vm via virt-manager and installed rhel6.6 on it and rhevm 3.5 5. rebooted one of the other hosts from pxe in order for it to be discovered by satellite. 6. after discovery, added my satellite as an external provider in the rhevm engine I created. 7. tried to add the discovered host with the use external provider option. 8. host re-provision was invoked - host rebooted, rhel6.5 was installed, after installation puppet was installed and configured according to the provision template and ran upon host reboot. 9. looking at the production.log on the sat host, seems that the OvirtProvisionPlugin was working as expected. Version-Release number of selected component (if applicable): rhevm-3.5.0-0.17.beta.el6ev.noarch foreman-vmware-1.6.0.46-1.el6sat.noarch ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch rose02.qa.lab.tlv.redhat.com-foreman-proxy-1.0-2.noarch foreman-installer-1.6.2-1.el6.noarch foreman-compute-1.6.0.46-1.el6sat.noarch foreman-ovirt-1.6.0.46-1.el6sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.el6sat.noarch foreman-postgresql-1.6.0.46-1.el6sat.noarch foreman-discovery-image-6.5-20140620.2.el6sat.noarch foreman-1.6.0.46-1.el6sat.noarch foreman-gce-1.6.0.46-1.el6sat.noarch ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch foreman-selinux-1.6.0.14-1.el6sat.noarch foreman-proxy-1.6.0.30-1.el6sat.noarch rose02.qa.lab.tlv.redhat.com-foreman-client-1.0-2.noarch foreman-release-1.6.1-1.el6.noarch ruby193-rubygem-foreman-redhat_access-0.0.4-1.el6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch foreman-libvirt-1.6.0.46-1.el6sat.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.1.el6sat.noarch katello-server-ca-1.0-1.noarch ruby193-rubygem-katello-1.5.0-88.el6sat.noarch katello-default-ca-1.0-1.noarch katello-installer-0.0.64-1.el6sat.noarch katello-certs-tools-1.5.6-1.el6sat.noarch rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch katello-1.5.0-30.el6sat.noarch pulp-katello-0.3-4.el6sat.noarch Actual results: the provisioned host stayed on installingOS state. Expected results: host installation is done and host is up after host provisioning in sat is done and OvirtProvisioningPlugin invokes host reboot. Additional info:
Can you attach the production.log please?
Created attachment 952192 [details] production.log
Created attachment 952204 [details] production.log This is the correct log.
2 interesting issue raised here: first, I need to change all the logs in ovirt_provision plugin to be warn or info to show them also if user don't put debug level on. otherwise we can't know anything about the failure (btw, maybe we should expose the production.log somehow via the engine's machine) second, apparently something was changed around the creation of VdsStatic object, it seems that the id is not generated when creating the object. therefore the ovirt_host_id parameter is none on the host's parameters and the plugin fails. Oved, are you familiar with such change in this area? if not, ill add in HostListModel::onSaveInternal line to generate the uuid before calling the provision command. but something was changed there for sure, because month ago the id was there..
> second, apparently something was changed around the creation of VdsStatic > object, it seems that the id is not generated when creating the object. > therefore the ovirt_host_id parameter is none on the host's parameters and > the plugin fails. > > Oved, are you familiar with such change in this area? if not, ill add in > HostListModel::onSaveInternal line to generate the uuid before calling the > provision command. but something was changed there for sure, because month > ago the id was there.. I don't know of changes recently. Did you actually debug it and got to the line where we pass the host_ovirt_id, and saw that the id in the vds object is null?
Verified with a similar environment with VMs as hosts instead bare metals. rhevm-3.5.0-0.22.el6ev.noarch. ruby193-rubygem-ovirt_provision_plugin-1.0.0-1.el6.noarch ruby193-rubygem-rbovirt-0.0.29-1.el6sat.noarch foreman-1.6.0.49-1.el6sat.noarch ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch foreman-compute-1.6.0.49-1.el6sat.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.1.el6sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.el6sat.noarch foreman-selinux-1.6.0.14-1.el6sat.noarch foreman-proxy-1.6.0.30-1.el6sat.noarch foreman-gce-1.6.0.49-1.el6sat.noarch ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.4-1.el6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch foreman-vmware-1.6.0.49-1.el6sat.noarch foreman-libvirt-1.6.0.49-1.el6sat.noarch
rhev 3.5.0 was released. closing.