Jira (PUP-6413) Pip provider on 3.x fails when using ensure => latest
Title: Message Title
Spencer Krum created an issue
Puppet / PUP-6413
Pip provider on 3.x fails when using ensure => latest
Issue Type:
Bug
Affects Versions:
PUP 3.8.7
Assignee:
Unassigned
Created:
2016/06/15 3:06 PM
Priority:
Normal
Reporter:
Spencer Krum
Pypi changed behaviour today because of vulnerabilities in urrlib, which is used by pip.
http://blog.blindspotsecurity.com/2016/06/advisory-http-header-injection-in.html
Pypi changed to denying http requests entirely instead of redirecting to https. (I guess? I don't really understand)
Without this patch:
root@derpderp:~# cat foo.pp package { 'diskimage-builder': ensure => latest, provider => pip, }
root@derpderp:~# puppet apply foo.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning') Notice: Compiled catalog for derpderp in environment production in 0.14 seconds Error: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP Error: /Stage[main]/Main/Package[diskimage-builder]/ensure: change from 1.17.0 to latest failed: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP Notice: Finished catalog run in 0.67 seconds
So this breaks any puppet 3.x using the default pip provider.
With this patch, it just
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Spencer Krum commented on PUP-4516 Re: Agent does not stop with Ctrl-C I believe the issue doesn't show up on 2.x+ ruby and is only seen on lower versions (I'm on 1.8.7 because I'm a bad person). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Spencer Krum commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Recent EL6's have moved from python-pip to pip. Is that going to be fixed here or is that a new ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4516) Agent does not stop with Ctrl-C
Title: Message Title Spencer Krum commented on PUP-4516 Re: Agent does not stop with Ctrl-C I'm affected by this too. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4055) Support DNF package manager (yum successor)
Title: Message Title Spencer Krum commented on PUP-4055 Re: Support DNF package manager (yum successor) Robin, can you try the puppet-dnf module? It's a super simple shim. I don't have any f22+ boxes to kick it on at the moment. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1376) Allow exclusion in tags specified on the command line
Title: Message Title Spencer Krum commented on PUP-1376 Re: Allow exclusion in tags specified on the command line I wan this feature. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC root@puppetapply:~# /opt/puppetlabs/bin/puppet config print config /etc/puppetlabs/puppet/puppet.conf root@puppetapply:~# mv /etc/puppet/puppet.conf /etc/puppetlabs/puppet/puppet.conf root@puppetapply:~# /opt/puppetlabs/bin/puppet config print modulepath /etc/puppetlabs/code/environments/production/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules root@puppetapply:~# mv /etc/puppet/modules/helloworld /etc/puppetlabs/code/modules/ root@puppetapply:~# /opt/puppetlabs/bin/puppet apply -- --debug--help --verbose --version root@puppetapply:~# /opt/puppetlabs/bin/puppet apply test.pp
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title
Spencer Krum updated an issue
Puppet / PUP-4694
Puppet apply doesn't read manifest when using ENC
Change By:
Spencer Krum
Thisisprettysimilarbehaviourtohttps://tickets.puppetlabs.com/browse/PUP-3258soitmightjustbethatagain.Situation:Anencdefinesclassesandasite.pporpuppetapplyfoo.ppdefinesmorepuppetthings.Intheexamplecasenotifyresourcesareusedbutinproductionresourcedefaultsareset.Fromhttps://docs.puppetlabs.com/guides/external_nodes.htmlIexpecttogetallresourcesdefinedbytheENCandinfoo.ppbutwhatIactuallygetisonlyresourcesfromtheENC.Thesetup:{code}root@puppetapply:~# ruby--versionruby1.9.3p484(2013-11-22revision43786)[x86_64-linux]root@puppetapply:~# cat/etc/puppet/puppet.conf[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppetfactpath=$vardir/lib/facternode_terminus=execexternal_nodes=/usr/local/bin/puppet_node_classifier[master]#Theseareneededwhenthepuppetmasterisrunbypassenger#andcansafelyberemovedifwebrickisused.ssl_client_header=SSL_CLIENT_S_DNssl_client_verify_header=SSL_CLIENT_VERIFY{code}{code}root@puppetapply:~#cat/usr/local/bin/puppet_node_classifier#!/bin/bashcat/root/foo.yaml{code}{code}root@puppetapply:~#catfoo.yaml---classes:-helloworld#environment:devel{code}{code}root@puppetapply:~#cattest.ppnotify{derp:}nodedefault{}{code}{code}root@puppetapply:~#cat/etc/puppet/modules/helloworld/manifests/init.ppclasshelloworld{notify{SUPNERDS:}}{code}Thecorrectbehaviourisseenon3.4:{code}root@puppetapply:~#puppet--version3.4.3root@puppetapply:~#puppetapplytest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsWarning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.Notice:derpNotice:/Stage[main]/Main/Notify[derp]/message:defined'message'as'derp'Notice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.20seconds{code}Butanincorrectbehaviourisseenin3.8.1:{code}root@puppetapply:~#puppetapply--environment=develtest.ppNotice:Compiledcatalogforpuppetapply.openstacklocalinenvironmentdevelin0.10secondsNotice:SUPNERDSNotice:/Stage[main]/Helloworld/Notify[SUPNERDS]/message:defined'message'as'SUPNERDS'Notice:Finishedcatalogrunin0.11secondsroot@puppetapply:~#puppet--version3.8.1{code}
Add Comment
Jira (PUP-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum commented on PUP-4694 Re: Puppet apply doesn't read manifest when using ENC Whats the best way to get a nightly version of 4.2? Just for testing. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4694) Puppet apply doesn't read manifest when using ENC
Title: Message Title Spencer Krum created an issue Puppet / PUP-4694 Puppet apply doesn't read manifest when using ENC Issue Type: Bug Assignee: Unassigned Created: 2015/06/03 11:44 PM Priority: Normal Reporter: Spencer Krum This is pretty similar behaviour to https://tickets.puppetlabs.com/browse/PUP-3258 so it might just be that again. Situation: An enc defines classes and a site.pp or puppet apply foo.pp defines more puppet things. In the example case notify resources are used but in production resource defaults are set. From https://docs.puppetlabs.com/guides/external_nodes.html I expect to get all resources defined by the ENC and in foo.pp but what I actually get is only resources from the ENC. The setup: root@puppetapply:~# cat /etc/puppet/puppet.conf [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter node_terminus = exec external_nodes = /usr/local/bin/puppet_node_classifier [master] These are needed when the puppetmaster is run by passenger and can safely be removed if webrick is used. ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY root@puppetapply:~# cat /usr/local/bin/puppet_node_classifier #!/bin/bash cat /root/foo.yaml root@puppetapply:~# cat foo.yaml — classes:
Jira (PUP-4055) Support DNF package manager (yum successor)
Title: Message Title Spencer Krum commented on PUP-4055 Re: Support DNF package manager (yum successor) Well so thats just me being bored and cping the yum provider. There is probably some way to do it such that we don't have the same code in two places. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4673) Pip installs from behind proxy can't ensure=latest
Title: Message Title Spencer Krum created an issue Puppet / PUP-4673 Pip installs from behind proxy can't ensure=latest Issue Type: Bug Assignee: Unassigned Created: 2015/05/29 6:15 PM Environment: behind http proxy Priority: Normal Reporter: Spencer Krum The pip package provider can ensure = version but can't ensure latest when using a proxy. https://github.com/puppetlabs/puppet/pull/3984 (venv)krum@ftctstories01g:~$ env| grep proxy http_proxy=http://web-proxy.houston.hp.com:8080 HTTPS_PROXY=http://web-proxy.houston.hp.com:8080 https_proxy=http://web-proxy.houston.hp.com:8080 HTTP_PROXY=http://web-proxy.houston.hp.com:8080 (venv)krum@ftctstories01g:~$ puppet --version 3.7.4 (venv)krum@ftctstories01g:~$ ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] (venv)krum@ftctstories01g:~$ gem --version 1.8.15 $ puppet resource package gear provider=pip ensure=latest --debug --trace Debug: Runtime environment: ruby_version=1.8.7, run_mode=user, puppet_version=3.7.4 Debug: Puppet::Type::Package::ProviderNim: file /usr/bin/lslpp does not exist Debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist Debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist Debug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does not exist Debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_info does not exist Debug: Puppet::Type::Package::ProviderPacman: file /usr/bin/pacman does not exist Debug:
Jira (PUP-1040) Segregate client facts, server facts and ENC params in topscope hashes
Title: Message Title Spencer Krum commented on PUP-1040 Re: Segregate client facts, server facts and ENC params in topscope hashes I don't agree with this. I think having each fact at top scope is natural. I've been using puppet for years and have never had a problem teaching this concept to new people. I think henrik mentioned that facts are all under a top scope facts hash anyways, so if someone wants to do that they can. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3661) Remove zpool from puppet core and into a module
Title: Message Title Spencer Krum commented on PUP-3661 Re: Remove zpool from puppet core and into a module The zfs type and provider should go with this. Mailing list thread: https://groups.google.com/forum/#!topic/puppet-dev/kLSiWghNrvY Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title
Spencer Krum commented on PUP-1054
Re: Services should support 'reload' in addition to 'restart'
This can be pretty easily worked around by:
file { /etc/config: ensure = present }
~ service { 'myservice': ensure = running, restart = '/usr/bin/apachectl reload', #or something like that }
This should probably be better documented/publicized though. I used to think that this ticket was a huge problem. I've kind of gotten over that. Its seductive to say that we should add a reload parameter to the service type. I think it will lead us into having more and more parameters to the service type (reload, graceful_reload, close_all_connections_and_turn_off, give_me_a_pony, and so on). I also think we will quickly end up with two services who define the word 'reload' and/or 'graceful reload' differently.
So what do I think should be done? I think the workaround of overloading the restart parameter should be exercised. Are there places it doesn't work? Where are those places? If we change Puppet we should make sure we don't leave those cases out in the cold.
To go a bit further, this makes me wonder if notify/subscribe should be extended. I'm not sure exactly what that would look like. But right now notify/subscribe is 'You should restart.' I think what I'm suggesting is a richer language for resources to interact. A file resource could notify the service resource with 'refresh' or with 'restart.' I'm usually pretty weary of adding complexity, but I can imagine types and providers writing handlers for arbitrary events, and that could enable some super cool behaviors in puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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
Jira (HI-148) Support multiple backends of the same type
Title: Message Title Spencer Krum commented on an issue Re: Support multiple backends of the same type I would like to see this as well. I think my requirements are a bit less stringent. I'd like to see the yaml backend support multiple data dirs. Right now I hack it by setting the datadir to something way up the filesystem such as '/etc/puppet/' Then I reach into two separate locations by using the hierarchy. This is awesome for keeping the insecure data with the puppet code and the secure data in a separate directory/repository with a lower surface area. I would like to simply provide a list of data directories, and have hiera run the entire hierarchy on them in order. Add Comment Hiera / HI-148 Support multiple backends of the same type It would be great if Hiera could support multiple backends of the same type. Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here: https://github.com/lukebigum/hiera https://github.com/lukebigum/hiera-json And it works with a configuration file like this: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-189) LXC Container support
Title: Message Title Spencer Krum commented on an issue Re: LXC Container support I just pulled down facter from git and it works great on LXCs. All the stderr complaints of various facts have been silenced. [root@ol63cont ~]# facter --version 1.7.3 [root@ol63cont ~]# facter is_virtual /dev/mem: No such file or directory false and now: [root@ol63cont facter]# facter --version 1.7.5-rc1 [root@ol63cont facter]# facter is_virtual false Much nicer. I also created a fact that can tell (at least for my flavor of lxc) if a host is an lxc or not. I'm really looking for help testing on other lxc flavors and building a little tree of logic to determine LXCness based on other available information. https://github.com/nibalizer/puppet-lxcfact Add Comment Facter / FACT-189 LXC Container support The virtual fact for facter should support lxc containers. For more information about lxc: http://lxc.sourceforge.net/ We can detect an running lxc master system, if /cgroup is mounted on the system. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
