Restarting of machine solved the problem... :/
Thanks li zheming for quick response... :)
Regards,
Varun
On Mon, Jan 20, 2014 at 6:15 PM, li zheming wrote:
> hi
> but I don't kown your environment.
> I only give you some info:
> 1. check your nova service is start-up
> 2 .check rpc is OK.
Hi,
I ran into this problem again... :(
Tried allocating more resources but that did not work.
I am pasting my log file contents below.
*ubuntu8gb@ubuntu8gb:/opt/stack/tempest$ cd /opt/stack/nova &&
/usr/local/bin/nov a-novncproxy --config-file /etc/nova/nova.conf --web
/opt/stack/noVNC |
Thank you sooo much everyone for the help and suggestions. The problem was
due to the resource allocation.
It is fixed now.
Thanks again!!!
Regards,
Varun
On Tue, Dec 31, 2013 at 12:05 PM, andrews...@gmail.com wrote:
> Usually when I have seen this the flavor was requiring more resources then
Usually when I have seen this the flavor was requiring more resources then
any of the nova nodes could support.
What is flavor 2 as far as resources go? And do you have enough allotted
for them?
Ben
On Dec 31, 2013 12:35 AM, "varun bhatnagar" wrote:
> Hi,
>
> I am new to Openstack. With lots of
Can you look at your log files under screen ? Scheduler and compute logs
must be able give you more information on why instance launch is failing.
-Dheeru
@Community Service
On Tue, Dec 31, 2013 at 11:00 AM, varun bhatnagar wrote:
> Hi,
>
> I am new to Openstack. With lots of difficulties I was
Hello,
Check services nova-scheduler and compute are running. Nova-compute service
should send update to nova-scheduler , which i hope is not doing . You can
check the service logs in /opt/stack/logs according to your localrc file.
Regards,
Ritesh
On Tue, Dec 31, 2013 at 11:00 AM, varun bhatna