8:15 a.m.
[I'm redirecting this to rdo-list for wider exposure.]
On Thu, Jan 09, 2014 at 10:22:36PM -0700, Pete Zaitcev wrote:
On Thu, 9 Jan 2014 15:40:13 -0500
Lars Kellogg-Stedman <lars(a)redhat.com> wrote:
> On Thu, Jan 09, 2014 at 01:34:54PM -0700, Pete Zaitcev wrote:
> > It feels like something simple enough, but... I installed RDO on F20
> > as a part of Test Day on Tuesday. Then I added a flat network to it,
> > and I found no better way to do it than to take the main Ethernet
> > out of the control of NetworkManager by adding NM_CONTROLLED=no to
> > ifcfg-br-ex and ifcfg-p4p1. Ever since, the box has no network on boot.
> > I have to log in on console and do "ifdown br-ex; ifup br-ex".
>
> Have you installed and activate the "network" service?
>
> chkconfig network on
>
> This is the legacy /etc/init.d/network script that brings up
> networking in the absence of NetworkManager.
I have done it and it makes no difference:
Actually, it looks like I'm experiencing the same issue with br-ex on
my F20 openstack install. Given an interface configuration file
/etc/sysconfig/network-scripts/ifcfg-br-ex that looks like this:
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=172.24.4.225
NETMASK=255.255.255.240
ONBOOT=yes
After I boot the interface looks like this:
br-ex: flags=67<UP,BROADCAST,RUNNING> mtu 1500
inet6 fe80::888c:81ff:febd:d8b8 prefixlen 64 scopeid 0x20<link>
ether 3a:69:08:00:0f:40 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Running ifdown/ifup as Pete describes correctly configures the
interface.
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.
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
10:35 a.m.
New subject: [Rdo-list] F20 networking refuses to start on boot
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.
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
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
12:14 p.m.
New subject: [Rdo-list] F20 networking refuses to start on boot
On Fri, 10 Jan 2014 11:35:05 -0500
Lars Kellogg-Stedman <lars(a)redhat.com> wrote:
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.
Thanks for taking care of bz.
I'm still open to the alternative, using NM, if anyone knows how
to do that.
-- Pete
12:07 p.m.
New subject: [Rdo-list] Neutron stops to work on F20 at certain point of time
At the beginning instances created could not be connected by ssh
and did not respond to ping. Then Neutron became unable to connect
to AMQP server. Server.log attached.
12:12 p.m.
New subject: [Rdo-list] Neutron stops to work on F20 at certain point of time 2
[root@openstack1 ~(keystone_admin)]# neutron net-list
Connection to neutron failed: Maximum attempts reached
[root@openstack1 ~(keystone_admin)]# service neutron-server status
Redirecting to /bin/systemctl status neutron-server.service
neutron-server.service - OpenStack Quantum Server
Loaded: loaded (/usr/lib/systemd/system/neutron-server.service; enabled)
Active: active (running) since Sat 2014-01-11 21:41:02 VOLT; 13min ago
Main PID: 1664 (neutron-server)
CGroup: /system.slice/neutron-server.service
└─1664 /usr/bin/python /usr/bin/neutron-server --config-file
/usr/share/neutron/neutron-dis...
Jan 11 21:44:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:44:36.106 1664
ERROR neut...ds
Jan 11 21:45:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:45:36.163 1664
ERROR neut...ds
Jan 11 21:46:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:46:36.223 1664
ERROR neut...ds
Jan 11 21:47:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:47:36.247 1664
ERROR neut...ds
Jan 11 21:48:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:48:36.306 1664
ERROR neut...ds
Jan 11 21:49:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:49:36.364 1664
ERROR neut...ds
Jan 11 21:50:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:50:36.410 1664
ERROR neut...ds
Jan 11 21:51:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:51:36.431 1664
ERROR neut...ds
Jan 11 21:52:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:52:36.491 1664
ERROR neut...ds
Jan 11 21:53:36 openstack1.localdomain neutron-server[1664]: 2014-01-11 21:53:36.550 1664
ERROR neut...ds
Hint: Some lines were ellipsized, use -l to show in full.
5:13 p.m.
New subject: [Rdo-list] F20 networking refuses to start on boot
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(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
--
/kashyap
3759
days inactive
3760
days old
5 comments
4 participants
participants (4)
-
Boris Derzhavets -
Kashyap Chamarthy -
Lars Kellogg-Stedman -
Pete Zaitcev