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.
Cause:
Regression caused by a fix for bug 1044122.
Consequence:
Replies to requests, e.g., those initiated by luci, were missing
the expected information, such as the status of selected daemons.
As a result, luci or ccs could make false claims about the cluster,
such as the daemon status, or about particular management tasks.
Fix:
Replies to clients' requests are composed correctly again.
Result:
Users will not get confused or misinformed when managing clusters.
DescriptionJan Pokorný [poki]
2015-01-30 19:06:25 UTC
It has been discovered that ricci modules built from ricci.srpm
(ricci-mod{service, rpm, log, storage, virt}) are not able to
return their output variables (in a sense of remote procedure call)
due to a bug in common/Module.cpp.
This results, for instance, in inability to examine status of clustering
daemon (running/stopped).
Note that core manipulations with cluster(s) are not affected as
modcluster (ricci module dedicated to core cluster.conf handling)
is built from clustermon.srpm that hasn't been patched in this way
([bug 1044122]) is irrelevant there.
Comment 3Jan Pokorný [poki]
2015-03-05 14:39:47 UTC
Comment 5Jan Pokorný [poki]
2015-03-05 16:26:39 UTC
Created attachment 998457[details]
Helper file to test the bugfix
# /usr/libexec/ricci-modservice <test-bz1187745
BEFORE:
<?xml version="1.0"?>
<response API_version="1.0" sequence="">
<function_response function_name="query"/>
</response>
AFTER (example):
<?xml version="1.0"?>
<response API_version="1.0" sequence="">
<function_response function_name="query">
<var mutable="false" name="result" type="list_xml">
<service description="" enabled="false" name="ricci" running="false"/>
<service description="" enabled="false" name="modclusterd" running="false"/>
<service description="" enabled="false" name="cman" running="false"/>
<service description="" enabled="false" name="rgmanager" running="false"/>
</var>
<var mutable="false" name="success" type="boolean" value="true"/>
</function_response>
</response>
Please re-test [bug 1044122] as well -- it is important that no temporary
batch in queue is not crippled in a way similar to BEFORE vs. AFTER
(i.e., no subtree is suddently missing).
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, 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://rhn.redhat.com/errata/RHBA-2015-1405.html
It has been discovered that ricci modules built from ricci.srpm (ricci-mod{service, rpm, log, storage, virt}) are not able to return their output variables (in a sense of remote procedure call) due to a bug in common/Module.cpp. This results, for instance, in inability to examine status of clustering daemon (running/stopped). Note that core manipulations with cluster(s) are not affected as modcluster (ricci module dedicated to core cluster.conf handling) is built from clustermon.srpm that hasn't been patched in this way ([bug 1044122]) is irrelevant there.