Bug 992916

Summary: rhev-h will create a bond named "bond=bond0" when auto install it with "bond=bond0:eth1" parameter
Product: Red Hat Enterprise Linux 6 Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: haiyang,dong <hadong>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: acathrow, bsarathy, cshao, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, mburns, ovirt-maint, tlavigne, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-2.el6 Doc Type: Bug Fix
Doc Text:
--no tech note required
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 19:48:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
attached Screenshot none

Description haiyang,dong 2013-08-05 08:03:35 UTC
Created attachment 782713 [details]
attached Screenshot

Description of problem:
Auto install rhev-h with the follow parameters:
BOOTIF=eth0 storage_init=/dev/vda bond=bond0:eth1 firstboot

After auto install success, rhev-h will create a bond named "bond=bond0"(Seen network.png)
Actually, we want it will create a bond named "bond0".

The issue happen in the follow code of /usr/libexec/ovirt-init-functions.sh 
    652             bond=*)
    653             eval $(printf $i|awk -F: '{print "bond_name="$1; print "bond_slaves="$2; print "bond_options="$3;}')
    654             ;;
change into the follow code can resole this issue:
    652             bond=*)
    653             i=${i#bond=}
    654             eval $(printf $i|awk -F: '{print "bond_name="$1; print "bond_slaves="$2; print "bond_options="$3;}')
    655             ;;



Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.5-20130725.0.el6

How reproducible:
100%

Steps to Reproduce:


Actual result:
rhev-h will create a bond named "bond=bond0" 
                                                           
Expect result:
rhev-h will create a bond named "bond0" 

Additional info:

Comment 6 Cheryn Tan 2013-11-08 00:34:13 UTC
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 9 haiyang,dong 2013-12-14 05:34:28 UTC
Test version:
ovirt-node-3.0.1-9.el6_5.noarch.rpm
rhevh-6.5-20131213.0.0.iso

Try auto install to create bond0 with "bond" parameter.
BOOTIF=eth0 storage_init=/dev/sda bond=bond0:eth1 firstboot

It will create a bond with named "bond0" . so this bug has been fixed on ovirt-node-3.0.1-9.el6_5, so change the status into "VERIFIED".

Comment 11 errata-xmlrpc 2014-01-21 19:48:19 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html