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 1020982 - RHCS should log warning if software version is not identical
Summary: RHCS should log warning if software version is not identical
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-18 16:17 UTC by Chester Knapp
Modified: 2014-07-21 04:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-21 14:37:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chester Knapp 2013-10-18 16:17:54 UTC 
Description of problem: I've been running with 1 version (old) of rhcs on one node, and the latest version on the other two. Regardless of whether or not this actually causes a problem, something in rhcs should log a version mismatch to warn the user. 


Version-Release number of selected component (if applicable):
  ccs.x86_64 0:0.16.2-63.el6                               cluster-glue-libs.x86_64 0:1.0.5-6.el6                    
  clusterlib.x86_64 0:3.0.12.1-49.el6_4.1                  cman.x86_64 0:3.0.12.1-49.el6_4.1                         
  corosync.x86_64 0:1.4.1-15.el6_4.1                       corosynclib.x86_64 0:1.4.1-15.el6_4.1                     
  fence-agents.x86_64 0:3.1.5-25.el6_4.2                   fence-virt.x86_64 0:0.2.3-13.el6                          
  modcluster.x86_64 0:0.16.2-20.el6                        resource-agents.x86_64 0:3.9.2-21.el6_4.3                 
  rgmanager.x86_64 0:3.0.12.1-17.el6                       ricci.x86_64 0:0.16.2-63.el6     

How reproducible:
100%

Steps to Reproduce:
1. Start cluster with version mismatch
2.
3.

Actual results: Nothing, cluster proceeds normally


Expected results: Log message to warn about mismatched versions. 


Additional info:
Packages in question, from yum update:
---> Package ccs.x86_64 0:0.16.2-43.el6 will be updated
---> Package ccs.x86_64 0:0.16.2-63.el6 will be an update
---> Package cluster-glue-libs.x86_64 0:1.0.5-2.el6 will be updated
---> Package cluster-glue-libs.x86_64 0:1.0.5-6.el6 will be an update
---> Package clusterlib.x86_64 0:3.0.12.1-23.el6 will be updated
---> Package clusterlib.x86_64 0:3.0.12.1-49.el6_4.1 will be an update
---> Package cman.x86_64 0:3.0.12.1-23.el6 will be updated
---> Package cman.x86_64 0:3.0.12.1-49.el6_4.1 will be an update
---> Package corosync.x86_64 0:1.4.1-4.1.el6 will be updated
---> Package corosync.x86_64 0:1.4.1-15.el6_4.1 will be an update
---> Package corosynclib.x86_64 0:1.4.1-4.1.el6 will be updated
---> Package corosynclib.x86_64 0:1.4.1-15.el6_4.1 will be an update
---> Package fence-agents.x86_64 0:3.1.5-10.el6 will be updated
---> Package fence-agents.x86_64 0:3.1.5-25.el6_4.2 will be an update
---> Package fence-virt.x86_64 0:0.2.3-5.el6 will be updated
---> Package fence-virt.x86_64 0:0.2.3-13.el6 will be an update
---> Package modcluster.x86_64 0:0.16.2-14.el6 will be updated
---> Package modcluster.x86_64 0:0.16.2-20.el6 will be an update
---> Package resource-agents.x86_64 0:3.9.2-7.el6 will be updated
---> Package resource-agents.x86_64 0:3.9.2-21.el6_4.3 will be an update
---> Package rgmanager.x86_64 0:3.0.12.1-5.el6 will be updated
---> Package rgmanager.x86_64 0:3.0.12.1-17.el6 will be an update
---> Package ricci.x86_64 0:0.16.2-43.el6 will be updated
---> Package ricci.x86_64 0:0.16.2-63.el6 will be an update
Comment 2 Jaroslav Kortus 2013-10-18 17:09:36 UTC 
well, if "cluster proceeds normally", then I don't think this warrants a bug :)
Comment 3 Chester Knapp 2013-10-18 17:17:58 UTC 
Still a bug, just a low priority one. Surely you recognize that it is suboptimal to be using different versions of RHCS simultaneously. Call it a usability issue if you like.
Comment 4 Fabio Massimo Di Nitto 2013-10-21 14:37:26 UTC 
(In reply to Chester Knapp from comment #3)
> Still a bug, just a low priority one. Surely you recognize that it is
> suboptimal to be using different versions of RHCS simultaneously. Call it a
> usability issue if you like.

We have clear documentation on how to update a cluster with a process that ensure compatibility across upgrades.

A situation as described should only be a temporary state while upgrading cluster nodes when a user is sitting in front of a terminal.

It basically adds no useful information for the end user, at the cost of adding very complex pieces of code to hook into rpm.
Note You need to log in before you can comment on or make changes to this bug.