Bug 1010180

Summary: Physical interface is not bringed up
Product: [Fedora] Fedora Reporter: Pavel Zhukov <pzhukov>
Component: openvswitchAssignee: Flavio Leitner <fleitner>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: chrisw, fleitner, markmc, nobody, pzhukov, tgraf
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-02 13:57:58 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:
Attachments:
Description Flags
/etc/sysconfig/network-scripts/
none
journald output none

Description Pavel Zhukov 2013-09-20 07:22:46 UTC 
Description of problem:
I've installed and configured openvswitch (see attachments for full configs). 
cat /etc/sysconfig/network-scripts/ifcfg-p3p1  | grep 'ONBOOT\|TYPE\|obr0'
ONBOOT="yes"
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=obr0

the ovs bridge is up and all ports are added but p3p1 interface is down and bridge is not able to obtain ip address. 

NOTE: network service is in use (not NetworkManager).

Workaround: 
ifconfig p3p1 up
dhclient obr0

Version-Release number of selected component (if applicable):
openvswitch-1.11.0-1.fc19.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install ovs and configure one port
2. Reboot


Actual results:
Physical interface is down

Expected results:
Physical interface is up

Additional info:
Comment 1 Pavel Zhukov 2013-09-20 07:24:54 UTC 
Created attachment 800325 [details]
/etc/sysconfig/network-scripts/
Comment 2 Pavel Zhukov 2013-09-20 07:26:10 UTC 
Created attachment 800326 [details]
journald output
Comment 3 Flavio Leitner 2013-09-26 20:48:43 UTC 
The problem happens because the OVS bridge isn't configured properly.
You uploaded this:
$ cat ifcfg-obr0 
DEVICE=obr0
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=dhcp
HOTPLUG=no

But OVS Bridge doesn't use BOOTPROTO and requires OVSDHCPINTERFACES.

To enable DHCP on the bridge you need to use OVSBOOTPROTO instead of BOOTPROTO, and all the interfaces that can reach the DHCP server as a space separated list in OVSDHCPINTERFACES.

In your case, it would be like below:
DEVICE=obr0
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
HOTPLUG=no
OVSBOOTPROTO="dhcp"
OVSDHCPINTERFACES="p3p1"

The other file ifcfg-p3p1 looks good to me.
Could you see if fixing ifcfg-obr0 fixes the problem?

Thanks!
Comment 4 Flavio Leitner 2013-10-02 13:57:58 UTC 
Pavel,

I am going to close this bug since I think the problem is just a misconfiguration. If you think otherwise, feel free to reopen it.

Thanks
Comment 5 Pavel Zhukov 2013-10-02 15:00:35 UTC 
(In reply to Flavio Leitner from comment #4)
> Pavel,
> 
> I am going to close this bug since I think the problem is just a
> misconfiguration. If you think otherwise, feel free to reopen it.
> 
> Thanks

Sorry for the last response. 
I've checked the configuration right now. It works. 
Thank you!