Created attachment 998320 [details] attached var logs for rhevh-7.1-20150304.0.el7ev.iso Description of problem: After auto install RHEV-H7.1 with "management_server=$RHEV-M_IP" parameter, rhevh can not register to rhevm3.5. Version-Release number of selected component (if applicable): rhevh-7.1-20150304.0.el7ev.iso ovirt-node-3.2.1-9.el7.noarch vdsm-4.16.8.1-7.el7ev.x86_64 Red Hat Enterprise Virtualization Manager Version: 3.5.0-0.33.el6ev How reproducible: dell machine with nic named "em1" --100% hp machine with nic named "eno1" --100% Steps to Reproduce: 1. Auto install RHEV-H with "management_server=$RHEV-M_IP" parameter 2. Check rhevh on rhevm3.5 side 3. Check in rhevh side Actual results: 1. After step2, rhevh7.1 is not registered on rhevm3.5 side. 2. After step3, the rhevh will display managed by : RHEV-M http://10.66.108.95. and network was unconfigured. No “ifcfg-em1” and "ifcfg-rhevm" files in "/etc/sysconfig/network-scripts". Expected results: 1. After step2, rhevh should list on rhevm3.5 side. Additional info No this issue in RHEV-H 7.0 for RHEV 3.5 build rhevh-7.0-20150128.0.1.el7ev.iso, so it's a regression bug.
Created attachment 998321 [details] attached sosreport logs for rhevh-7.1-20150304.0.el7ev.iso
> I have tried locally with BOOTIF=MACaddress and it doesn't even > start the autoinstall with the iso rhevh-7.1-20150304.0.el7ev.iso (at least > in my vm), it goes to manual install. Answering myself, the PXE IPAPPEND appends "01-" so MAC address during the boot and ovirt-init-functions.sh validates only 07 bytes of MAC address when the BOOTIF option is used. However, during my tests I have added manually the 06 bytes of mac adress into the BOOTIF kernel argument so ovirt-init-functions.sh didn't catch and do not continue the autoinstall. I don't think that's your case, but I have sent a patch to upstream for review anyway. These questions are still valid: could you please confirm that the rhevh-7.1-20150304.0.el7ev.iso doesn't work in the hardwares you shared the with params: "BOOTIF=em1 storage_init=/dev/sda management_server=$RHEV-M_IP firstboot" ? I am asking because I would like to confirm if the issue is only on BOOTIF using the MACaddress or not. Finally, could you please point me the url for: rhevh- 7.0-20150128.0.1.el7ev.iso that you mentioned it worked? > but still failed with "BOOTIF=MACaddress storage_init=/dev/sda > management_server=$RHEV-M_IP firstboot" parameter. Is it go to dracut shell or just simply the host doesn't appear into the RHEV-M? Could you please attach the new logs? Thanks!
(In reply to Douglas Schilling Landgraf from comment #6) > > I have tried locally with BOOTIF=MACaddress and it doesn't even > > start the autoinstall with the iso rhevh-7.1-20150304.0.el7ev.iso (at least > > in my vm), it goes to manual install. > > Answering myself, the PXE IPAPPEND appends "01-" so MAC address during the > boot and ovirt-init-functions.sh validates only 07 bytes of MAC address when > the BOOTIF option is used. However, during my tests I have added manually > the 06 bytes of mac adress into the BOOTIF kernel argument so > ovirt-init-functions.sh didn't catch and do not continue the autoinstall. I > don't think that's your case, but I have sent a patch to upstream for review > anyway. > > These questions are still valid: > > could you please confirm that the rhevh-7.1-20150304.0.el7ev.iso doesn't > work > in the hardwares you shared the with params: "BOOTIF=em1 > storage_init=/dev/sda > management_server=$RHEV-M_IP firstboot" ? Yes, I confirmed BOOTIF=em1 still _not_ work on build rhevh-7.1-20150304.0.el7ev.iso. > > I am asking because I would like to confirm if the issue is only on BOOTIF > using the MACaddress or not. > > Finally, could you please point me the url for: rhevh- > 7.0-20150128.0.1.el7ev.iso that you mentioned it worked? This build is scratch build, only iso, not rpm. so it is gone in brew. I think rhevh 7.0 for 3.5.0 GA build(rhev-hypervisor7-7.0-20150127.0.el7ev) did not have this issue, https://brewweb.devel.redhat.com/buildinfo?buildID=419169 > > > but still failed with "BOOTIF=MACaddress storage_init=/dev/sda > > management_server=$RHEV-M_IP firstboot" parameter. > > Is it go to dracut shell or just simply the host doesn't appear into the > RHEV-M? Could you please attach the new logs? _not_ go to dracut shell. rhevh host auto installed successful, but host can not be listed in rhevm, and rhevh host network is not up after auto installation with management_server=$RHEV-M_IP. Thanks Ying > > Thanks!
Test version: rhev-hypervisor7-7.2-20150928.0 ovirt-node-3.3.0-0.10.20150928gite7ee3f1.el7ev.noarch Test steps: 1. Auto install RHEV-H with ""BOOTIF=em1 storage_init=/dev/sda management_server=$RHEV-M_IP firstboot" parameter 2. Auto install RHEV-H with ""BOOTIF=MACaddress storage_init=/dev/sda management_server=$RHEV-M_IP firstboot" parameter 3. Check rhevh on rhevm3.5 side 4. Check in rhevh side Test result: After step 3: can't approve RHEV-H in RHEV-M side, it show as installation failed, command returned failure code 1. during SSH session... After step 4, met bug 1251151, can not login RHEV-H after automatic installation, so I can't provide log info. So this bug is blocked by bug 1251151, I will verify this bug after 1251151 fixed. Thanks!
(In reply to shaochen from comment #16) > Test version: > rhev-hypervisor7-7.2-20150928.0 > ovirt-node-3.3.0-0.10.20150928gite7ee3f1.el7ev.noarch > RHEV-M 3.6.0-0.18.el6 > Test steps: > 1. Auto install RHEV-H with ""BOOTIF=em1 storage_init=/dev/sda > management_server=$RHEV-M_IP firstboot" parameter > 2. Auto install RHEV-H with ""BOOTIF=MACaddress storage_init=/dev/sda > management_server=$RHEV-M_IP firstboot" parameter > 3. Check rhevh on rhevm3.5 side typo: it should be rhevm3.6. > 4. Check in rhevh side > > Test result: > After step 3: can't approve RHEV-H in RHEV-M side, it show as installation > failed, command returned failure code 1. during SSH session... > After step 4, met bug 1251151, can not login RHEV-H after automatic > installation, so I can't provide log info. > > So this bug is blocked by bug 1251151, I will verify this bug after 1251151 > fixed. > Thanks!
Test version: rhev-hypervisor7-7.2-20151104.0 ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch vdsm-4.17.10.1-0.el7ev.noarch RHEV-M 3.6.0.3-0.1.el6 Test steps: 1. Boot from PXE 2. Auto install RHEV-H with below parameters BOOTIF=xxxxxx storage_init=/dev/sda management_server=$RHEV-M_IP adminpw=xxxxxx firstboot 3. Login the hypervisor and check the network status. 4. Approve RHEV-H in RHEV-M side Test results: 1. RHEV-H can register to RHEV-M. 2. RHEV-H can up in RHEV-M side. So the bug is fixed, change bug status to VERIFIED. Bug 1280241 can trace the issue: Network status shows "Unknown ovirtmgmt" after register to rhevm3.6
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-0378.html