yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

OK it looks like this is your problem, OSA disables versioned
notifications by default:

https://github.com/openstack/openstack-ansible-
os_nova/blob/7d4b4ef3700d678c30435a90a54742a18d0f7941/defaults/main.yml#L26

https://github.com/openstack/openstack-ansible-
os_nova/blob/7d4b4ef3700d678c30435a90a54742a18d0f7941/templates/nova.conf.j2#L167

So you have to fix your OSA configuration.

** Changed in: nova
       Status: Incomplete => 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/1831226

Title:
  nova service related versioned notifications not getting generated

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I am using Openstack-Ansible queens version on my platform and trying
  to check the versioned notifications generated by nova service. I have
  verified the flavor and instance related notifications but failed to
  generated service.update notifications. I am trying to generate
  service related notifications by putting nova-compute service up/down
  using the systemctl command on the compute node. When this command is
  issued, after few seconds nova service-status shows the status of that
  compute node as "up"/"down" without any notification generated in the
  system.

  Is service.update notification not supported or my method to test it
  is wrong or some other configuration changes are required before
  testing it.

  My objective is to generate event in following scenarios:
   - compute agent is down
   - compute node is down
  Since both the above scenarios are getting detected by nova as nova service-status changes for that specific compute node, how could I generate an event/notifications for the same? 

  Regards,
  Arvind.

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