Created attachment 1227214 [details] host_deploy log Description of problem: Add rhvh to engine over dhcp bond failed, and the bond were configured during the anaconda installation. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20161130.0.x86_64 imgbased-0.8.10-0.1.el7ev.noarch vdsm-4.18.17-1.el7ev.x86_64 Red Hat Virtualization Manager Version: 4.0.6-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Install rhvh via anaconda 2. On the network page, add a dhcp bond contains two slave (em1 and p4p2) 3. After the installation, add rhvh to engine over this bond Actual results: 1.After step#3, Failed to configure management network on the host Expected results: 1. After step#3, Add to engine successfully Additional info:
Created attachment 1227217 [details] network-scrpits before adding to engine
Created attachment 1227218 [details] network-scripts after adding to engine
Created attachment 1227219 [details] /var/logs under host
Daijie, could you recheck this bug whether it is still here in last RHVH 4.0.6 build, as we knew, the previous build redhat-virtualization-host-4.0-20161130.0 built incorrect vdsm version in, see bug 1401205.
Still caught the issue in the build redhat-virtualization-host-4.0-20161206.0, will attach the new logs
Created attachment 1228949 [details] network-scripts and deploy logs
Besides, host can not be added to engine with the static VLAN configured during anaconda installation. Guess it is a same issue.
Please provide vdsm and supervdsm logs. Perhaps even Engine logs will help here.
Created attachment 1229428 [details] Include engine.log and vdsm log Please see the detail log
Which bond mode are you using? this could be a dup of bug 1367261
Yes, the same mode (active-backup) with that bug 1367261. And before adding to engine, the bond's ip is did different with the ip got during anaconda.
(In reply to dguo from comment #8) > Besides, host can not be added to engine with the static VLAN configured > during anaconda installation. Guess it is a same issue. Daijie, could you provide the detail steps if you failed adding host with static VLAN configured by NM after anaconda installation?
I re-test with another two systems, adding to engine can be successful with static vlan confiugred during anacnda installation, so just ignore the Comment 8.
Re-test the static bond configured by NM during anaconda installation is also failed to add to engine. I will share my test env by email
The limitation found in Vdsm is as follows: we cannot add a host if it has a bond, and a bond's slave has two connections: an active connection as a slave, and another inactive connection as an independent NIC.
Acquiring NetworkManager ifaces while NetworkManager is operational should solve this issue. Please note that the host deploy currently defaults to disable NM service, therefore this patch will not solve this bug scenario. It should be tested while setting the host deploy to leave NM running.
Verified on rhvh-4.1-20170116.0(vdsm-4.19.1-1.el7ev)