Bug 1007191

Summary: [RFE] Support "BOOTIF=bondname" in auto-install parameters
Product: [oVirt] ovirt-node Reporter: haiyang,dong <hadong>
Component: RFEsAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: medium    
Version: ---CC: bugs, cshao, fdeutsch, gouyang, huiwa, iheim, leiwang, mgoldboi, ovirt-bugs, ovirt-maint, rbalakri, ycui, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1008286 (view as bug list) Environment:
Last Closed: 2015-10-20 14:45:28 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:
Bug Depends On:    
Bug Blocks: 1008286    

Description haiyang,dong 2013-09-12 05:32:40 UTC 
Description of problem:
auto install ovirt-node-iso with the follow parameters:
BOOTIF=bond0 storage_init=/dev/sda bond=bond0:eth0,eth1 firstboot

it will enter TUI install process not auto install process



Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.999.20130909102449gitbee8c8f.564.fc18.iso

How reproducible:
100% 
 
Steps to Reproduce:

Actual result:


Expect result:


Additional info:

--
Comment 1 Mike Burns 2013-09-12 12:21:50 UTC 
hmm...this might be a bug instead of an RFE.  Fabian, thoughts?
Comment 2 Fabian Deutsch 2013-09-16 10:25:35 UTC 
Yep, that sounds more like a bug.

Basically that cmdline should trigger an auto install and create a bond device.
Comment 3 Fabian Deutsch 2013-09-16 10:40:36 UTC 
> 
> Version-Release number of selected component (if applicable):
> ovirt-node-iso-3.1.0-0.999.999.20130909102449gitbee8c8f.564.fc18.iso

I actually can't find the commit bee8c8f. Does it maybe contain a custom patch?

Additionally adding
BOOTIF=link storage_init bond=bond0:eth1,eth2
to the cmdline triggers the auto install - with downstream build based on 3.0.1.
Comment 4 haiyang,dong 2013-09-17 03:25:51 UTC 
(In reply to Fabian Deutsch from comment #3)
> > 
> > Version-Release number of selected component (if applicable):
> > ovirt-node-iso-3.1.0-0.999.999.20130909102449gitbee8c8f.564.fc18.iso
> 
> I actually can't find the commit bee8c8f. Does it maybe contain a custom
> patch?
> 

Using the latest master patch of ovirt-node upstream iso:
http://jenkins.ovirt.org/view/ovirt_node/job/node-devel/646/distro=fedora18/artifact/ovirt-node-iso-3.1.0-0.999.999.20130916155620git5cc2ee2.646.fc18.iso

could reproduce this issue.

> Additionally adding
> BOOTIF=link storage_init bond=bond0:eth1,eth2
> to the cmdline triggers the auto install - with downstream build based on
> 3.0.1.
Hey Fabian,

using bond=bond0:eth0,eth1 will create bond0, i report this bug to want using "BOOTIF=bond0" to configure this bond and make network up.
Comment 5 Fabian Deutsch 2013-09-18 16:04:21 UTC 
(In reply to haiyang,dong from comment #4)
> Hey Fabian,
> 
> using bond=bond0:eth0,eth1 will create bond0, i report this bug to want
> using "BOOTIF=bond0" to configure this bond and make network up.

Ah yes. Thanks for pointing that out.
Yes, true that is not working. And yes, as Mike noted, this is more an RFE.
Comment 6 Itamar Heim 2014-02-13 18:30:55 UTC 
pushing to target release 3.5, assuming its not planned for 3.4 at this point...
Comment 7 Yaniv Lavi 2015-04-07 10:23:32 UTC 
Isn't this fixed in BZ #1008286?