Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10584

puppet_gem provider does not use vendored PKG_CONFIG_PATH when installing native extensions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.5.22, PUP 6.18.0
    • Component/s: None
    • Labels:
    • Environment:

      Running on Puppet 6 environment.
      Puppet-Agent version of 6.0.2
      Puppet Gem version of 2.5.0
      Running on a Centos 7 machine

    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Story Points:
      3
    • Sprint:
      NW - 2020-07-21
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Allows installing of gems with native extensions that require PKG_CONFIG_PATH when using puppet_gem provider, for example the rugged gem
    • QA Risk Assessment:
      Needs Assessment

      Description

      Based on bellow issue on using /opt/puppetlabs/puppet/bin/gem, we will update puppet_gem package provider to be able to handle rugged installation with puppet: puppet resource package rugged ensure=present provider=puppet_gem

      ------

       

      When installing R10K, if you install Rugged with the following method

      `/opt/puppetlabs/puppet/bin/gem install rugged`

      It will build as intended, but will then cause SegV to occur on running R10K even no matter what provider you have it set to use.

      If you first set your pkgconfig env with
      `export PKG_CONFIG_PATH=/opt/puppetlabs/puppet/lib/pkgconfig`

      And then install Rugged, it will then build and run as intended.

      The Puppet Gem environment should probably handle making sure gems built use vendored components.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ciprian.badescu Ciprian Badescu
              Reporter:
              ciprian.badescu Ciprian Badescu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support