Description of problem: In the TUI, Register rhevh system to rhevm3.5, it's failed. Version-Release number of selected component (if applicable): Rhev-hypervisor7-7.0-20141006.0.el7ev + rhevm-3.5.0(vt5) ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch vdsm-4.16.6-1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Install rhevh7.0, login to TUI with admin/redhat 2.In the TUI, Go to Network-->Available System NICs, set the DNS server, then enable network ,setting IPv4 settings to "DHCP", save the configuration. 3.Go to Security -->Enable SSH password authentication 4.Go to RHEV-M-->Management Server:10.66.78.3, Setting password will enable SSH daemon , Then click on "save&Register" 5.Open rhev-m webUI with admin/redhat (https://10.66.78.3/), go to "Hosts" tab,choose the rhevh, then click on "Approve" 6.Check the ovirt log in the rhevm # vim /var/log/ovirt-engine/host-deploy/ovirt-*.log Actual results: After step5, Failed to add rhevh to rhevm After step6, it will show some error log in the log, please see the detail in the attachment ovirt.log 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm/vdsm.id Failed to persist "/etc/vdsm/vdsm.id" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/libvirt/private/clientkey.pem Failed to persist "/etc/pki/libvirt/private/clientkey.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/libvirt-spice/server-key.pem Failed to persist "/etc/pki/vdsm/libvirt-spice/server-key.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/keys/vdsmkey.pem Failed to persist "/etc/pki/vdsm/keys/vdsmkey.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/libvirt/clientcert.pem Failed to persist "/etc/pki/libvirt/clientcert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/libvirt-spice/server-cert.pem Failed to persist "/etc/pki/vdsm/libvirt-spice/server-cert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/certs/vdsmcert.pem Failed to persist "/etc/pki/vdsm/certs/vdsmcert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/libvirt/../CA/cacert.pem Failed to persist "/etc/pki/libvirt/../CA/cacert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/libvirt-spice/ca-cert.pem Failed to persist "/etc/pki/vdsm/libvirt-spice/ca-cert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/certs/cacert.pem Failed to persist "/etc/pki/vdsm/certs/cacert.pem" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm/vdsm.id Failed to persist "/etc/vdsm/vdsm.id" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/udev/rules.d/12-ovirt-iosched.rules Failed to persist "/etc/udev/rules.d/12-ovirt-iosched.rules" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm-reg/vdsm-reg.conf Failed to persist "/etc/vdsm-reg/vdsm-reg.conf" 2014-10-13 01:46:36 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm/vdsm.conf Failed to persist "/etc/vdsm/vdsm.conf" 2014-10-13 01:46:36 INFO otopi.context context.runSequence:417 Stage: Pre-termination 2014-10-13 01:46:36 DEBUG otopi.context context.runSequence:421 STAGE pre-terminate 2014-10-13 01:46:36 DEBUG otopi.context context._executeMethod:138 Stage pre-terminate METHOD otopi.plugins.otopi.core.misc.Plugin._preTerminate Expected results: rhevh should add to rhevm3.5 successfully. Additional info: In the rhevm webUI, Add rhevh to rhevm successfully
Created attachment 947100 [details] ovirt.log
Liushihui, can you tell me if this also happens in permissive mode?
It also happens in permissive mode. [root@hp-z220-06 ~]# getenforce Permissive Check the /var/log/ovirt-engine/host-deploy/ovirt-20141023021239-10.66.100.111-6170e91f.log as the following: 2014-10-23 06:12:38 DEBUG otopi.context context._executeMethod:138 Stage closeup METHOD otopi.plugins.otopi.system.reboot.Plugin._closeup 2014-10-23 06:12:38 DEBUG otopi.context context._executeMethod:144 condition False 2014-10-23 06:12:38 DEBUG otopi.context context._executeMethod:138 Stage closeup METHOD otopi.plugins.ovirt_host_deploy.node.persist.Plugin._closeup 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm/vdsm.id Failed to persist "/etc/vdsm/vdsm.id" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/libvirt/private/clientkey.pem Failed to persist "/etc/pki/libvirt/private/clientkey.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/libvirt-spice/server-key.pem Failed to persist "/etc/pki/vdsm/libvirt-spice/server-key.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/keys/vdsmkey.pem Failed to persist "/etc/pki/vdsm/keys/vdsmkey.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/libvirt/clientcert.pem Failed to persist "/etc/pki/libvirt/clientcert.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/libvirt-spice/server-cert.pem Failed to persist "/etc/pki/vdsm/libvirt-spice/server-cert.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/pki/vdsm/certs/vdsmcert.pem Failed to persist "/etc/pki/vdsm/certs/vdsmcert.pem" 2014-10-23 06:12:39 DEBUG otopi.plugins.ovirt_host_deploy.node.persist persist._closeup:69 persisting: /etc/vdsm-reg/vdsm-reg.conf Failed to persist "/etc/vdsm-reg/vdsm-reg.conf" (In reply to Fabian Deutsch from comment #2) > Liushihui, can you tell me if this also happens in permissive mode?
Test version: rhev-hypervisor7-7.0-20141107.0 (https://brewweb.devel.redhat.com/taskinfo?taskID=8214986) ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el7.noarch vdsm-4.16.7.3-1.el7ev.x86_64 ovirt-node-plugin-vdsm-0.2.0-10.el7ev.noarch rhevm vt 9 (hevm-3.5.0-0.19.beta.el6ev.noarch) Test steps: 1.Install rhevh7.0 2.In the TUI, Go to Network-->Available System NICs, set the DNS server, then enable network ,setting IPv4 settings to "DHCP", save the configuration. 3.Enter RHEV-M menu, -->Management Server:10.66.110.5, then click on "save&Register" 4.Open rhev-m webUI and go to "Hosts" tab, choose the rhevh, then click on "Approve" Test result: Register the hypervisor to RHEVM can succeed.
Verified it on rhev-hypervisor7-7.0-20141107.0. Version-Release number of selected component (if applicable): Rhev-hypervisor7-7.0-20141107.0.el7ev + rhevm-3.5.0(vt5) ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el7.noarch ovirt-node-plugin-vdsm-0.2.0-10.el7ev.noarch vdsm-4.16.7.3-1.el7ev.x86_64 Verify process: 1.Install Rhev-hypervisor7-7.0-20141107.0.el7ev, login to TUI with admin/redhat 2.In the TUI, Go to Network-->Available System NICs, set the DNS server, then enable network ,setting IPv4 settings to "DHCP", save the configuration. 3.Go to Security -->Enable SSH password authentication 4.Go to RHEV-M-->Management Server:10.66.78.3, Setting password will enable SSH daemon , Then click on "save&Register" 5.Open rhev-m webUI with admin/redhat (https://10.66.78.3/), go to "Hosts" tab,choose the rhevh, then click on "Approve", success to reigster rhevh to rhevm. 6.Check the ovirt log in the rhevm ,there isn't any failed log show on the log. # vim /var/log/ovirt-engine/host-deploy/ovirt-*.log
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-2015-0160.html