Bug 1147989

Summary: cibadmin -u yields a Timer Expired error when run on a non-DC node
Product: Red Hat Enterprise Linux 7 Reporter: Radek Steiger <rsteiger>
Component: pacemakerAssignee: Andrew Beekhof <abeekhof>
Status: CLOSED CURRENTRELEASE QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: cluster-maint, dvossel, lmiksik
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pacemaker-1.1.12-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-09 11:15:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Radek Steiger 2014-09-30 13:28:08 UTC 
Description of problem:
When running the 'cibadmin -u --force' command on a node which is not the domain controller, it will get stuck for 30 seconds and then returns "Call cib_upgrade failed (-62): Timer expired", while in fact the scheme version is upgraded correctly. This does not happen on the DC node.


Version-Release number of selected component (if applicable):
pacemaker-libs-1.1.12-1.el7.x86_64
pacemaker-cli-1.1.12-1.el7.x86_64
pacemaker-1.1.12-1.el7.x86_64
pacemaker-cluster-libs-1.1.12-1.el7.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Check that the CIB version can be upgraded: pcs cluster cib | egrep -o '(validate\S+)'
2. Find out which node is the current DC: pcs status | grep DC
3. Perform the upgrade on node other than the DC:  cibadmin --upgrade --force


Actual results:

[root@virt-042 ~]# pcs cluster cib | egrep -o '(validate\S+)'
validate-with="pacemaker-1.2"
[root@virt-042 ~]# pcs status | grep DC
Current DC: virt-043 (3) - partition with quorum

[root@virt-042 ~]# cibadmin --upgrade --force
Call cib_upgrade failed (-62): Timer expired
[root@virt-042 ~]# pcs cluster cib | egrep -o '(validate\S+)'
validate-with="pacemaker-2.1"


Expected results:

[root@virt-042 ~]# cibadmin --upgrade --force
[root@virt-042 ~]# pcs cluster cib | egrep -o '(validate\S+)'
validate-with="pacemaker-2.1"
Comment 3 Andrew Beekhof 2014-09-30 22:55:52 UTC 
crm_report archive?
Comment 4 Andrew Beekhof 2014-10-01 05:09:15 UTC 
Fixed upstream:  https://github.com/beekhof/pacemaker/commit/93c872b

Is this really a regression though?
I don't think we advertised this command previously