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 1299812 - crm_node output changed which breaks some openstack-foreman-installer scripts
Summary: crm_node output changed which breaks some openstack-foreman-installer scripts
Keywords:
Status: CLOSED DUPLICATE of bug 1290684
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 10:24 UTC by GE Scott Knauss
Modified: 2019-09-12 09:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-20 08:56:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description GE Scott Knauss 2016-01-19 10:24:08 UTC 
Description of problem:

most recent version of pacemaker (1.1.13-10.el7) changes the output of crm_node which is breaking scripts in openstack foreman installer.

Version-Release number of selected component (if applicable):

1.1.13-10.el7

How reproducible:

attempt to deploy openstack using foreman installer after updating to latest pacemaker



Actual results:

deployment fails 

Expected results:

successful deployment

Additional info:

Earlier version 1.1.12-22.el7.1.4
[root@controller-1 ~]# /usr/sbin/crm_node -l
2 pcmk-controller-3
3 pcmk-controller-2
1 pcmk-controller-1

With new 1.1.13-10.el7
[root@controller-1 ~]# /usr/sbin/crm_node -l
2 pcmk-controller-3 member
3 pcmk-controller-2 member
1 pcmk-controller-1 member

I.e. there is a third field added which will confuse script

[root@controller-1 ~]# grep crm_node /tmp/ha-all-in-one-util.bash 
  /usr/sbin/crm_node -n
  members=$(/usr/sbin/crm_node -l | perl -p -e 's/^.*\s+(\S+)$/$1/g')
[root@controller-1 ~]# 

making it not get the cluster members but just "member" three times.

This script comes from 

# rpm -qf /usr/share/openstack-foreman-installer/puppet/modules/quickstack/templates/ha-all-in-one-util.erb
openstack-foreman-installer-3.0.26-1.el7ost.noarch
Comment 4 GE Scott Knauss 2016-01-19 16:46:51 UTC 
Chris,

   Done. 

BZ: 1299987

-Scott
Comment 5 GE Scott Knauss 2016-01-20 08:56:09 UTC 

*** This bug has been marked as a duplicate of bug 1290684 ***
Comment 7 Andrew Beekhof 2016-02-17 02:16:20 UTC 
Right. The mistake is mine. 

I assumed that people would be looking for the second field (and thus it would be safe to add a third).  It didn't occur to me that people would be looking for the 'last' field.

It appears I was/am in the minority.  Sorry.
Note You need to log in before you can comment on or make changes to this bug.