Bug 861516

Summary:	compute_nodes not being properly updated
Product:	Red Hat OpenStack	Reporter:	Dan Yocum <dyocum>
Component:	openstack-nova	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	Yaniv Kaul <ykaul>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0 (Essex)	CC:	jkt, ndipanov
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-04 18:14:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Yocum 2012-09-28 21:53:40 UTC

Description of problem:

One of my compute nodes is never receiving new VMs.  The running_vms field has not been updated since several VMs have failed on this node.  This should be updated regularly, not when VMs are started and terminated.

Version-Release number of selected component (if applicable):

Essex

How reproducible:

always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Nikola Dipanov 2013-01-04 18:14:26 UTC

I am not sure I understand what this bug is about. Resource updates (updatest to the  in Essex are done through notifications and the capacity_notifier needs to be set in the notification_driver flag in the nova.conf as it is not used by default.

Folsom does not have this problem as the resource tracker has been implemented at that time and the tables are updated correctly on every action.

I will close it as not a bug.

Comment 3 Dan Yocum 2013-01-04 23:54:10 UTC

What's the correct value to set notification_driver to?  The default is nova.notifier.no_op_notifier.

Thanks

Comment 4 Nikola Dipanov 2013-01-05 13:49:29 UTC

The value of the notification_driver if you want the compute_nodes db table to be updated should be:

nova.notifier.capacity_notifier

This makes sense only in Essex - this does not exist in Folsom anymore as the updates are done automatically.