Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMarkéta Smazová
2022-01-25 15:44:58 UTC
+++ 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
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