+++ This bug was initially created as a clone of Bug #2045096 +++ Description of problem: Pacemaker is unable to show metadata for "service" agents with "@" and "." in the name. Version-Release number of selected component (if applicable): pacemaker-2.1.2-2.el9 How reproducible: Always Steps to Reproduce: 1. List "service" agents that have "@" and "." in the name: # crm_resource --list-agents service | grep -E "@.\.*" systemd-journald-varlink@.socket systemd-journald@.socket 2. Try to show metadata: # crm_resource --show-metadata service:systemd-journald-varlink@.socket crm_resource: Metadata query for service:systemd-journald-varlink@.socket failed: No such device or address Error performing operation: No such object Actual results: Unable to show metadata. Expected results: Metadata are displayed. Additional info: # crm_resource --show-metadata service:systemd-journald-varlink@.socket -VVVVVV (set_crm_log_level) trace: New log level: 8 (crm_log_args) notice: Invoked: crm_resource --show-metadata service:systemd-journald-varlink@.socket -VVVVVV (mainloop_add_fd) trace: Added connection 1 for dbus[0x55f6bf275a20].3 (add_dbus_watch) trace: Added DBus watch for file descriptor 3 (mainloop_add_fd) trace: Added connection 2 for dbus[0x55f6bf276010].3 (add_dbus_watch) trace: Added DBus watch for file descriptor 3 (update_dispatch_status) trace: DBus connection has messages available for dispatch (systemd_new_method) trace: Calling: LoadUnit on org.freedesktop.systemd1.Manager (add_dbus_timer) trace: Added 25000ms DBus timer (remove_dbus_timer) trace: Removing 25000ms DBus timer (pcmk_dbus_find_error) trace: DBus reply indicated error 'org.freedesktop.DBus.Error.InvalidArgs' (Unit name systemd-journald-varlink@.socket is missing the instance name.) (pcmk_dbus_find_error) trace: DBus reply indicated error 'org.freedesktop.DBus.Error.InvalidArgs' (Unit name systemd-journald-varlink@.socket is missing the instance name.) (expand_resource_class) info: Assuming resource class lsb for agent systemd-journald-varlink@.socket for systemd-journald-varlink@.socket (services__get_lsb_metadata) trace: Looking into /etc/rc.d/init.d/systemd-journald-varlink@.socket (services_action_sync) trace: > systemd-journald-varlink@.socket_meta-data_0: /etc/rc.d/init.d/systemd-journald-varlink@.socket = 193 (lrmd_api_get_metadata_params) error: Failed to retrieve meta-data for service:(null):systemd-journald-varlink@.socket (lrmd_api_disconnect) info: Disconnecting IPC local executor connection crm_resource: Metadata query for service:systemd-journald-varlink@.socket failed: No such device or address Error performing operation: No such object (mainloop_destroy_signal_entry) trace: Destroying signal 0 (mainloop_destroy_signal_entry) trace: Destroying signal 1 [...] (mainloop_destroy_signal_entry) trace: Destroying signal 63 (mainloop_destroy_signal_entry) trace: Destroying signal 64 (crm_xml_cleanup) info: Cleaning up memory from libxml2 (crm_exit) info: Exiting crm_resource | with status 105
Fixed upstream as of commit 13d00a74
after fix ---------- [root@virt-527 ~]# rpm -q pacemaker pacemaker-2.1.3-2.el9.x86_64 [root@virt-527 ~]# crm_resource --list-agents service | grep -E "@.\.*" systemd-journald-varlink@.socket systemd-journald@.socket [root@virt-527 ~]# crm_resource --show-metadata service:systemd-journald-varlink@.socket <?xml version="1.0"?> <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd"> <resource-agent name="systemd-journald-varlink@.socket" version="0.1"> <version>1.1</version> <longdesc lang="en"> Journal Varlink Socket for Namespace pacemaker </longdesc> <shortdesc lang="en">systemd unit file for systemd-journald-varlink@.socket</shortdesc> <parameters/> <actions> <action name="start" timeout="100" /> <action name="stop" timeout="100" /> <action name="status" timeout="100" /> <action name="monitor" timeout="100" interval="60"/> <action name="meta-data" timeout="5" /> </actions> <special tag="systemd"/> </resource-agent> verified in pacemaker-2.1.3-2.el9
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (pacemaker bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:7937