yahoo-eng-team team mailing list archive

[gordon chung <gordon.chung@xxxxxxxxxxxx>]

marking this as won't fix on ceilometer end. we removed the
nova_notifier as the plugin mechanism didn't play well with nova

** Changed in: ceilometer
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1221987

Title:
  compute node heartbeat out of sync causing scheduler to fail in
  devstack:  VMs fail to spawn

Status in OpenStack Telemetry (Ceilometer):
  Won't Fix
Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  I have now seen this several times in devstack-gate

  Occasionally instances will go into error state, and when checking the
  logs, I see the error is in nova-scheduler where the heartbeat is too
  old, which causes the scheduler to not schedule on that node.

  
  http://logs.openstack.org/97/45497/2/check/gate-tempest-devstack-vm-postgres-full/084442d/logs/screen-n-sch.txt.gz#_2013-09-07_00_06_14_880

  
  From logfile:

   DB_Driver.is_up last_heartbeat = 2013-09-07 00:04:47.516557 elapsed =
  87.363841 is_up /opt/stack/new/nova/nova/servicegroup/drivers/db.py:71

    (devstack-precise-hpcloud-az1-229926, devstack-precise-hpcloud-az1-229926) ram:5170 disk:210944 io_ops:5 instances:18 is disabled or has not been heard from in a while host_passes /opt/stack/new/nova/nova/scheduler/filters/compute_filter.py:44
   
    Filter ComputeFilter returned 0 host(s) get_filtered_objects /opt/stack/new/nova/nova/filters.py:85
  [instance: 415fb048-1d47-4fb8-8974-323529d8b1b5] Setting instance to ERROR state.
  20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1221987/+subscriptions