Ask Your Question
0

Nova Compute is not reporting actual available resource

asked 2014-06-11 07:39:43 -0500

S.Bharath gravatar image

Hi All,

It looks like my Compute node is giving wrong insufficient resources when creating an Instance, first time the nova resource tracker reports the correct stats but after running reclaiming and then it reports wrong resources, below is the log and finally the image creation fails "No space left on drive\n" I have quoted below where it says actual then reports wrong stats, any help?

2014-06-11 17:46:16.623 3312 AUDIT nova.service [-] Starting compute node (version 2014.1)
2014-06-11 17:46:16.654 3312 WARNING nova.virt.libvirt.driver [-] URI qemu:///system does not support events: internal error: could not initialize domain event timer

2014-06-11 17:46:16.841 3312 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources 2014-06-11 17:46:16.980 3312 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 6929 2014-06-11 17:46:16.981 3312 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 26 2014-06-11 17:46:16.981 3312 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 1

2014-06-11 17:46:17.015 3312 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute:compute
2014-06-11 17:46:17.044 3312 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on controller:5672
2014-06-11 17:46:59.776 3312 AUDIT nova.compute.manager [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Starting instance...
2014-06-11 17:46:59.908 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Attempting claim: memory 2048 MB, disk 20 GB, VCPUs 1
2014-06-11 17:46:59.908 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Total memory: 7953 MB, used: 1024.00 MB
2014-06-11 17:46:59.909 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] memory limit not specified, defaulting to unlimited
2014-06-11 17:46:59.909 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Total disk: 27 GB, used: 1.00 GB
2014-06-11 17:46:59.909 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] disk limit not specified, defaulting to unlimited
2014-06-11 17:46:59.910 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Total CPUs: 2 VCPUs, used: 1.00 VCPUs
2014-06-11 17:46:59.910 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] CPUs limit not specified, defaulting to unlimited
2014-06-11 17:46:59.910 3312 AUDIT nova.compute.claims [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Claim successful
2014-06-11 17:47:00.727 3312 INFO nova.virt.libvirt.driver [req-7832217e-4dcc-4203-a190-9e754419731c 256e48ab67964481ab90cf167fda76a5 73551d16e7544c48806c9b277ca0ad37] [instance: c4eafe05-dda5-4558-82f8-187d0324d7c7] Creating image

2014-06-11 17:47:15.052 3312 AUDIT nova.compute.resource_tracker [req-d8f727cd-173c-4370-a5a9-a9453e0ad5ec None None] Auditing locally available compute resources 2014-06-11 17:47:15.216 3312 AUDIT nova.compute.resource_tracker [req-d8f727cd-173c-4370-a5a9-a9453e0ad5ec None None] Free ram (MB): 4881 2014-06-11 17:47:15.217 3312 AUDIT nova.compute.resource_tracker [req-d8f727cd-173c-4370-a5a9-a9453e0ad5ec None None] Free disk (GB): 6 2014-06-11 17:47:15.217 3312 AUDIT nova.compute.resource_tracker [req-d8f727cd-173c-4370-a5a9-a9453e0ad5ec None None] Free VCPUS: 0

2014-06-11 17:47:15.250 3312 INFO nova.compute.resource_tracker [req-d8f727cd-173c-4370-a5a9-a9453e0ad5ec None None] Compute_service record updated for compute:compute
2014-06-11 17:47 ...
(more)
edit retag flag offensive close merge delete

Comments

according to this link, the resource tracker somewhere has to update available resources as available in the hypervisor layer which isn't being updated. http://docs.openstack.org/developer/n...

S.Bharath gravatar imageS.Bharath ( 2014-06-11 08:02:12 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-06-11 10:37:46 -0500

S.Bharath gravatar image

I just increased the disk space and tried, it started, not sure what provisioning it was doing and still required more than required allotment space for the instance.

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-06-11 07:39:43 -0500

Seen: 2,521 times

Last updated: Jun 11 '14