Bug 1322345

Summary: bond0 automatic created after installation
Product: [oVirt] ovirt-node Reporter: wanghui <huiwa>
Component: Installation & UpdateAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED NOTABUG QA Contact: wanghui <huiwa>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: bugs, cshao, huiwa, huzhao, leiwang, weiwang, yaniwang, ycui
Target Milestone: ovirt-4.0.0-alphaFlags: fdeutsch: ovirt-4.0.0?
fdeutsch: planning_ack?
fdeutsch: devel_ack+
ycui: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 13:38:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
sosreport none

Description wanghui 2016-03-30 11:04:49 UTC
Description of problem:
bond0 is already created after finished installation.

Version-Release number of selected component (if applicable):
ovirt-node-ng-nightly-boot-20160323.iso
squashfs.20160323
ovirt-node-ng-image-update-placeholder-005-1.el7.noarch
imgbased-0.5-0.201603181316git77345d3.el7.centos.noarch
ovirt-release-host-node-005-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Check the network after finished installation.

Actual results:
1. bond0 is created.

Expected results:
1. bond0 should not be created automatically.

Additional info:

Comment 1 Fabian Deutsch 2016-03-30 11:32:56 UTC
Please provide the sosreport.

Maybe we or vdsm eneds to cleanup the ifcfg scripts.

Comment 2 wanghui 2016-03-30 12:22:08 UTC
Created attachment 1141727 [details]
sosreport

Comment 3 Douglas Schilling Landgraf 2016-04-07 05:00:55 UTC
Hi Wangui,

Could you please confirm that adding into the kargs in grub after the installation: modprobe.blacklist=bonding stops to showing the bond0 interface?

If you prefer, across reboot:

# vi /etc/modprobe.d/blacklist.conf and add: blacklist bonding <reboot>
It will not load automatically the module but if required you can load it again manually anytime.

Comment 4 Douglas Schilling Landgraf 2016-04-07 13:38:18 UTC
Hi Wangui,

I have installed pure CentOS-7-x86_64-Minimal.iso with 3 nics and *no* bond0 interface was created. However, after installing vdsm and rebooting starts to shows the bond0 interface.

# cat /etc/redhat-release 
CentOS Linux release 7.1.1503 (Core) 


# yum localinstall http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
# yum install vdsm

# rpm -qa | grep -i vdsm
vdsm-4.17.23.2-0.el7.centos.noarch
vdsm-xmlrpc-4.17.23.2-0.el7.centos.noarch
vdsm-infra-4.17.23.2-0.el7.centos.noarch
vdsm-yajsonrpc-4.17.23.2-0.el7.centos.noarch
vdsm-hook-vmfex-dev-4.17.23.2-0.el7.centos.noarch
vdsm-python-4.17.23.2-0.el7.centos.noarch
vdsm-jsonrpc-4.17.23.2-0.el7.centos.noarch

# reboot 

<start appearing bond0>

If I remove vdsm and reboot, the bond0 is not created automatically again.

So, based on the above and in the fact that we ship vdsm in ovirt-node-ng image I am closing this report.