Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Prior to this update, pcs used the corosync.conf file when listing cluster nodes using the "pcs status nodes corosync" command. However, corosync.conf does not exist in Red Hat Enterprise Linux 6. As a consequence, "pcs status nodes corosync" failed to execute. With this update, cluster nodes on Red Hat Enterprise Linux 6 are listed using the cman_tool program and the /etc/cluster/cluster.conf file, and "pcs status nodes corosync" now functions correctly.
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
Our company maintains a version Centos 6.6 and calls it Mitel Standard Linux.
Here's what the version files look like.
[root@huysnpmvm9 ~]# cat /etc/system-release /etc/redhat-release
Mitel Networks server 10.3.17.0
Mitel Standard Linux release 10.3.17.0
[root@huysnpmvm9 ~]#
This is equivalent to
bash-4.1$ cat /etc/system-release /etc/redhat-release
Red Hat Enterprise Linux Server release 6
CentOS release 6.6 (Final)
Red Hat Enterprise Linux Server release 6
CentOS release 6.6 (Final)
Huy Vu,
The problem you're seeing is that pcs is not properly detecting whether you're on a RHEL6 based system or a RHEL7 based system.
In your version of pcs it checks for the first two digits separated by a '.'. If the first of the two digits is a 6, it assumes it's a RHEL 6 system, otherwise it assumes a RHEL 7 system.
With your system-release file it thinks it's on a RHEL 7 based system, which is why these problems are happening.
In future version of pcs for RHEL 6 we will be doing a better job of determining if it's a RHEL6 or RHEL7 system, but you'll have to wait for the 6.8 package of pcs to see those changes.
In the meantime you can fix this issue by hard coding the 'is_rhel6()' function in utils.py to always return true.