Suggest adding this to workaround the issue in end of sections 3.4 and 4.4

Bring up the bridges:
ifconfig br-int up
ifconfig br-tun up

Also add it in rc.local file to get the bridges UP during reboot:

sleep 15
ifconfig br-int up
ifconfig br-tun up

from openstack-grizzly-install-guide.

I rebooted the network and compute node but they didn't go down. Are you
sure about this ?
I will double check on my side !

2013/4/26 hrushig [email protected]

Suggest adding this to workaround the issue in end of sections 3.4 and 4.4

Bring up the bridges:
ifconfig br-int up
ifconfig br-tun up

Also add it in rc.local file to get the bridges UP during reboot:

sleep 15
ifconfig br-int up
ifconfig br-tun up

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-17099701
.

Best regards,

Bilel Msekni | IT Engineer
Mobile: +33 6 49 52 42 17

from openstack-grizzly-install-guide.

yes, specifically br-int and br-tun

Cheers ~hrushi

On Apr 27, 2013, at 12:32 AM, "SkiBLE" <[email protected]mailto:[email protected]> wrote:

I rebooted the network and compute node but they didn't go down. Are you
sure about this ?
I will double check on my side !

2013/4/26 hrushig <[email protected]mailto:[email protected]>

Suggest adding this to workaround the issue in end of sections 3.4 and 4.4

Bring up the bridges:
ifconfig br-int up
ifconfig br-tun up

Also add it in rc.local file to get the bridges UP during reboot:

sleep 15
ifconfig br-int up
ifconfig br-tun up

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-17099701
.

Best regards,

Bilel Msekni | IT Engineer
Mobile: +33 6 49 52 42 17

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-17112014.

from openstack-grizzly-install-guide.

You are right hrushig ! they go down after reboot.
I don't that's enough, router interface and even other tap devices are down.

Reboot of network node is not recommended to me.

regards,
Bilel

from openstack-grizzly-install-guide.

hi hrushig,

how you check the state of the bridge ? with the command "ifconfig" , right?
thanks

from openstack-grizzly-install-guide.

ip addr

From: claenjoy [mailto:[email protected]]
Sent: Thursday, May 16, 2013 12:53 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Cc: Gangur, Hrushikesh (HP Converged Cloud - R&D - Sunnyvale)
Subject: Re: [OpenStack-Grizzly-Install-Guide] Missing instructions on bringing up br-* interfaces on reboot (#38)

hi hrushig,

how you check the state of the bridge ? with the command "ifconfig" , right?
thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-18024886.

from openstack-grizzly-install-guide.

thanks , an other point is to bring up also the br-ex, in the network node , right ?

from openstack-grizzly-install-guide.

It is not needed as we are bringing up br-ex through interfaces file.

From: claenjoy [mailto:[email protected]]
Sent: Thursday, May 16, 2013 2:13 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Cc: Gangur, Hrushikesh (HP Converged Cloud - R&D - Sunnyvale)
Subject: Re: [OpenStack-Grizzly-Install-Guide] Missing instructions on bringing up br-* interfaces on reboot (#38)

thanks , an other point is to bring up also the br-ex, in the network node , right ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-18029514.

from openstack-grizzly-install-guide.

Not find the config interfaces file in the guide could you post here , please

from openstack-grizzly-install-guide.

I have in all bridge state UNKNOWN ?!?

adfter ifconfig br-int up / ifconfig br-ex up / ifconfig br-tun up

<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether e2:df:01:e8:16:4c brd ff:ff:ff:ff:ff:ff
inet6 fe80::e0df:1ff:fee8:164c/64 scope link
valid_lft forever preferred_lft forever

I have all of them in compute node and network node

from openstack-grizzly-install-guide.

That is expected behavior. It should not be showing as DOWN.

-------Network Node::interfaces-------------------------

The loopback network interface

auto lo
iface lo inet loopback

Openstack Management

auto eth0
iface eth0 inet static
address 10.10.10.52
netmask 255.255.255.0

VM Configuration

auto eth1
iface eth1 inet static
address 10.20.20.52
netmask 255.255.255.0

VM Internet Access

auto eth2
iface eth2 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off
down ifconfig $IFACE down

auto br-ex
iface br-ex inet static
address 192.168.100.52
netmask 255.255.255.0

-------- Network Node::rc.local--------------------------
sleep 15
ifconfig br-int up
ifconfig br-tun up
exit 0

-------Compute Node::interfaces-------------------------
interfaces

The loopback network interface

auto lo
iface lo inet loopback

OpenStack Management

auto eth0
iface eth0 inet static
address 10.10.10.53
netmask 255.255.255.0

VM Configuration

auto eth1
iface eth1 inet static
address 10.20.20.53
netmask 255.255.255.0

-------- Compute Node::rc.local--------------------------
sleep 15
ifconfig br-int up
ifconfig br-tun up
exit 0

From: claenjoy [mailto:[email protected]]
Sent: Friday, May 17, 2013 1:02 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Cc: Gangur, Hrushikesh (HP Converged Cloud - R&D - Sunnyvale)
Subject: Re: [OpenStack-Grizzly-Install-Guide] Missing instructions on bringing up br-* interfaces on reboot (#38)

I have in all bridge state UNKNOWN ?!?

adfter ifconfig br-int up / ifconfig br-ex up / ifconfig br-tun up

mtu 1500 qdisc noqueue state UNKNOWN
link/ether e2:df:01:e8:16:4c brd ff:ff:ff:ff:ff:ff
inet6 fe80::e0df:1ff:fee8:164c/64 scope link
valid_lft forever preferred_lft forever

I have all of them in compute node and network node

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/38#issuecomment-18083045.

from openstack-grizzly-install-guide.

Problem in Keystone Service restart
following errors coming
service openstack-keystone restart
Redirecting to /bin/systemctl restart openstack-keystone.service
Job for openstack-keystone.service failed. See 'systemctl status openstack-keystone.service' and 'journalctl -xn' for details.
[root@new-host-2 ~]# systemctl status openstack-keystone.service
openstack-keystone.service - OpenStack Identity Service (code-named Keystone)
Loaded: loaded (/usr/lib/systemd/system/openstack-keystone.service; disabled)
Active: failed (Result: start-limit) since Tue 2013-05-21 07:22:31 EDT; 12s ago
Process: 29206 ExecStart=/usr/bin/keystone-all --config-file /etc/keystone/keystone.conf (code=exited, status=1/FAILURE)

May 21 07:22:31 new-host-2.home systemd[1]: Failed to start OpenStack Identi....
May 21 07:22:31 new-host-2.home systemd[1]: Unit openstack-keystone.service ....
May 21 07:22:31 new-host-2.home systemd[1]: openstack-keystone.service holdo....
May 21 07:22:31 new-host-2.home systemd[1]: Stopping OpenStack Identity Serv....
May 21 07:22:31 new-host-2.home systemd[1]: Starting OpenStack Identity Serv....
May 21 07:22:31 new-host-2.home systemd[1]: openstack-keystone.service start....
May 21 07:22:31 new-host-2.home systemd[1]: Failed to start OpenStack Identi....
May 21 07:22:31 new-host-2.home systemd[1]: Unit openstack-keystone.service ....

from openstack-grizzly-install-guide.

@snavdeepgill
wrong place ! open a new issues

from openstack-grizzly-install-guide.

@hrushig
@mseknibilel

what about rest of the devices - router interface and even other tap devices are showing down after reboot. Do i need to perform something else to make these devices states as UP? Please confirm. much appreciated

from openstack-grizzly-install-guide.