yahoo-eng-team team mailing list archive

[Artom Lifshitz <1887751@xxxxxxxxxxxxxxxxxx>]

> when/how Nova decides that a compute node is really down there.

The compute services update their status in the database every
`report_interval` seconds [1]. If a service doesn't report after
`service_down_time`, it's considered down.

So if a compute service goes down, it'll be at most `service_down_time`
seconds before it'll be reported as such.

I hope that answers your question, I'm going aggressively but without
prejudice to close this as Invlaid, feel free to set it to New again for
any further clarification (or chat to us on IRC :)

[1] https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.report_interval
[2] https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.service_down_time


** Changed in: nova
       Status: New => Invalid

-- 
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/1887751

Title:
  Disabling an unreachable Node raises StackTrace

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Im getting an 504 return-code if I try to disable an unreachable, but
  still as active marked compute node. This is f.e. an issue if masakari
  tries to disable the agent after impi fenced the hardware.

  Steps to reproduce:

  * force poweroff of phy. node (f.e. poweroff -f)
  * use api to disable the nova-compute agent

  Expected:

    Dont know if this an expected behavior (so masakari should handle
  this) or is this a bug?

  Actual result:

    The API-Request returns a 504
    Logs: http://paste.openstack.org/show/Vm2KQvxAJI2bd3S3iEUR/

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