openstack team mailing list archive

[Shashank Sahni <shredder12@xxxxxxxxxxxx>]

Hi,

Here are the network configuration parameters in my nova.conf

--network_manager = nova.network.manager.FlatManager
--flat_network_bridge=br100
--flat_injected=true
--flat_interface=eth0
--public_interface=eth0

Hence, I ran tcpdump with following three filters on the interfaces - eth0,
lo & br100.

ip host 169.254.169.254
port 8773
port 80

but, nothing was returned for around a minute. Do I need to use different
filters?

Thank you.

Regards,
Shashank Sahni

On Sun, Oct 2, 2011 at 11:31 PM, Jesse Andrews <anotherjesse@xxxxxxxxx>wrote:

> If the request isn't coming into the nova-api then I recommend
> checking the network path using tcpdump (or wireshark - there is a
> curses version).
>
> As you can see it tries 100 times to hit the metadata server so you
> should see traffic every couple seconds
>
>
> On Sat, Oct 1, 2011 at 1:59 PM, Shashank Sahni <shredder12@xxxxxxxxxxxx>
> wrote:
> > Hi everyone,
> > I'm working on a single node installation of openstack(for testing). I'm
> > using ubuntu uec images and am successfully able to boot them. But
> > unfortunately, I get the error
> > DataSourceEc2.py[WARNING]:   20:07:30 [17/100]: url error [[Errno 101]
> > Network is unreachable]
> > at the end of "euca-get-console-output". I believe that is the reason why
> > I'm not able to either ping or ssh into the instance.
> > There already exists a pre-routing rule to redirect all the communication
> > from 169.254.169.254:80 to nova-api:8773.
> > -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport
> 80 -j
> > DNAT --to-destination 10.2.4.135:8773
> > Any suggestions?
> > Regards,
> > Shashank Sahni
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
>