[ClusterLabs Developers] OCF_RESKEY_CRM_meta_notify_inactive_uname never set ?

Jehan-Guillaume de Rorthais jgdr at dalibo.com
Fri Jan 20 09:16:20 EST 2017

Hi all,

While working on a patch in regard with the recent fix for
OCF_RESKEY_CRM_meta_notify_active_*  in 1.1.16, I found another strange
behavior with the "notify_inactive_uname" variable: it seems it just never
exists whatever I do. It is not even empty, just not existing. 

I did multiple tests with a node hosting 0 resources, a node in standby, etc.
Each time triggering some cluster action while the node was already hosting no

Note that "notify_inactive_resource" do exists, either empty or filled with
stopped resources.

While grep'ing in my debug files, I find 29 "notify_inactive_resource", 0

  # cat test-148492* | grep inactive | sort | uniq -c
     29 OCF_RESKEY_CRM_meta_notify_inactive_resource = ''pgsqld:2''

Shouldn't it at least exists? Even with an empty value as other notify variables? 

According to Pacemaker documentation, "notify_*_resource" and "notify_*_uname"
come in pairs, so I guess if a resource is listed in "notify_inactive_resource"
it should have a corresponding entry in "notify_inactive_uname", isn't it?

Thank you for your help!

Jehan-Guillaume de Rorthais

More information about the Developers mailing list