[ClusterLabs] clone_op_key pcmk__notify_key - Triggered fatal assertion

[Ken Gaillot]

On Sat, 2024-02-17 at 13:39 +0100, lejeczek via Users wrote:
> Hi guys.
> 
> Everything seems to be working a ok yet pacemakers logs
> ...
>  error: clone_op_key: Triggered fatal assertion at
> pcmk_graph_producer.c:207 : (n_type != NULL) && (n_task != NULL)
>  error: pcmk__notify_key: Triggered fatal assertion at actions.c:187
> : op_type != NULL
>  error: clone_op_key: Triggered fatal assertion at
> pcmk_graph_producer.c:207 : (n_type != NULL) && (n_task != NULL)
>  error: pcmk__notify_key: Triggered fatal assertion at actions.c:187
> : op_type != NULL
> ...
>  error: pcmk__create_history_xml: Triggered fatal assertion at
> pcmk_sched_actions.c:1163 : n_type != NULL
>  error: pcmk__create_history_xml: Triggered fatal assertion at
> pcmk_sched_actions.c:1164 : n_task != NULL
>  error: pcmk__notify_key: Triggered fatal assertion at actions.c:187
> : op_type != NULL
> ...
> 
> Looks critical, is it it - would you know?
> many thanks, L.
> 

That's odd. This suggests the scheduler created a notify action without
adding all the necessary information, which would be a bug. Do you have
the scheduler input that causes these messages? 

Also, what version are you using, and how did you get it?
--
Ken Gaillot <kgaillot at redhat.com>