Bug 1353531

Summary:	Bonding network options not configured correctly during undercloud deployment
Product:	Red Hat OpenStack	Reporter:	Eduard Barrera <ebarrera>
Component:	instack-undercloud	Assignee:	James Slagle <jslagle>
Status:	CLOSED WONTFIX	QA Contact:	Arik Chernetsky <achernet>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0 (Liberty)	CC:	mburns, mcornea, rhel-osp-director-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-01 02:20:31 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:

Description Eduard Barrera 2016-07-07 11:42:29 UTC

Description of problem:


When configuring the undercloud the pre configured network bond options for the provisioning network are overwritten. I expect the existing bond options to be carried through by the installer.

The following options are removed from the config causing the bond to fail:

BONDING_MASTER=yes
BONDING_OPTS="mode=active-backup"

This leaves the vswitch in the following state:

[stack@undercloud1 ~]$ sudo ovs-vsctl show
70d28009-f5f5-4470-a266-0e22b7db483f
    Bridge br-ctlplane
        Port br-ctlplane
            Interface br-ctlplane
                type: internal
        Port "bond1"
            Interface "bond1"
                error: "could not open network device bond1 (No such device)"
        Port phy-br-ctlplane
            Interface phy-br-ctlplane
                type: patch
                options: {peer=int-br-ctlplane}
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ctlplane
            Interface int-br-ctlplane
                type: patch
                options: {peer=phy-br-ctlplane}
        Port "tap59ae9ba0-68"
            tag: 1
            Interface "tap59ae9ba0-68"
                type: internal
    ovs_version: "2.4.0"

Adding the options back in and running:

ifup bond1

fixes the issue.

Problem appears during the undercloud installation



Version-Release number of selected component (if applicable):
OSP 8

How reproducible:
always

Steps to Reproduce:
1. starting with a server with bonding configured
2. install the undercloud
3.

Actual results:

The following options are removed from the config causing the bond to fail:

BONDING_MASTER=yes
BONDING_OPTS="mode=active-backup"

removed options break bonding when restarting the network

Expected results:
Options not removed