Open Stack

Hi guys,

Sorry for the late post.

I've successfully been able to ssh into the load balancer instance.
However, i'm still getting the timeout error and the stack is failing.

here's the content of my heat-provision.log file:
http://pastebin.com/bmjwSypP

Can you tell me if there's anything wrong?

FYI : I'm using devstack on ubuntu 12.04 64 bit.


On Tue, Mar 26, 2013 at 2:44 AM, Steven Dake <sdake at redhat.com> wrote:

>  On 03/24/2013 10:50 PM, Skanda Nag wrote:
>
> Hi Angus,
> Thanks for replying. I'll try this and i'll post back if i encounter with
> any problem.
>
>  Thanks :)
>
>
> Skanda,
>
> A problem folks have had in the past is their Nova networking or Quantum
> networking was not functioning properly in devstack.  Heat requires a
> functional network.  This can be verified by logging into the vm and
> retrieving a file from the network.
>
> Regards
> -steve
>
>
>
>  On Mon, Mar 25, 2013 at 6:14 AM, Angus Salkeld <asalkeld at redhat.com>wrote:
>
>>  On 24/03/13 14:17 +0530, Skanda Nag wrote:
>>
>>> I've tried to create a stack using the
>>> AutoScalingMultiAZSample.template file. The LoadBalancing instance
>>> boots up normally. The actual instance which has to start continuously
>>> waits for resource and then dies.
>>>
>>> 013-03-22 11:26:29.718 10817 DEBUG
>>> heat.engine.resources.wait_condition [-] Polling for WaitCondition
>>> completion, sleeping for 6 seconds, timeout 600 handle_create
>>> /opt/stack/heat/heat/engine/resources/wait_condition.py:258
>>>
>>> The load balancer instance starts up, then uses a wait condition.
>>> however, i'm not able to ssh or ping into the load balancer instance.
>>>
>>> Any tips on how i can get this to work? Thanks.
>>>
>>
>>  Hi
>>
>> This works for me, but only after _really_ making sure my repos were
>> uptodate (esp. the python clients).
>>
>> I rm -rf python-*clients and ran ./stack.sh again.
>>
>> In the heat-engine logs you should see an rpc method "metadata_update"
>> that comes from the api, this is what tells the engine that the vm is
>> ready to progess (the vm posts a wait condition to the api when it is
>> finished or config failed). A common problem is when the vm can't
>> communicate from the vm to the host, to check this ssh into the
>> vm (something like "ssh ec2-user at 10.0.0.2") and check to see if
>> you can communicate with the host. Whilst you are there check
>> the logs and see what is running.
>> -Angus
>>
>>
>>
>>> Regards.
>>>
>>
>>  _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> _______________________________________________
> OpenStack-dev mailing listOpenStack-dev at lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130402/f392e103/attachment.html>