Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title
Jason Antman commented on an issue
Re: service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Jo,
In my previous comment I suggested 4 possibilities, which ranged from not too nice to flat-out Bad idea. But I don't recall saying anything about disallowing puppet to check for status... But once again, it seems like the issue here is that mco puppet runonce actually starts the process with --daemon.
Add Comment
Puppet / PUP-1320
service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
We have recently switched from puppet agent in daemon mode (for kick) to cron-run puppet with mcollective agent. However, I started noticing that puppet policies were being inconsistently applied across the hosts. It turns out that this policy is the problem: pre service { 'puppet': ensure = stopped, enable = false, ...
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
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Jason Antman updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Jason Antman Affects Version/s: 3.3.0 Affects Version/s: 3.4.1 Add Comment 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/groups/opt_out.
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Jason Antman updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Jason Antman Component/s: TypesandProviders Labels: archpackagepacman redmine Add Comment 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/groups/opt_out.
Jira (PUP-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Jason Antman updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Jason Antman Thepacmansystemunderstandstheconceptofpackagegroups;agroupofpackagesgivenaname,allofwhichareinstalledwhenthatnameisspecified.Thedefaultrepos'packagegroupscanbeseenathttps://www.archlinux.org/groups/;examplesincludekdebase(22packages;https://www.archlinux.org/groups/x86_64/kdebase/),xorg(77packages;https://www.archlinux.org/groups/x86_64/xorg/)andxorg-apps(37packages;https://www.archlinux.org/groups/x86_64/xorg-apps/).IfIspecifyoneofthesegroupsasaPackageresourceinmymanifest,thepackageswithinthegrouparereinstalledateverypuppetrun.Thisisbecauserunningapackagelistquery(listcmd;pacman-Q)onlyliststheactualpackagesinstalled,notthegroups.Thepacmanprovider(self.instances)shouldalsoexecute`pacman-Qg`andaddtheuniquevaluesofthefirstcolumnofoutput(thenamesofinstalledpackagegroups)tothelistofinstalledpackages-thiswillstopthereinstallfromhappening. Myrubyisprettybasic,butI'lltakeacrackatapatchsometimethisweek. Add Comment 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/groups/opt_out.
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title
Jason Antman commented on an issue
Re: Yum provider using version-release to validate installation.
I've started a branch with some unit tests that describe what I think the intended behavior is, as well as some of the current behavior: https://github.com/jantman/puppet/tree/PUP1244tests
I've also copied the current logic of Puppet::Util::Package.versioncmp to a yumversioncmp() method in the yum provider, as the generic (naive) version comparison done by the current versioncmp() is the problem here. There are probably also going to need to be some tweaks to the 'latest' logic. In light of PUP-682 and PUP-683, I'm going to see if I can dive into the yum/rpm source to figure out the details of version comparison before I do any more work.
Add Comment
Puppet / PUP-1244
Yum provider using version-release to validate installation.
When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification. pre $snmp_version = 5.3.2.2 package { net-snmp: ensure = ${snmp_version}; } /pre Client output: pre debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Chan...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1084) Python Pip wheel support
Title: Message Title Jason Antman commented on an issue Re: Python Pip wheel support If any help is needed, I work with one of the pip/virtualenv maintainers, who's very interested in seeing wheel support included in Puppet. If his assistance is needed in figuring out any of the pip-side stuff, I can loop him in on this. Add Comment Puppet / PUP-1084 Python Pip wheel support Now that Python's package manager pip[0] supports installing the new binary distributions (wheels[1]) we should be able to install these through Puppet. I've had a preliminary look at this here: https://github.com/davbo/puppet/tree/add-python-pip-wheel This works (at first glance) but I'm not a puppet developer and certainly not a Ruby dev. I... 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
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title
Jo Rhett commented on an issue
Re: service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Yeah, RI mentioned that to me. There are some thoughts that it would be useful to run it --no-daemonize so that we can grab the return code from the run but it would require another fork, and yes that's certainly not how mcollective expects it today.
Ugh, okay that was just a long way of saying yes, there are two different scenarios but I believe they are the same problem after all and that one good commit could fix both of them.
Add Comment
Puppet / PUP-1320
service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
We have recently switched from puppet agent in daemon mode (for kick) to cron-run puppet with mcollective agent. However, I started noticing that puppet policies were being inconsistently applied across the hosts. It turns out that this policy is the problem: pre service { 'puppet': ensure = stopped, enable = false, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are
Jira (PUP-1062) Add virtualenv support to the pip package provider
Title: Message Title Jason Antman updated an issue Puppet / PUP-1062 Add virtualenv support to the pip package provider Change By: Jason Antman Component/s: TypesandProviders Labels: pip redmine Add Comment 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/groups/opt_out.
Jira (PUP-1193) pip provider does not detect existance of system installed packages
Title: Message Title Jason Antman updated an issue Puppet / PUP-1193 pip provider does not detect existance of system installed packages Change By: Jason Antman Component/s: TypesandProviders Labels: pip redmine Add Comment 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/groups/opt_out.
Jira (PUP-1082) pip provider should handle multiple pips/pythons
Title: Message Title Jason Antman updated an issue Puppet / PUP-1082 pip provider should handle multiple pips/pythons Change By: Jason Antman Component/s: TypesandProviders Labels: pip redmine Add Comment 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/groups/opt_out.
Jira (PUP-1071) Install Options for PIP package provider (incl. patch)
Title: Message Title Jason Antman updated an issue Puppet / PUP-1071 Install Options for PIP package provider (incl. patch) On one hand, yes, install options could be useful for pip. However, the ones you specified - prefix and install_lib - make the provider non-idempotent. These things install the package in a non-default location, but don't do anything else to tell the provider how to know about it. For the reporter's use case, PUP-1062 - adding virtualenv support to pip - is the better, safer, idempotent alternative. However, there's still a whitelist of pip options that should be handed in install options (things like proxy, timeout, find-links, index-url, extra-index-url, no-index, use-mirrors, etc.) Change By: Jason Antman Component/s: TypesandProviders Labels: pip redmine Add Comment 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
Jira (PUP-931) PR (2122): Feature #23359: Added support of http_proxy environment variable for pip... - clarsonneur
Title: Message Title gepetto-bot commented on an issue Re: PR (2122): Feature #23359: Added support of http_proxy environment variable for pip... - clarsonneur jantman commented: Perhaps someone from PL can comment, but is it really safe to use an environment variable for this, as that would be set outside of puppet (and possibly effect the end-result of a pip install if, for example, this is a caching proxy with an old cache?) It seems to me that passing in install options to pip from Puppet (https://tickets.puppetlabs.com/browse/PUP-1071) might be better.. but I may be wrong/overly cautious... Add Comment Puppet / PUP-931 PR (2122): Feature #23359: Added support of http_proxy environment variable for pip... - clarsonneur h2. Feature #23359: Added support of http_proxy environment variable for pip... * Author: * Company: * Github ID: [clarsonneur|https://github.com/clarsonneur] * [Pull Request 2122 Discussion|https://github.com/puppetlabs/puppet/pull/2122] * [Pull Request 2122 File Diff|https://github.com/puppetlabs/puppet/pull/2122/files] h2. Pull Request Desc... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1088) manage python virtualenvs
Title: Message Title Jason Antman updated an issue Puppet / PUP-1088 manage python virtualenvs PUP-1062 adds (when it's done) virtualenv support to the built-in pip package provider. So that can handle installing packages (assuming they're on pypi, and specified in packagename or packagename==version format. That's all relevant to installing packages (your python::app, sort of) in an already existing virtualenv. As to managing virtualenvs themselves, there are already a few modules out there that do this, though most of them are called python and also handle other python aspects, which may or may not be desired in a particular environment. I'd say the best way to handle this is to finish PUP-1062, and then create an appropriate virtualenv provider (or just a defined type) as a module, hopefully to be picked up by puppetlabs. Change By: Jason Antman Component/s: TypesandProviders Labels: pippython redmine virtualenv Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PUP-83) Data bindings don't set calling_module / calling_class variables during lookups
Title: Message Title
Markus Nussdorfer commented on an issue
Re: Data bindings don't set calling_module / calling_class variables during lookups
According to the redmine ticket this should be resolved, but i am still having issues with the following versions
hiera-1.3.0-1.el6.noarch
puppet-3.4.1-1.el6.noarch
hiera.yaml
---
:backends:
- puppet
- json
:json:
:datadir: /etc/puppet/hieradata
:hierarchy:
- node/%{::fqdn}
- hostgroup/%{::hostgroup}/%{::environment}
- hostgroup/%{::hostgroup}/default
- class/%{::calling_class}/%{::environment}
- class/%{::calling_class}/default
- default/%{::environment}
- default/default
class file
class role::deployment {
$test = hiera('test')
notice(hiera-test: ${test})
class { 'foreman': }
}
none of the lookups seem to return any result.
log output
Debug: hiera(): Looking up test in Puppet backend
Debug: hiera(): Looking for data in data::node/foreman-test.localdomain
Debug: hiera(): Looking for data in data::hostgroup//dev
Debug: hiera(): Looking for data in data::hostgroup//default
Debug: hiera(): Looking for data in data::class//dev
Debug: hiera(): Looking for data in data::class//default
Debug: hiera(): Looking for data in data::default/dev
Debug: hiera(): Looking for data in data::default/default
Debug: hiera(): Looking for data in jumio::role::deployment::data
Debug: hiera(): Looking for data in jumio::data
Debug: hiera(): Looking up test in JSON backend
Debug: hiera(): Looking for data source node/foreman-test.localdomain
Debug: hiera(): Cannot find datafile /etc/puppet/hieradata/node/foreman-test.localdomain.json, skipping
Debug: hiera(): Looking for data source default/dev
Notice: Scope(Class[Jumio::Role::Deployment]): hiera-test: default/dev.json
Debug: hiera(): Looking up foreman::port in Puppet backend
Debug: hiera(): Looking for data in data::node/foreman-test.localdomain
Debug: hiera(): Looking for data in data::hostgroup//dev
Debug: hiera(): Looking for data in data::hostgroup//default
Debug: hiera(): Looking for data in data::class//dev
Debug: hiera(): Looking for data in data::class//default
Debug: hiera(): Looking for data in data::default/dev
Debug: hiera(): Looking for data in data::default/default
Debug: hiera(): Looking for data in foreman::data
Debug: hiera(): Looking up foreman::port in JSON backend
Debug: hiera(): Looking for data source node/foreman-test.localdomain
Debug: hiera(): Cannot find
