Created attachment 1202122 [details] All logs Description of problem: Auto_install rhevh with parameters: BOOTIF=em1 adminpw=OKr05SbCu3D3g storage_init=/dev/sda management_server=10.66.148.253 firstboot After install successfully, can not show rhevh in rhevm side. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20160913.0 ovirt-node-3.6.1-15.0.el7ev.noarch ovirt-node-plugin-vdsm-0.6.1-10.el7ev.noarch vdsm-4.17.35-1.el7ev.noarch Red Hat Enterprise Virtualization Manager Version: 3.6.9.2-0.1.el6 How reproducible: 100% Steps to Reproduce: 1. Auto install rhev-hypervisor7-7.2-20160913.0 with the following parameters: BOOTIF=em1 adminpw=OKr05SbCu3D3g storage_init=/dev/sda management_server=10.66.148.253 firstboot 2. After install successful, reboot and login rhevh 3. Login rhevm UI and check rhevh status Actual results: 1. After step3, can not show rhevh in rhevm UI. vdsmd service is active in rhevh. Expected results: 1. After step3, should show rhevh in rhevm UI Additional info: 1. Also encounter this issue with parameter: management_server=10.66.148.253:443 2. After step3, login rhevh and enter RHEV-M page, click "<Save / Register>", can show rhevh in rhevm UI 3. No such issue in rhev-hypervisor7-7.2-20160829.0, so this is regression and blocker auto_install
Hi, There is no /var/log/messages anymore to auto-registration service grab the karg keys used for registration. The rsyslog dependency got removed from the components in rhev-h affecting it. --- rhev-hypervisor7-7.2-20160829.0.iso.d/isolinux/manifest-srpm.txt 2016-08-29 13:12:46.000000000 -0400 +++ rhev-hypervisor7-7.2-20160913.0.iso.d/isolinux/manifest-srpm.txt 2016-09-13 10:17:53.000000000 -0400 -ceph-0.94.5-14.el7cp.src.rpm +ceph-0.94.5-15.el7cp.src.rpm -glusterfs-3.7.1-16.el7.src.rpm +glusterfs-3.7.9-12.el7.src.rpm -ioprocess-0.15.0-5.el7ev.src.rpm +ioprocess-0.15.2-1.el7ev.src.rpm -libestr-0.1.9-2.el7.src.rpm -mom-0.5.5-1.el7ev.src.rpm +mom-0.5.6-1.el7ev.src.rpm -qemu-kvm-rhev-2.3.0-31.el7_2.16.src.rpm +qemu-kvm-rhev-2.3.0-31.el7_2.21.src.rpm ================ here ======================= -rsyslog-7.4.7-12.el7.src.rpm ================ here ======================= -userspace-rcu-0.7.9-2.el7rhgs.src.rpm +userspace-rcu-0.7.9-2.el7rhs.src.rpm -vdsm-4.17.34-1.el7ev.src.rpm +vdsm-4.17.35-1.el7ev.src.rpm # journalctl -u ovirt-node-plugin-vdsm -- Logs begin at Sun 2016-09-18 16:42:30 UTC, end at Sun 2016-09-18 17:12:01 UTC. -- Sep 18 16:43:00 localhost systemd[1]: Started oVirt Node Plugin VDSM. Sep 18 16:43:00 localhost systemd[1]: Starting oVirt Node Plugin VDSM... Sep 18 16:43:03 localhost /sbin/ovirt-node-plugin-vdsm-autoreg[3476]: ======================================= Sep 18 16:43:03 localhost /sbin/ovirt-node-plugin-vdsm-autoreg[3476]: Auto-Registering the node Sep 18 16:43:03 localhost /sbin/ovirt-node-plugin-vdsm-autoreg[3476]: ======================================= Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: Traceback (most recent call last): Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: File "/sbin/ovirt-node-plugin-vdsm-autoreg", line 183, in <module> Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: sys.exit(main()) Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: File "/sbin/ovirt-node-plugin-vdsm-autoreg", line 136, in main Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: kargs = get_kargs() Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: File "/sbin/ovirt-node-plugin-vdsm-autoreg", line 91, in get_kargs Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: with open('/var/log/messages', 'r') as f: Sep 18 16:43:03 localhost ovirt-node-plugin-vdsm-autoreg[3476]: IOError: [Errno 2] No such file or directory: '/var/log/messages'
Test version: rhev-hypervisor7-7.2-20160920.1 ovirt-node-3.6.1-15.0.el7ev.noarch ovirt-node-plugin-vdsm-0.6.1-11.el7ev.noarch vdsm-4.17.35-1.el7ev.noarch Red Hat Enterprise Virtualization Manager Version: 3.6.9.2-0.1.el6 Test Steps: 1. Auto install rhev-hypervisor7-7.2-20160920.1 with the following parameters: BOOTIF=em1 adminpw=OKr05SbCu3D3g storage_init=/dev/sda management_server=10.66.148.253 firstboot 2. After install successful, reboot and login rhevh 3. Login rhevm UI and check rhevh status Test results: After step3, can show rhevh in rhevm UI, approve host, it can register to rhevm successful. So this bug is fixed in rhev-hypervisor7-7.2-20160920.1, I will change the status to VERIFIED
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/RHBA-2016-1936.html