Hi,
Output from the controller node:
root@aopcach:~# ifconfig
eth0 Link encap:Ethernet HWaddr 1c:c1:de:65:6f:ee
inet addr:158.109.65.21 Bcast:158.109.79.255 Mask:255.255.240.0
inet6 addr: fe80::1ec1:deff:fe65:6fee/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:111595 errors:0 dropped:0 overruns:0 frame:0
TX packets:10941 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18253579 (17.4 MiB) TX bytes:1747833 (1.6 MiB)
Interrupt:19 Memory:f3000000-f3020000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:45623 errors:0 dropped:0 overruns:0 frame:0
TX packets:45623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9862970 (9.4 MiB) TX bytes:9862970 (9.4 MiB)
root@aopcach:~# ps aux | grep dnsmasq
root 6355 0.0 0.0 7828 880 pts/0 S+ 19:23 0:00 grep dnsmasq
output from the compute node:
root@aopcso1:~# ifconfig
br100 Link encap:Ethernet HWaddr 38:60:77:0d:31:87
inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::3a60:77ff:fe0d:3187/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:689504 errors:0 dropped:4251 overruns:0 frame:0
TX packets:76508 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:89086934 (84.9 MiB) TX bytes:22405496 (21.3 MiB)
eth0 Link encap:Ethernet HWaddr 38:60:77:0d:31:87
inet6 addr: fe80::3a60:77ff:fe0d:3187/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:16329913 errors:0 dropped:0 overruns:0 frame:0
TX packets:927591 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2596968421 (2.4 GiB) TX bytes:448796862 (428.0 MiB)
Interrupt:20 Memory:f7100000-f7120000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:313717 errors:0 dropped:0 overruns:0 frame:0
TX packets:313717 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16434128 (15.6 MiB) TX bytes:16434128 (15.6 MiB)
root@aopcso1:~# ps aux | grep dnsmasq
nobody 12485 0.0 0.0 25124 1104 ? S 12:05 0:00
/usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file=
--domain='novalocal' --pid-file=/var/lib/nova/networks/nova-br100.pid
--listen-address=192.168.100.1 --except-interface=lo
--dhcp-range=set:private,192.168.100.2,static,255.255.255.0,120s
--dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf
--dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 12486 0.0 0.0 25124 472 ? S 12:05 0:00
/usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file=
--domain='novalocal' --pid-file=/var/lib/nova/networks/nova-br100.pid
--listen-address=192.168.100.1 --except-interface=lo
--dhcp-range=set:private,192.168.100.2,static,255.255.255.0,120s
--dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf
--dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 32616 0.0 0.0 7848 876 pts/0 S+ 19:27 0:00 grep dnsmasq
To: arin...@live.com
CC: openstack@lists.launchpad.net
Subject: RE: [Openstack] problem with metadata and ping
From: jsbry...@us.ibm.com
Date: Wed, 24 Apr 2013 11:26:23 -0500
Can you provided the output of 'ifconfig'
on the hosting node? Also 'ps aux | grep dnsmasq' .
Jay S. Bryant
Linux Developer -
OpenStack Enterprise Edition
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail: jsbry...@us.ibm.com
--------------------------------------------------------------------
All the world's a stage and most of us are desperately unrehearsed.
-- Sean
O'Casey
--------------------------------------------------------------------
From:
Arindam Choudhury <arin...@live.com>
To:
Jay S Bryant/Rochester/IBM@IBMUS,
openstack <openstack@lists.launchpad.net>,
Date:
04/24/2013 11:16 AM
Subject:
RE: [Openstack]
problem with metadata and ping
Hi,
So I added that rule:
iptables -I INPUT -i tap+ -p udp --dport 67:68 --sport 67:68 -j ACCEPT
but still the same problem.
There is another thing:
# nova-manage service list
Binary Host
Zone Status
State Updated_At
nova-network aopcach
internal
enabled :-) 2013-04-24
16:07:37
nova-cert aopcach
internal
enabled :-) 2013-04-24
16:07:36
nova-conductor aopcach
internal
enabled :-) 2013-04-24
16:07:36
nova-consoleauth aopcach
internal
enabled :-) 2013-04-24 16:07:36
nova-scheduler aopcach
internal
enabled :-) 2013-04-24
16:07:36
nova-network aopcso1
internal
enabled :-) 2013-04-24
16:07:36
nova-compute aopcso1
nova
enabled :-) 2013-04-24
16:07:37
shows all the host and services. But in dashboard it only shows the services
running in aopcach.
screenshot: http://imgur.com/ED9nbxU
To: arin...@live.com
CC: openstack@lists.launchpad.net
Subject: RE: [Openstack] problem with metadata and ping
From: jsbry...@us.ibm.com
Date: Wed, 24 Apr 2013 10:55:12 -0500
Arindam,
Ooops, I had a typo. The command should have been: iptables
-I input -i tap+ -p udp -dport 67:68 --sport 67:68 -j ACCEPT
You need the iptables configuration on the system where dnsmasq is running.
It shouldn't be necessary in the compute nodes that are being booted.
Jay S. Bryant
Linux Developer -
OpenStack Enterprise Edition
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail: jsbry...@us.ibm.com
--------------------------------------------------------------------
All the world's a stage and most of us are desperately unrehearsed.
-- Sean
O'Casey
--------------------------------------------------------------------
From: Arindam
Choudhury <arin...@live.com>
To: Jay
S Bryant/Rochester/IBM@IBMUS, openstack <openstack@lists.launchpad.net>,
Date: 04/24/2013
10:47 AM
Subject: RE:
[Openstack] problem with metadata and ping
Hi,
Thanks for your reply.
The dnsmasq is running properly.
when I tried to run iptables -I input
-i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT
it says,
# iptables -I input -i tap+ -p udp 67:68 --sport 67:68 -j ACCEPT
Bad argument `67:68'
Do I have to do this iptables configuration in controller or in compute
nodes also.
To: arin...@live.com
Subject: Re: [Openstack] problem with metadata and ping
From: jsbry...@us.ibm.com
Date: Wed, 24 Apr 2013 10:17:41 -0500
Arindam,
I saw a similar problem with quantum. If you have iptables running
on the hosting system you may need to update the rules to allow the DHCP
Discover packet through: iptables -I input -i tap+ -p udp 67:68 --sport
67:68 -j ACCEPT
Also ensure that dnsmasq is running properly.
Jay S. Bryant
Linux Developer -
OpenStack Enterprise Edition
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail: jsbry...@us.ibm.com
--------------------------------------------------------------------
All the world's a stage and most of us are desperately unrehearsed.
-- Sean O'Casey
--------------------------------------------------------------------
From: Arindam
Choudhury <arin...@live.com>
To: openstack
<openstack@lists.launchpad.net>,
Date: 04/24/2013
10:12 AM
Subject: Re:
[Openstack] problem with metadata and ping
Sent by: "Openstack"
<openstack-bounces+jsbryant=us.ibm....@lists.launchpad.net>
hi,
I was misled by this:
[(keystone_user)]$ nova list
+--------------------------------------+--------+--------+-----------------------+
| ID
| Name | Status
| Networks |
+--------------------------------------+--------+--------+-----------------------+
| 122ceb44-0b2d-442f-bb4b-c5a8cdbcb757 | cirros | ACTIVE | private=192.168.100.2
|
+--------------------------------------+--------+--------+-----------------------+
This is a nova-network problem.
From: arin...@live.com
To: openstack@lists.launchpad.net
Date: Wed, 24 Apr 2013 16:12:47 +0200
Subject: [Openstack] problem with metadata and ping
Hi,
I having problem with metadata service. I am using nova-network. The console
log says:
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40network failed
cloudsetup: checking http://169.254.169.254/20090404/metadata/instanceid
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloudsetup: failed 1/30: up 10.06. request failed.
the whole console log is here: https://gist.github.com/arindamchoudhury/5452385
my nova.conf is here: https://gist.github.com/arindamchoudhury/5452410
[(keystone_user)]$ nova network-list
+----+---------+------------------+
| ID | Label | Cidr |
+----+---------+------------------+
| 1 | private | 192.168.100.0/24 |
+----+---------+------------------+
[(keystone_user)]$ nova secgroup-list
+---------+-------------+
| Name | Description |
+---------+-------------+
| default | default |
+---------+-------------+
[(keystone_user)]$ nova secgroup-list-rules default
+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range | Source Group |
+-------------+-----------+---------+-----------+--------------+
| icmp | -1 | -1
| 0.0.0.0/0 |
|
| tcp | 22 | 22
| 0.0.0.0/0 |
|
+-------------+-----------+---------+-----------+--------------+
_______________________________________________ Mailing list:
https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net Unsubscribe :
https://launchpad.net/~openstack
More help :
https://help.launchpad.net/ListHelp_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
<<inline: ATT00001>>
<<inline: ATT00002>>
<<inline: ATT00003>>
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
