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.
Comment 2Jan Pokorný [poki]
2013-11-07 16:52:12 UTC
NB: there is another discrepancy in that the node joining the cluster
(after leaving it, i.e., after cluster services being stopped there)
is not checked for configuration version, which may be different
from what the cluster uses ... it will likely be synced upon config
modification, but expected is that it should be got right immediately
so that the complete cluster can work properly even if "stopped"
node hadn't communicated with luci for some time (and hence has
a stale configuration)
Comment 3Jan Pokorný [poki]
2013-11-07 17:12:50 UTC
NB2: another discrepancy seems to be that when a node is made a non-member
while still associated (leave cluster), normally the modifications
are propagated; however if you delete cluster.conf manually,
modifications are no longer propagated, which may be either
intentional (cannot see why, though) or a bug
(unlike on active cluster member, where cluster.conf should rather
be present all the time [rgmanager, fenced, ...], it seems perfectly
OK to temporarily remove cluster.conf on such inactived node)
Comment 4Jan Pokorný [poki]
2013-11-07 17:17:28 UTC
Comment 5RHEL Program Management
2013-11-10 22:44:58 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.