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.
Bug 896628 - [RFE] Implement configuration syncing over all nodes [rhel6]
Summary: [RFE] Implement configuration syncing over all nodes [rhel6]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 1025054 1092720
TreeView+ depends on / blocked
 
Reported: 2013-01-17 16:17 UTC by Radek Steiger
Modified: 2014-10-14 07:21 UTC (History)
3 users (show)

Fixed In Version: pcs-0.9.123-6.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1092720 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:21:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1526 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2014-10-14 01:22:04 UTC

Description Radek Steiger 2013-01-17 16:17:28 UTC 
Description of problem:

PCS on RHEL6 is able to generate a cluster.conf to get pacemaker work with cman, however it is not able to sync the configuration to all other nodes.

One way to do this would be to just invoking ccs_sync, this will however require to have ccs authenticated against other nodes' ricci daemon.
Comment 5 Chris Feist 2014-06-11 21:56:43 UTC 
With pcsd support in RHEL6, this now works....

Two nodes, bid-05, bid-06 (authentication is already done)...


[root@bid-05 pcs]# pcs cluster setup --name testcluster bid-05 bid-06 --start
bid-05: Updated cluster.conf...
bid-06: Updated cluster.conf...
Starting cluster on nodes: bid-05, bid-06...
bid-05: Starting Cluster...
bid-06: Starting Cluster...
...
Comment 8 Chris Feist 2014-08-07 22:57:27 UTC 
Should now be working:

[root@bid-05 ~]# rpm -q pcs
pcs-0.9.123-6.el6.x86_64
[root@bid-05 ~]# pcs cluster sync
bid-05: Updated cluster.conf...
bid-06: Updated cluster.conf...
m2: Updated cluster.conf...


[root@bid-06 ~]# grep uidgid /etc/cluster/cluster.conf
[root@bid-06 ~]# 

[root@bid-05 ~]# pcs cluster uidgid add uid=root
bid-05: Updated cluster.conf...
bid-06: Updated cluster.conf...
m2: Updated cluster.conf...


[root@bid-06 ~]# grep uidgid /etc/cluster/cluster.conf
  <uidgid gid="" uid="root"/>
Comment 10 Radek Steiger 2014-08-08 08:48:48 UTC 
For activating the new config it is also possible to use "cman_tool version -r -S" on any of the nodes.

VERIFIED in pcs-0.9.123-6.el6
Comment 12 errata-xmlrpc 2014-10-14 07:21:14 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2014-1526.html
Note You need to log in before you can comment on or make changes to this bug.