-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
CentOS Stream 9
-
None
-
No
-
None
-
rhel-ha
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
x86_64
-
None
What were you trying to do that didn't work?
Hi.
I have a seemingly healthy 3-node cluster which constantly, periodically logs:
-> $ journalctl -lf -o cat -u pacemaker.service notice: Requesting local execution of notify operation for PGSQL on swir error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1164 : n_type != NULL error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1165 : n_task != NULL error: pcmk__notify_key: Triggered fatal assertion at actions.c:340 : op_type != NULL notice: Result of notify operation for PGSQL on swir: ok notice: Requesting local execution of notify operation for PGSQL on swir error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1164 : n_type != NULL error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1165 : n_task != NULL error: pcmk__notify_key: Triggered fatal assertion at actions.c:340 : op_type != NULL notice: Result of notify operation for PGSQL on swir: ok
-> $ journalctl -lf -o cat -u pacemaker.service notice: Requesting local execution of notify operation for PGSQL on whale error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1164 : n_type != NULL error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1165 : n_task != NULL error: pcmk__notify_key: Triggered fatal assertion at actions.c:340 : op_type != NULL notice: Result of notify operation for PGSQL on whale: ok notice: Requesting local execution of notify operation for PGSQL on whale error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1164 : n_type != NULL error: pcmk__create_history_xml: Triggered fatal assertion at pcmk_sched_actions.c:1165 : n_task != NULL error: pcmk__notify_key: Triggered fatal assertion at actions.c:340 : op_type != NULL notice: Result of notify operation for PGSQL on whale: ok
-> $ journalctl -lf -o cat -u pacemaker.service notice: State transition S_IDLE -> S_POLICY_ENGINE 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:340 : 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:340 : op_type != NULL notice: Calculated transition 836, saving inputs in /var/lib/pacemaker/pengine/pe-input-3212.bz2 notice: Initiating notify operation (null) on whale notice: Initiating notify operation (null) on swir notice: Transition 836 (Complete=2, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-3212.bz2): Complete notice: State transition S_TRANSITION_ENGINE -> S_IDLE
Something quite obvious I think to spot is - two nodes log virtually identically whereas third one differently.
I think it has something to do with some resource &| constraints for - that "third" node can be any node and then the remaining two become the "two" logging similarly - all depending on how where (whichever) resource(s) go - but I don't see any other (obvious) errors/issues with resources.
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
pacemaker-schemas-2.1.10-1.el9.noarch
pacemaker-libs-2.1.10-1.el9.x86_64
pacemaker-cluster-libs-2.1.10-1.el9.x86_64
pacemaker-cli-2.1.10-1.el9.x86_64
pacemaker-2.1.10-1.el9.x86_64
