Bug 1163982

Summary:	Upgrading pacemaker-1.3-style configuration to pacemaker-2.0 with upgrade-1.3.xsl every 15 minutes
Product:	Red Hat Enterprise Linux 6	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	pacemaker	Assignee:	Andrew Beekhof <abeekhof>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	cfeist, cluster-maint, dvossel, jkortus, pzimek, robert.scheck, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-1.1.12-8.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-22 07:43:54 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 Robert Scheck 2014-11-13 20:51:09 UTC

Description of problem:
Since upgrading to RHEL 6.6 we see the following lines every 15 minutes on
all of our (and our customers') systems:

Nov 13 21:44:59 tux1 crmd[3630]:   notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]
Nov 13 21:44:59 tux1 pengine[3629]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Nov 13 21:44:59 tux1 pengine[3629]:   notice: update_validation: Upgrading pacemaker-1.3-style configuration to pacemaker-2.0 with upgrade-1.3.xsl
Nov 13 21:44:59 tux1 pengine[3629]:   notice: update_validation: Transformed the configuration from pacemaker-1.2 to pacemaker-2.0
Nov 13 21:44:59 tux1 pengine[3629]:   notice: unpack_config: On loss of CCM Quorum: Ignore
Nov 13 21:44:59 tux1 pengine[3629]:   notice: process_pe_message: Calculated Transition 2680: /var/lib/pacemaker/pengine/pe-input-1118.bz2
Nov 13 21:44:59 tux1 crmd[3630]:   notice: run_graph: Transition 2680 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-1118.bz2): Complete
Nov 13 21:44:59 tux1 crmd[3630]:   notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]

Version-Release number of selected component (if applicable):
pacemaker-1.1.12-4.el6.x86_64

How reproducible:
Everytime after upgrading from RHEL 6.5 with pacemaker to RHEL 6.6.

Actual results:
Upgrading message every 15 minutes.

Expected results:
Upgrading message only once - especially because pacemaker tells that it is
performing the upgrade. We did not see any impact but it still seems to be a
bug somehow?

Comment 2 Andrew Beekhof 2014-11-17 05:33:57 UTC

There is a in-place upgrade of the copy sent to the pengine, the main copy in the cib isn't touched.  We can arrange to log it only once though.

Comment 3 Robert Scheck 2014-11-17 13:45:17 UTC

This is confusing now: Why is that upgrade only happening in-place (this is
what I get from your reply)? Did we miss any step to upgrade the main copy in
the cib?

Comment 4 Andrew Beekhof 2014-11-17 21:52:25 UTC

The policy engine only understands the latest format.

However we don't update the main configuration since the customer might have scripts or workflows that rely on the old format.

So when the policy engine runs, it upgrades a temporary copy of the configuration and uses that.

Comment 5 Robert Scheck 2014-11-17 21:56:23 UTC

Ah, understood. So logging it only once rather every 15 minutes seems to make 
more sense to me.

Comment 6 Andrew Beekhof 2014-11-18 21:51:29 UTC

Upstream patch:
   https://github.com/beekhof/pacemaker/commit/7dd9022

Comment 11 errata-xmlrpc 2015-07-22 07:43:54 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.

https://rhn.redhat.com/errata/RHSA-2015-1424.html

Comment 12 Robert Scheck 2015-07-24 15:04:23 UTC

This is only solved half, one of the messages still appears every 15 minutes;
filed bug #1246563 to get this addressed, too.