Ask Your Question
0

Got error on bring up vm on compute node

asked 2014-08-13 04:47:14 -0500

srinivasulu gravatar image

updated 2014-08-13 04:54:25 -0500

I have setup one controller and one compute node the following are details

              $more /etc/hosts
                    #compute1
                    192.168.191.82  controller
                    #compute1
                    192.168.191.18  compute1

$nova-manage service list ( on controller)

nova-cert        tsrinivasulu-308                     internal         enabled    :-)   2014-08-13 09:39:09
nova-consoleauth tsrinivasulu-308                     internal         enabled    :-)   2014-08-13 09:39:10
nova-scheduler   tsrinivasulu-308                     internal         enabled    :-)   2014-08-13 09:39:10
nova-conductor   tsrinivasulu-308                     internal         enabled    :-)   2014-08-13 09:39:09
nova-network     tsrinivasulu-308                     internal         enabled    :-)   2014-08-13 09:39:09
                 nova-compute     thunder-auto1.                      nova             enabled    :-)   2014-08-13 09:39:11

          Network is

nova net-list

       | 63a013ad-9474-430f-b1b9-b271b46eb50f | demo-net | 192.168.190.200/29 |

i started a vm on compute node, its shows status as spawning for long time, so i went through the log file in compute node. $tail /var/log/nova/compute.log

                  LOG FILE

     2014-08-13 14:58:06.594 16136 INFO oslo.messaging._drivers.impl_qpid [-] Connected to AMQP server on controller:5672
     2014-08-13 14:58:16.264 16136 WARNING nova.virt.disk.vfs.guestfs [req-287c595c-0a28-4f9e-adc0-f0769eb287ed 724582e87cad40f8aacfc19b0a5fdba7 0a0b65f3b90742f1b1f8695508e0145a] Failed to close augeas            aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas
      2014-08-13 15:05:10.032 16136 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
          2014-08-13 15:05:12.156 16136 WARNING nova.compute.manager [-] Found 1 in the database and 0 on the   hypervisor.

how to solve this , any idea

I appreciate your time ..

edit retag flag offensive close merge delete

Comments

Do you have any ERROR (not a WARNING) in your log file? have a look at this other question...

Antonio G. gravatar imageAntonio G. ( 2014-08-13 05:05:21 -0500 )edit

What is log when spawning is done ? That is really important

dbaxps gravatar imagedbaxps ( 2014-08-13 05:05:35 -0500 )edit

its still in spawning state for last 1hour .. no errors except above warnings

srinivasulu gravatar imagesrinivasulu ( 2014-08-13 05:09:59 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-08-13 06:00:29 -0500

dbaxps gravatar image

Issue "DELETE VM". Reboot system and try one more time.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-08-13 04:47:14 -0500

Seen: 1,431 times

Last updated: Aug 13 '14