Jira (PUP-8027) gem provider does not work behind proxy

[Josh Davidson (JIRA)]

Josh Davidson created an issue

Puppet / PUP-8027 gem provider does not work behind proxy Issue Type: Bug Affects Versions: PUP 5.3.1 Assignee: Eric Sorenson Components: Community Created: 2017/10/04 5:59 PM Environment: RHEL 7 x64 Priority: Normal Reporter: Josh Davidson PUP-620 added an install_options parameter to the gem provider which can be used to specify a proxy: package { 'puppet-lint': ensure => latest, provider => 'gem', install_options => [ Unknown macro: {'--http-proxy' => 'http} ], } This works fine on the the original run where the gem is installed. However, on subsequent runs the puppet agent will hang since the gem list command does not pass in the install options (proxy): Debug: Executing: '/bin/gem list --local' Debug: Executing: '/bin/gem list --remote ^puppet-lint At this point the puppet agent will hang until killed. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Josh Davidson (JIRA)]

Josh Davidson updated an issue

Puppet / PUP-8027 gem provider does not work behind proxy

Change By: Josh Davidson

PUP-620 added an install_options parameter to the gem provider which can be used to specify a proxy:

{ quote} {

package { 'puppet-lint':     ensure          => latest,     provider        => 'gem',

install_options => [{'--http-proxy' => 'http:// myproxy proxy1 . lmco. com:80'}],   } {quote } }

This works fine on the the original run where the gem is installed.  However, on subsequent runs the puppet agent will hang since the gem list command does not pass in the install options (proxy):

{quote}Debug: Executing: '/bin/gem list --local' Debug: Executing: '/bin/gem list --remote ^puppet-lint{quote}

At this point the puppet agent will hang until killed.

Add Comment

[Josh Davidson (JIRA)]

Josh Davidson updated an issue

Puppet / PUP-8027 gem provider does not work behind proxy Change By: Josh Davidson

PUP-620 added an install_options parameter to the gem provider which can be used to specify a proxy:

{ {   code}

package { 'puppet-lint':     ensure          => latest,     provider        => 'gem',

install_options => [{'--http-proxy' => 'http:// proxy1 myproxy . lmco. com:80'}],   } {code } }

This works fine on the the original run where the gem is installed.  However, on subsequent runs the puppet agent will hang since the gem list command does not pass in the install options (proxy): {quote}Debug: Executing: '/bin/gem list --local' Debug: Executing: '/bin/gem list --remote ^puppet-lint{quote} At this point the puppet agent will hang until killed.

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-8027 gem provider does not work behind proxy

Change By: Moses Mendoza Team: Platform Core

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-8027 gem provider does not work behind proxy

Change By: Moses Mendoza Sprint: Platform Core Grooming

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-8027 gem provider does not work behind proxy

Change By: Josh Cooper Sprint: Platform Core Grooming

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-8027

Re: gem provider does not work behind proxy Package providers like yum and apt allow proxy settings to be configured in their respective config files, such as /etc/apt/apt.conf.d/proxy.conf for apt. I'm thinking we should do the same for gems. For example. add the following to /etc/gemrc: --- http-proxy: http://example.com:80 Trying to reuse install_options for things other than the gem install command is going to be problematic, as some options may not be suitable for gem list.

Add Comment