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 1026431 - pcs incorrectly detects RHEL6 variants
Summary: pcs incorrectly detects RHEL6 variants
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact:
URL:
Whiteboard:
: 1073584 (view as bug list)
Depends On:
Blocks: 996235
TreeView+ depends on / blocked
 
Reported: 2013-11-04 15:59 UTC by Tuomo Soini
Modified: 2014-10-14 07:21 UTC (History)
15 users (show)

Fixed In Version: pcs-0.9.123-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 07:21:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch to cater for 3 most popular el6 variants (433 bytes, patch)
2013-11-05 22:54 UTC, Trevor Hemsley 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 663283 0 None None None Never
Red Hat Product Errata RHBA-2014:1526 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2014-10-14 01:22:04 UTC

Description Tuomo Soini 2013-11-04 15:59:51 UTC 
Description of problem:

snippets of pcs status output:

Cluster name:

cluster name is not shown here while it is set in cluster.conf

Stack: cman

and stack is cman...

PCSD Status:

There is no PCSD in rhel 6.4 so why print this header when pcsd is not even installed.

Error: no nodes found in corosync.conf

This is printed to stderr - this should be very expected with cman stack where there is no corosync.conf at all.
Comment 1 Tuomo Soini 2013-11-04 16:02:52 UTC 
PCS version is  0.9.90-1.el6_4
Comment 3 Chris Feist 2013-11-04 19:05:00 UTC 
Can you post the output you get when you run 'pcs status' and the output you get what you run 'pcs cluster status'.
Comment 4 Tuomo Soini 2013-11-05 19:01:17 UTC 
# pcs cluster status
Cluster Status:
 Last updated: Tue Nov  5 20:55:37 2013
 Last change: Tue Nov  5 20:07:50 2013 via cibadmin on test1.foobar.fi
 Stack: cman
 Current DC: test1.foobar.fi - partition with quorum
 Version: 1.1.10-1.el6_4.4-368c726
 2 Nodes configured
 4 Resources configured

PCSD Status:
Error: no nodes found in corosync.conf

# pcs status
Cluster name: 
Last updated: Tue Nov  5 20:55:30 2013
Last change: Tue Nov  5 20:07:50 2013 via cibadmin on test1.foobar.fi
Stack: cman
Current DC: test1.foobar.fi - partition with quorum
Version: 1.1.10-1.el6_4.4-368c726
2 Nodes configured
4 Resources configured


Online: [ test1.foobar.fi test2.foobar.fi ]

Full list of resources:

 Resource Group: services
     ClusterIP   (ocf::heartbeat:IPaddr2):      Started test1.foobar.fi 
     ldirectord  (lsb:ldirectord):              Started test1.foobar.fi 
 Clone Set: cl-Connectivity [Connectivity]
     Started: [ test1.foobar.fi test2.foobar.fi ]


PCSD Status:
Error: no nodes found in corosync.conf
Comment 5 Tuomo Soini 2013-11-05 19:02:38 UTC 
everything else is output to stdout but Error: line is stderr.
Comment 6 Chris Feist 2013-11-05 19:49:31 UTC 
Can you post the output of this command: 'cat /etc/issue'
Comment 7 Tuomo Soini 2013-11-05 21:18:57 UTC 
You could just ask if this is real rhel or not - it's not - but the problems I described are rhel specific with unmodified software.

ldirctord is our own package.
Comment 8 Tuomo Soini 2013-11-05 21:43:18 UTC 
ah - I understand - is_rhel6() doesn't work with any rhel clones.

I'll patch to suppot our linux variant. I inform which problems are left behind when os is correctly detected - and I'll inform Centos folks about need for patching.
Comment 9 Trevor Hemsley 2013-11-05 22:54:44 UTC 
Created attachment 820054 [details]
Proposed patch to cater for 3 most popular el6 variants

One liner patch to work on RHEL6, CentOS 6 and SL6
Comment 10 Chris Feist 2013-11-08 06:17:22 UTC 
Yes, just wanted to see if that was the issue.

Thanks for that patch, I'll be applying that patch upstream ASAP.

There is also one other issue (that is fixed upstream) which causes the pcsd checks to happen when running 'pcs cluster status' ('pcs status' is fine).

Those messages should be harmless (so you can ignore them).  However, there are a few other situations where is_rhel6 does things differently, so if you're running CentOS or Scientific Linux you'll want to apply that patch on your installs.
Comment 12 Chris Feist 2014-01-13 23:14:15 UTC 
Note: the patch to fix this issue is here:

https://github.com/feist/pcs/commit/eed5198ea20cbad4be100990a6cca8a101296358
Comment 14 Fabio Massimo Di Nitto 2014-03-27 12:20:27 UTC 
*** Bug 1073584 has been marked as a duplicate of this bug. ***
Comment 15 Russ Anderson 2014-05-30 16:32:08 UTC 
Status check.  This BZ is marked POST but no indication that the fix is in.
Is this problem fixed?  Or what needs to be done to fix it?
Thanks,
Comment 16 Chris Feist 2014-06-11 21:43:09 UTC 
This fix has been committed upstream, but is not yet released in RHEL.
Comment 17 Chris Feist 2014-06-11 21:44:46 UTC 
Updated summary to reflect that this bug is for fixing issues with pcs detecting RHEL 6 variants.  pcsd should be working upstream with RHEL 6 systems so 'pcs cluster status' should be printing out this information.
Comment 18 Chris Feist 2014-06-23 14:42:49 UTC 
This fix is in the latest pcs build, I'll find an easy way to test this.
Comment 28 Chris Feist 2014-09-03 20:18:45 UTC 
Before Fix:


[root@bid-06 pcs]# rpm -q pcs
pcs-0.9.123-6.el6.x86_64
[root@bid-06 pcs]# echo "Red Hat Enterprise Linux Client release 6.5 (Santiago)" > /etc/system-release
[root@bid-06 pcs]# python -c'import utils; print utils.is_rhel6()'
False


After Fix:

[root@bid-05 pcs]# rpm -q pcs
pcs-0.9.123-9.el6.x86_64
[root@bid-05 pcs]# echo "Red Hat Enterprise Linux Client release 6.5 (Santiago)" > /etc/system-release
[root@bid-05 pcs]# python -c'import utils; print utils.is_rhel6()'
True
[root@bid-05 pcs]# echo "Red Hat Enterprise Linux ComputeNode release 6.6 Beta (Santiago)" > /etc/system-release
[root@bid-05 pcs]# python -c'import utils; print utils.is_rhel6()'
True
[root@bid-05 pcs]# echo "Red Hat Enterprise Linux Workstation release 6.6 Beta (Santiago)" > /etc/system-release
[root@bid-05 pcs]# python -c'import utils; print utils.is_rhel6()'
True
[root@bid-05 pcs]# echo "Red Hat Enterprise Linux Server release 7.0 (Maipo)" > /etc/system-release
[root@bid-05 pcs]# python -c'import utils; print utils.is_rhel6()'
False
Comment 31 errata-xmlrpc 2014-10-14 07:21:29 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.

http://rhn.redhat.com/errata/RHBA-2014-1526.html
Note You need to log in before you can comment on or make changes to this bug.