openstack team mailing list archive

["Vaze, Mandar" <Mandar.Vaze@xxxxxxxxxxx>]

Dan,
Bug you referred to specifically says "default" tenant - which is not the case for me.
I'm not using default tenant - I'm using  uuid of "demo" tenant created by stack.sh
BTW, stack.sh creates incorrect  entries in quantum/mélange DB,  it has tenant ID = "default" - This should be uuid of some valid tenant, not string "default"

FWIW, this setup (although seems incorrect) works with quantum+nova_ipam - not with quantum+mélange
i.e. With quantum+nova_ipam I can just create a VM and ssh to it.

-Mandar

From: Dan Wendlandt [mailto:dan@xxxxxxxxxx]
Sent: Wednesday, April 11, 2012 11:07 PM
To: Vaze, Mandar
Cc: Nicolas de BONFILS; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Instance can't reach dhcp or metadata


On Wed, Apr 11, 2012 at 5:24 AM, Vaze, Mandar <Mandar.Vaze@xxxxxxxxxxx<mailto:Mandar.Vaze@xxxxxxxxxxx>> wrote:
I have never been able to get to ssh to an instance with Quantum+mélange
https://lists.launchpad.net/openstack/msg09206.html

Looking at that thread, I suspect you may be hitting the same issue I mentioned above: https://bugs.launchpad.net/quantum/+bug/949234

If you try that fix and either do or don't have luck with it, please add a comment to the issue.

Dan



-Mandar

From: openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx<mailto:nttdata.com@xxxxxxxxxxxxxxxxxxx> [mailto:openstack-bounces+mandar.vaze<mailto:openstack-bounces%2Bmandar.vaze>=nttdata.com@xxxxxxxxxxxxxxxxxxx<mailto:nttdata.com@xxxxxxxxxxxxxxxxxxx>] On Behalf Of Nicolas de BONFILS
Sent: Wednesday, April 11, 2012 1:45 AM
To: Dan Wendlandt
Cc: openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Openstack] Instance can't reach dhcp or metadata

Hi,

I can't get the ssh connection,VNC doesn't respond and 10.0.0.1 go to localhost (ssh to server itself)

---
Nicolas

On Tue, Apr 10, 2012 at 21:42, Dan Wendlandt <dan@xxxxxxxxxx<mailto:dan@xxxxxxxxxx>> wrote:

On Tue, Apr 10, 2012 at 11:54 AM, Nicolas de BONFILS <ndebonfils@xxxxxxxxx<mailto:ndebonfils@xxxxxxxxx>> wrote:
Things starting to work !
When I boot boot cirros image with ip 10.0.0.1, I can ssh (even if it doesn't accept my password), but when I lauch tty-uec image (or other) with ip starting at 10.0.0.2, ssh tell "no route to host"

If it works on one image, but not another, this is probably an issue with the image itself.  The "no route to host" error is likely because the gateway interface 10.0.0.1 is arping for 10.0.0.2 and not getting a response.  Perhaps the image is not configured to use DCHP on the interface?  Or is not correctly launching?  I'd use VNC to login and check it out.

Dan


I sum up the actual conf

  *   br-int as bridge in OVS, no other conf (nothing in interfaces file), ifconfig show a 10.0.0.1 ip
  *   nova conf got public_interface=br-int / flat_network_bridge=br-int / flat_interface=eth0
  *   quantum manage the assignation successfully
Thanks
---
Nicolas

_______________________________________________
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com<http://www.nicira.com>
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~



______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com<http://www.nicira.com>
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~


______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding