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 1190732 - Fix pcsd gem files
Summary: Fix pcsd gem files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.6
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-09 14:42 UTC by Tomas Jelinek
Modified: 2016-05-10 19:27 UTC (History)
3 users (show)

Fixed In Version: pcs-0.9.145-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 19:27:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed fix (3.24 KB, patch)
2015-09-18 12:29 UTC, Tomas Jelinek
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0739 0 normal SHIPPED_LIVE pcs bug fix update 2016-05-10 22:29:32 UTC

Description Tomas Jelinek 2015-02-09 14:42:16 UTC
It works in RHEL currently, but it could be dealt with in a more elegant way which would be possibly 100 % compatible with upstream and non-RHEL machines.

Related parts of existing github pull request https://github.com/feist/pcs/pull/48
6) pcsd/Makefile was modified so it considers the Ruby gems a dependency of build_gems (which won't try downloading gems), and it doesn't try to differentiate between RHEL 6 and RHEL 7 gems anymore.
7) pcsd/Gemfile (and pcsd/Gemfile.lock) have been modified so that the one problematic gem in RHEL 6 (rpam-ruby19-feist) is now pulled from a git repository instead.
8) Some dependencies were not being included in pcsd/Gemfile (and pcsd/Gemfile.lock), and they have been added so the build from makefile works correctly.
8) pcsd/pscd.rb was modified so it requires bundler/setup and executes Bundler.setup(:default), which allows rpam-ruby19-feist to be used (since rubygems won't do it).
9) pcsd/pcsd (the init script) was modified to execute via bundler rather than directly with ruby, which allows the bundled gems to be required properly (needed for rpam-ruby19-feist).

Comment 3 Tomas Jelinek 2015-09-18 12:29:12 UTC
Created attachment 1074852 [details]
proposed fix

Comment 8 errata-xmlrpc 2016-05-10 19:27:38 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-0739.html


Note You need to log in before you can comment on or make changes to this bug.