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 1246563 - update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3 every 15 minutes
Summary: update_validation: pacemaker-1.2-style configuration is also valid for pacema...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.7
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.8
Assignee: Andrew Beekhof
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-24 15:01 UTC by Robert Scheck
Modified: 2019-10-10 09:59 UTC (History)
9 users (show)

Fixed In Version: pacemaker-1.1.14-1.1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 23:52:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0856 0 normal SHIPPED_LIVE pacemaker bug fix and enhancement update 2016-05-10 22:44:25 UTC

Description Robert Scheck 2015-07-24 15:01:29 UTC 
Description of problem:
Since upgrading to RHEL 6.6 or 6.7 we see the following lines every 15
minutes on all of our (and our customers') systems:

Jul 24 12:14:51 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 12:29:51 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 12:44:51 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 12:59:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 13:14:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 13:29:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 13:44:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 13:59:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 14:14:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 14:29:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 14:44:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 14:59:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 15:14:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 15:29:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 15:44:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 15:59:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 16:14:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 16:29:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3
Jul 24 16:44:52 tux1 pengine[3845]:   notice: update_validation: pacemaker-1.2-style configuration is also valid for pacemaker-1.3

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

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

Actual results:
Update validation message every 15 minutes.

Expected results:
Update validation message only once.

Additional info:
This is NOT a duplicate of bug #1163982, but meant to address the parts that
were not addressed in the previously mentioned bug.
Comment 2 Robert Scheck 2015-07-24 15:06:46 UTC 
Updated case 01286927 in the Red Hat customer portal regarding this issue.
Comment 3 Robert Scheck 2015-07-24 15:10:21 UTC 
Btw, this issue also exists also on RHEL 7: pacemaker-1.1.12-22.el7_1.2.x86_64
Comment 4 Andrew Beekhof 2015-07-30 23:39:49 UTC 
ack
Comment 11 errata-xmlrpc 2016-05-10 23:52:12 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/RHBA-2016-0856.html
Note You need to log in before you can comment on or make changes to this bug.