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 1163982 - Upgrading pacemaker-1.3-style configuration to pacemaker-2.0 with upgrade-1.3.xsl every 15 minutes
Summary: Upgrading pacemaker-1.3-style configuration to pacemaker-2.0 with upgrade-1.3...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-13 20:51 UTC by Robert Scheck
Modified: 2019-10-10 09:28 UTC (History)
7 users (show)

Fixed In Version: pacemaker-1.1.12-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-22 07:43:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1424 0 normal SHIPPED_LIVE Moderate: pacemaker security and bug fix update 2015-07-20 18:06:24 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.