Jira (FACT-380) Private ipaddress is used as ipaddress fact

2016-01-12 Thread Jason Ashby (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Ashby commented on  FACT-380 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Private ipaddress is used as ipaddress fact  
 
 
 
 
 
 
 
 
 
 
Eric Sorenson is this issue addressed in the Puppet 4 "bundle"? 
Another workaround for those interested... Instead of using a custom fact, you can override facter variables with an environment variable, e.g. 
 
 
 
 
 
 
# /etc/environment 
 
 
 
 
FACTER_ipaddress=172.20.2.2
 
 
 
 
 
 
 
just prefix any fact name with FACTER_ and add to your global environment file (/etc/environment for me on CentOS 6). (Side note - if you're testing via puppet agent -t, be sure to source that environment file (or log out and back in) in order to realize the change.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit ht

Jira (PUP-620) (PR 2429) Add install_options to gem provider

2014-10-13 Thread Jason Ashby (JIRA) 
Title: Message Title










 

 Jason Ashby commented on an issue











 






  Re: (PR 2429) Add install_options to gem provider 










Hi Charlie Sharpsteen, I'm still seeing the quoting issue on puppet 3.7.1.






$ sudo puppet agent -t




Notice: Ignoring --listen on onetime run




Info: Retrieving pluginfacts




Notice: /File[/var/lib/puppet/facts.d]/mode: mode changed '0755' to '2775'




Info: Retrieving plugin




Info: Loading facts




Info: Loading facts




Info: Caching catalog for foo.example.com




Info: Applying configuration version '1413212488'




Error: Execution of '/usr/bin/gem install --no-rdoc --no-ri sys-proctable "--http-proxy http://webproxy.example.com:8080"' returned 2: ERROR:  Could not find a valid gem '"--http-proxy http://webproxy.example.com:8080"' (>= 0) in any repository

Jira (PUP-1521) Allow configuration of SSL ciphers

2014-10-07 Thread Jason Ashby (JIRA) 
Title: Message Title










 

 Jason Ashby commented on an issue











 






  Re: Allow configuration of SSL ciphers 










Eric Sorenson I noticed this was set to Closed before your most recent comment. Are there any plans to make the ciphers configurable on the agent side?












   

 Add Comment











 













 Puppet /  PUP-1521



  Allow configuration of SSL ciphers 







 We run puppet in a secure environment. One of the policies in place states that no weak ciphers (key length < 128 bit) are allowed anywhere.   Our puppetmasterd got flagged by a review recently as it allows such ciphers on incoming connections. I temporarily worked around it with this horrible hack in /usr/lib/ruby/1.8/webrick/ssl.rb:     ctx.verify...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-620) (PR 2429) Add install_options to gem provider

2014-10-03 Thread Jason Ashby (JIRA) 
Title: Message Title










 

 Jason Ashby commented on an issue











 






  Re: (PR 2429) Add install_options to gem provider 










Excellent, thanks. You said 3.6.0...do you mean it will ship in the next Puppet (3.7.2)?












   

 Add Comment











 













 Puppet /  PUP-620



  (PR 2429) Add install_options to gem provider 







 h2. added install_options to gem provider. now you can do... install_options...   * Author: Mike   * Company:   * Github ID: [mmoghadas|https://github.com/mmoghadas]  * [Pull Request 2012 Discussion|https://github.com/puppetlabs/puppet/pull/2012]  * [Pull Request 2012 File Diff|https://github.com/puppetlabs/puppet/pull/2012/files...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-620) (PR 2429) Add install_options to gem provider

2014-09-15 Thread Jason Ashby (JIRA) 
Title: Message Title










 

 Jason Ashby commented on an issue











 






  Re: (PR 2429) Add install_options to gem provider 










This doesn't seem to work very well for me for installing a gem. I'm on puppet 3.6.1, CentOS 6.5. I have the following:



package { 'fpm':
ensure => 'latest',
provider => 'gem',
install_options => ['--http-proxy http://webproxy.example.com:8080'],
}





$ sudo puppet agent -t
...snip...
Info: Applying configuration version '1410792649'
Error: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm "--http-proxy http://webproxy.example.com:8080"' returned 1: ERROR:  Could not find a valid gem 'fpm' (>= 0) in any repository
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)
Wrapped exception:
Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm "--http-proxy http://webproxy.example.com:8080"' returned 1: ERROR:  Could not find a valid gem 'fpm' (>= 0) in any repository
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)
Error: /Stage[main]/Fpm/Package[fpm]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri fpm "--http-proxy http://webproxy.example.com:8080"' returned 1: ERROR:  Could not find a valid gem 'fpm' (>= 0) in any repository
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: Connection timed out - connect(2) (http://rubygems.org/latest_specs.4.8.gz)



However, running the 'gem install' it directly from the shell on the host works fine. I believe its something with the quotes being inserted into the command?



$ sudo /usr/bin/gem install --no-rdoc --no-ri fpm --http-proxy http://webproxy.example.com:8080
Fetching: json-1.8.1.gem (100%)
Building native extensions.  This could take a while...
...
...

Fetching: cabin-0.6.1.gem (100%)
Fetching: backports-3.6.0.gem (100%)
Fetching: arr-pm-0.0.9.gem (100%)
Fetching: clamp-0.6.3.gem (100%)
Fetching: ffi-1.9.3.gem (100%)
Building native extensions.  This could take a while...
...
.

Fetching: childprocess-0.5.3.gem (100%)
Fetching: fpm-1.2.0.gem (100%)
Successfully installed json-1.8.1
Successfully installed cabin-0.6.1
Successfully installed backports-3.6.0
Successfully installed arr-pm-0.0.9
Successfully installed clamp-0.6.3
Successfully installed ffi-1.9.3
Successfully installed childprocess-0.5.3
Successfully installed fpm-1.2.0
8 gems installed



Running it directly from the shell EXACTLY as puppet displayed it (with quotes) gives a different error than puppet spits out:



$ /usr/bin/gem install --no-rdoc --no-ri fpm "--http-proxy http://webproxy.example.com:8080"
ERROR:  While executing gem ... (OptionParser::InvalidOption)