[Rdo-list] F20 networking refuses to start on boot
Kashyap Chamarthy
kchamart at redhat.com
Fri Jan 10 23:13:36 UTC 2014
On 01/10/2014 05:35 PM, Lars Kellogg-Stedman wrote:
> On Fri, Jan 10, 2014 at 09:15:10AM -0500, Lars Kellogg-Stedman wrote:
>> I'm starting up another F20 system right now to see if this is a
>> general problem with OVS bridges or if there's something peculiar on
>> my install.
>
> So this appears to be a general problem with OVS bridges on F20. I've
> opened https://bugzilla.redhat.com/show_bug.cgi?id=1051593 against
> initscripts.
IIRC, I've noticed something like that among the various issues I was
trying to note down over the course of test days.
Thanks for chasing this down, Lars!
>
> If I start with the F20 cloud image and install OpenVswitch:
>
> yum install openvswitch
>
> And enable openvswitch:
>
> systemctl enable openvswtich
>
> And create a bridge device:
>
> ovs-vsctl add-br br0
>
> And add an interface configuration file that looks like this:
>
> DEVICE=br0
> DEVICETYPE=ovs
> TYPE=OVSBridge
> BOOTPROTO=static
> IPADDR=172.24.4.225
> NETMASK=255.255.255.240
> ONBOOT=yes
>
> And reboot, I end up with:
>
> # ip addr show dev br0
> 4: br0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
> link/ether ce:ac:68:75:a2:4d brd ff:ff:ff:ff:ff:ff
> inet6 fe80::e8ec:8aff:fe03:dd51/64 scope link
> valid_lft forever preferred_lft forever
>
> If I run:
>
> # ifdown br0
> # ifup br0
>
> I get what I expect:
>
> # ip addr show dev br0
> 5: br0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
> link/ether 0a:49:24:10:dc:4d brd ff:ff:ff:ff:ff:ff
> inet 172.24.4.225/28 brd 172.24.4.239 scope global br0
> valid_lft forever preferred_lft forever
> inet6 fe80::cc6c:9cff:fef1:d32a/64 scope link
> valid_lft forever preferred_lft forever
>
>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
--
/kashyap
More information about the dev
mailing list