Bug 1207612

This might be related to (or be a race between) the unified persistence of vdsm and the vdsm configure hook in the ovirt-node-plugin-vdsm package.

We should try to understand the flow during the installation.
And we need to understan dif the bug is during installation - or during the first boot (where the vdsm-tool configure call takes place).

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.

Isn't this a dup of a but that was already resolved?

The other (bug 1200207) was about using BOOTIF=<macaddr> , this is about using BOOTIF=<ifname>.

The <ifname> solution worked until recently, and there were no changes in that area on the node side.
It might be possibly related to the race we see with the vdsm hook.

Our testign showed that builds with a more recent vdsm version do not have this bug anymore, probably again a symptom of the recent vdsm/hook race, which is fixed in the next RHEV-H build.

Setting it to TestOnly for now, and will move it to ON_QA once a build is available.

Test version:
rhev-hypervisor7-7.1-20150402.0.el7ev    
ovirt-node-3.2.2-3.el7.noarch

Test steps:
1. Boot from PXE
2. Auto install RHEV-H with below parameters
BOOTIF=enp1s0 storage_init=/dev/sda management_server=$RHEV-M_IP  adminpw=xxxxxx firstboot
3. Login the hypervisor and check the nic status.
4. Approve the hypervisor in RHEVM web UI.

Test results:
1. Auto install: rhevm can get ip address when using BOOTIF=interface
2. Failed to approve the hypervisor.

Message: Host hp-z600-03.qe.lab.eng.nay.redhat.com does not comply with the cluster cshao_intel networks, the following networks are missing on host: 'rhevm'

Details info please see engine.log

Created attachment 1010518 [details]
engine.log

According #c6, change status to ASSIGNED.

I noticed that the fixed in version: ovirt-node-3.2.2-3.el6 ovirt-node-3.2.2-3.el7 rhev-hypervisor6-6.6-20150402.0 rhev-hypervisor7-7.1-20150402.0,
but it not fixed yet, so I have to reassign this bug

Hello shaochen,

(In reply to shaochen from comment #6)
> Test version:
> rhev-hypervisor7-7.1-20150402.0.el7ev    
> ovirt-node-3.2.2-3.el7.noarch
> 
> Test steps:
> 1. Boot from PXE
> 2. Auto install RHEV-H with below parameters
> BOOTIF=enp1s0 storage_init=/dev/sda management_server=$RHEV-M_IP 
> adminpw=xxxxxx firstboot
> 3. Login the hypervisor and check the nic status.
> 4. Approve the hypervisor in RHEVM web UI.
> 
> Test results:
> 1. Auto install: rhevm can get ip address when using BOOTIF=interface
> 2. Failed to approve the hypervisor.
> 
> Message: Host hp-z600-03.qe.lab.eng.nay.redhat.com does not comply with the
> cluster cshao_intel networks, the following networks are missing on host:
> 'rhevm'
> 
> Details info please see engine.log

With the image rhev-hypervisor7-7.1-20150402.0.el7ev  I cannot reproduce the original report anymore. I can do autoinstall/autoregister and approve without any issue. Do you mind to share your vdsm and vdsm-reg logs from the node?

Thanks!

> With the image rhev-hypervisor7-7.1-20150402.0.el7ev  I cannot reproduce the
> original report anymore. I can do autoinstall/autoregister and approve
> without any issue. Do you mind to share your vdsm and vdsm-reg logs from the
> node?
> 
> Thanks!

Re-test this bug with other RHEVM env, the issue has been fixed. Autoinstall & autoregister and approve without any issue. Seem the #c6's issue was occurred due to the broken RHEVM. please ignore it.

Test version:
rhev-hypervisor7-7.1-20150402.0.el7ev    
ovirt-node-3.2.2-3.el7.noarch

Test steps:
1. Boot from PXE
2. Auto install RHEV-H with below parameters
BOOTIF=enp1s0/enp63s0 storage_init=/dev/sda management_server=$RHEV-M_IP  adminpw=xxxxxx firstboot
3. Login the hypervisor and check the nic status.
4. Approve the hypervisor in RHEVM web UI.

Test results:
1. Auto install: rhevm can get ip address when using BOOTIF=interface
2. Approve the hypervisor can succeed.

So the bug has been fixed. I will verify this bug after bug status change to ON_QA.

Thanks!

Test version:
rhev-hypervisor7-7.2-20151104.0
ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch

Test steps:
1. Boot from PXE
2. Auto install RHEV-H with below parameters
BOOTIF=enp63s0/em1 storage_init=/dev/sda management_server=$RHEV-M_IP  adminpw=xxxxxx firstboot
3. Login the hypervisor and check the nic status.
4. Approve RHEV-H in RHEV-M side

Test results:
1. rhevm can get ip address when using BOOTIF=interface.
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