Jira (FACT-341) Windows operatingsystemrelease support
Title: Message Title Louis Mayorga commented on an issue Re: Windows operatingsystemrelease support I believe this is not yet on PE 3.2.3. Is this feature going to be integrated on the next release of PE? Add Comment Facter / FACT-341 Windows operatingsystemrelease support operatingsystemrelease should return any of the following XP, Vista, 7, 2003, 2008, 2008R2 rather than the kernel version. 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-1125) Exec checks should be turned into metaparameters
Title: Message Title Geoffrey Hicks commented on an issue Re: Exec checks should be turned into metaparameters I have an additional use case that I'd like to submit for this. It may not be a very good use of Puppet, and I may be going against Puppet's whole configuration management philosophy by doing it this way, but it's the reality I'm faced with for the time being. Right now, we're using git clone as an ad-hoc way of deploying code to many of our boxes. We intend to move away from it in favor of packages eventually, but even after that we'll probably want to use git for convenience on developer boxes. Certain configuration files for these git-deployed apps are handled by Puppet, as their contents may vary based on what environment the box is in - for example we may want to use Facter to determine whether a box is in the Development environment, and set the log level to DEBUG if that's the case. Or we might want to turn on certain low-resource modes in Development but be greedy about resources on a dedicated Production box. The problem we're running into is that git doesn't allow you to clone into a directory that already has files in it - you either have to do a wonky work-around with git init, or you have to store the config files in a different directory. If we had onlyif available for the file resource type, we could easily tell Puppet that we want the config files to be written only if the main application executable exists. That way, the directory stays empty if the repository hasn't been cloned into it yet; but if the application is there, Puppet will write its config files on the next run. You could probably distill this down to a more general case: resources whose ordering depends on another resource that isn't managed in Puppet. The ideal, of course, is to put everything into your configuration management tool, but there will always be cases where that isn't feasible for reasons that aren't in the puppetmaster's control (other development teams, for example). It'd be nice to have an easy way to tell Puppet to check whether some outside task has been completed before applying certain parts of the manifest, without having to write a custom fact for every time that this shows up. Add Comment Puppet / PUP-1125
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 kbarber commented: @cprice404 hows it going? Looks like a recent merge makes this one up for a rebase. Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... 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 (FACT-341) Windows operatingsystemrelease support
Title: Message Title Joshua Cooper commented on an issue Re: Windows operatingsystemrelease support Louis Mayorga that's correct, PE 3.x hasn't moved to facter 2.x yet. That said if this is something that would greatly help, you can always file a Puppet Enterprise feature request to have this fact backported to pe-facter. If you do, make sure to link to this ticket. Add Comment Facter / FACT-341 Windows operatingsystemrelease support operatingsystemrelease should return any of the following XP, Vista, 7, 2003, 2008, 2008R2 rather than the kernel version. 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-1787) Improved strictness and safety in the Language
Title: Message Title Andy Parker updated an issue Puppet / PUP-1787 Improved strictness and safety in the Language Change By: Andy Parker Summary: DataTypesthroughout Improvedstrictnessandsafetyin the Puppet Language 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/d/optout.
Jira (PUP-1787) Improved strictness and safety in the Language
Title: Message Title Andy Parker updated an issue Puppet / PUP-1787 Improved strictness and safety in the Language Change By: Andy Parker Thepuppetlanguagestillhasalotofgotchasthatcancropup.Manyoftheseallowunexpectedbehaviortooccurorgetridoftheguaranteesexpectedbyuserssuchasimmutability,strictnessaboutvariableuse,anddifficultycreatinggoodencapsulations.Weneedtoimplementsomethinglikeastrictmodethatletsusersturnoncertainchecksincertaincasesandinothercasesweneedtoprovidenewfunctionalitytoletthemexpresswhatisreallyneeded. 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/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title
Andy Parker commented on an issue
Re: defining a class twice merges their behaviors
That is unfortunately the behavior the language has had for a long time. Any class can be re-opened and have more added to its body. I believe that it came about as a side effect of the main class, which is the class to which any expressions outside of any node, class, or define will be added. This is also the source of the behavior described in both PUP-1414 and
PUP-280
.
Given how long this has been around, I don't think we can simply change it. I think it should be made an error when a strict mode is enabled.
Add Comment
Puppet / PUP-2695
defining a class twice merges their behaviors
A new hire ([~erin]) is working through exercises and inadvertently defined a class twice in a file with surprising results. {code} class test { notice('testing') notify { 'first': } } class test { notice('again') notify { 'surprise!': } } include test {code} {code} [root@student ~]# puppet apply test.pp Notice: Scope(Class[T...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-694) Retire short name http stat querying in metrics
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-694 Retire short name http stat querying in metrics Issue Type: Task Assignee: Unassigned Created: 29/May/14 9:08 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber The old way of doing name based URL stats is hard to manage. It always needs changes for each version. It's uncertain what version stats it should return also. We should just remove it in favour of full paths. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-693) Retire events-query-limit
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-693 Retire events-query-limit Issue Type: Task Assignee: Unassigned Created: 29/May/14 9:07 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber Event-query-limit is no longer used, it should be retired. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-695) Retire v2 API
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-695 Retire v2 API Issue Type: Task Assignee: Unassigned Created: 29/May/14 9:10 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber The v2 API has been deprecated in 2.x so should be retired in 3.0.0. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-696) Retire full puppetdb-* subcommands
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-696 Retire full puppetdb-* subcommands Issue Type: Task Assignee: Unassigned Created: 29/May/14 9:12 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber We introduced puppetdb subcommands in 1.x time to retire the old puppetdb-* subcommands. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby
Title: Message Title Matthaus Owens commented on an issue Re: Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby Joshua Cooper We currently build ruby for windows using this jenkins job: http://jenkins-release.delivery.puppetlabs.net/job/WindowsRubyBuilds This allows us to build ruby independently of rubyinstaller when a vulnerability exists in ruby or its dependent libraries. Add Comment Puppet / PUP-2389 Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby We need to vendor x86 and x64 versions of ruby 2.x, and install the appropriate sets of gems into both branches. 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-2383) Need x64 win-builder to generate both 32 and 64bit MSIs
Title: Message Title Joshua Cooper commented on an issue Re: Need x64 win-builder to generate both 32 and 64bit MSIs Moses Mendoza thanks, I think we are good as-is. I will keep this ticket open until we get to the stage where we're actually generating x86 and x64 MSIs, to see if we need to update the wix toolset for example. Add Comment Puppet / PUP-2383 Need x64 win-builder to generate both 32 and 64bit MSIs Need to verify that existing win-builders are x64 and can generate MSIs for both platforms. If win-builders are x32, then we will need to provision new x64 builders. 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-2696) puppetd kernel panic
Title: Message Title Charlie Sharpsteen commented on an issue Re: puppetd kernel panic Also, Puppet 2.6.x is long past end of life. Can the issue be re-produced under 3.x? Add Comment Puppet / PUP-2696 puppetd kernel panic We had a kernel panic caused by what seems like puppetd. I've attached the screenshot in hopes of someone identifying the bug and letting me know if this can happen again without upgrade. 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-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby
Title: Message Title Joshua Cooper commented on an issue Re: Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby Matthaus Owens yes, though the problem is that ruby 2.1 still has test failures when run on windows, so I don't think it's ready for prime time yet. The end of this thread https://groups.google.com/d/topic/rubyinstaller/8Je3OEbtb3w/discussion mentions the remaining two bugs in ruby core: test_float: https://bugs.ruby-lang.org/issues/8358 test_machine_stackoverflow: https://bugs.ruby-lang.org/issues/9739 Add Comment Puppet / PUP-2389 Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby We need to vendor x86 and x64 versions of ruby 2.x, and install the appropriate sets of gems into both branches. 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.
Jira (PUP-2696) puppetd kernel panic
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2696 puppetd kernel panic Change By: Charlie Sharpsteen Assignee: Bart 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/d/optout.
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title
John Bollinger commented on an issue
Re: Exec checks should be turned into metaparameters
If we had onlyif available for the file resource type, we could easily tell Puppet that we want the config files to be written only if the main application executable exists. That way, the directory stays empty if the repository hasn't been cloned into it yet; but if the application is there, Puppet will write its config files on the next run.
Ok.
This discussion has lead me to realize that Puppet already has a pretty good approximation of 'onlyif' for all resource types, with this syntax:
exec { 'onlyif_command': }
-
type { 'title': parameters }
That yields roughly Felix's behavior (3) because syncing the Exec will fail if the onlyif command does not return a success result, preventing Puppet from attempting to sync the other resource.
Alternatively, if you prefer something similar to Felix's behavior (2), then I think you can use this variation:
exec { '/bin/true': _onlyif_ = 'onlyif_command', noop = true }
-
type { 'title': parameters }
In that case, Puppet will detect the Exec as out of sync if the onlyif command succeeds, but it will not attempt to sync it because it is marked noop. Because the Exec is not synchronized, Puppet will not (should not) attempt to sync the other resource.
Would one of those serve your requirement adequately?
Add Comment
Puppet / PUP-1125
Exec checks should be turned into metaparameters
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title Kylo Ginsberg commented on an issue Re: Exec checks should be turned into metaparameters You could probably distill this down to a more general case: resources whose ordering depends on another resource that isn't managed in Puppet. Yes, that seems like the primary abstraction that's being requested. Although Frederik Wagner's package A unless package B example earlier on suggests two resource manageable by puppet, so it did make me wonder if there was also a request for conditional relationships between two managed (or noop'd) puppet resources? I'm not quite sure how that would work though It'd be nice to have an easy way to tell Puppet to check whether some outside task has been completed before applying certain parts of the manifest, without having to write a custom fact for every time that this shows up. Is a custom fact (or even easier, an external fact) that much harder? And wouldn't an external fact allow for a more DRY approach, e.g. if the same conditional logic was needed in more than one place? I'm not trolling; I think I may be missing some pain point. And if so, that makes me wonder if we should work on alleviating that pain point, rather than working around it by adding metaparameters. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter.
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Andy Parker updated an issue Puppet / PUP-2689 A node can't always collect its own exported resources Change By: Andy Parker Component/s: DSL 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Andy Parker updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing Change By: Andy Parker Component/s: Server 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/d/optout.
Jira (FACT-341) Windows operatingsystemrelease support
Title: Message Title Louis Mayorga commented on an issue Re: Windows operatingsystemrelease support I just did. Thanks. Add Comment Facter / FACT-341 Windows operatingsystemrelease support operatingsystemrelease should return any of the following XP, Vista, 7, 2003, 2008, 2008R2 rather than the kernel version. 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-837) FFI Puppet::Util::Windows::SID module
Title: Message Title Andy Parker updated an issue Puppet / PUP-837 FFI Puppet::Util::Windows::SID module Change By: Andy Parker Component/s: Client 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/d/optout.
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 cprice404 commented: @kbarber Updated; fixes support for the dashboard, adds documentation. Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... 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-1125) Exec checks should be turned into metaparameters
Title: Message Title
John Bollinger commented on an issue
Re: Exec checks should be turned into metaparameters
You cannot get an analog of Felix's option (1) by chaining in in Exec, however, nor in general can you implement groups of alternative resources, such as we discussed earlier, where one resource being in sync is sufficient for the whole group to be synchronized. For such purposes, I find myself imagining a variation on defined types. Consider this syntax:
define package_a_or_b disjunctive () {
package { 'A': ensure = 'latest' }
-
package { 'B': ensure = 'present', noop = true }
}
...
package_a_or_b { 'A unless B': }
An ordinary defined type attempts to ensure that all resources declared within are synchronized, and succeeds if that is achieved. The obscurely-named 'disjunctive' keyword would indicate a different behavior, wherein the define succeeds if any one or more of the resources declared within is or can be synchronized, and it only attempts to sync any resource if none of them are yet synchronized.
In the example code, an instance of the disjunctive 'package_a_or_b' type is in sync if Package['B'] is present on the system, or if Package['A'] is present and at the latest version. If neither, then Puppet will attempt to ensure the latest version of A installed, but in no case will it install or update Package['B'], because that package is declared with noop = true.
Although that would introduce a new keyword, it would be backwards compatible with the current DSL because nothing is currently allowed between defined name and parentheses / body. Disjunctive types would have the nice property that the resources within succeed or fail as a group, with all the attending benefits for declaring relationships, while still relying on Puppet resources as their building blocks, with all the benefits attending that. And judicious use of Exec resources within such a construct could yield everything that 'onlyif' and 'unless' metaparameters might do, and then some.
Add Comment
Puppet / PUP-1125
Jira (PUP-2625) PuppetLabs repo dependencies for Ubuntu Saucy are insufficient
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2625
PuppetLabs repo dependencies for Ubuntu Saucy are insufficient
Change By:
Charlie Sharpsteen
Thedocumentationprovidedonhttp://docs.puppetlabs.com/guides/puppetlabs_package_repositories.htmlnolongerworksforubuntusaucy: pre {code} root@sunstone:~#apt-getinstallpuppetReadingpackagelists...DoneBuildingdependencytreeReadingstateinformation...DoneSomepackagescouldnotbeinstalled.ThismaymeanthatyouhaverequestedanimpossiblesituationorifyouareusingtheunstabledistributionthatsomerequiredpackageshavenotyetbeencreatedorbeenmovedoutofIncoming.Thefollowinginformationmayhelptoresolvethesituation:Thefollowingpackageshaveunmetdependencies:puppet:Depends:puppet-common(=3.3.2-1puppetlabs1)butitisnotgoingtobeinstalledE:Unabletocorrectproblems,youhaveheldbrokenpackages.root@sunstone:~#apt-getinstallpuppetpuppet-commonReadingpackagelists...DoneBuildingdependencytreeReadingstateinformation...DoneSomepackagescouldnotbeinstalled.ThismaymeanthatyouhaverequestedanimpossiblesituationorifyouareusingtheunstabledistributionthatsomerequiredpackageshavenotyetbeencreatedorbeenmovedoutofIncoming.Thefollowinginformationmayhelptoresolvethesituation:Thefollowingpackageshaveunmetdependencies:puppet-common:Depends:hiera(=1.0.0)butitisnotinstallableRecommends:debconf-utilsbutitisnotgoingtobeinstalledE:Unabletocorrectproblems,youhaveheldbrokenpackages.root@sunstone:~#apt-getinstallpuppetpuppet-commondebconf-utilsReadingpackagelists...DoneBuildingdependencytreeReadingstateinformation...DoneSomepackagescouldnotbeinstalled.ThismaymeanthatyouhaverequestedanimpossiblesituationorifyouareusingtheunstabledistributionthatsomerequiredpackageshavenotyetbeencreatedorbeenmovedoutofIncoming.Thefollowinginformationmayhelptoresolvethesituation:Thefollowingpackageshaveunmetdependencies:puppet-common:Depends:hiera(=1.0.0)butitisnotinstallableE:Unabletocorrectproblems,youhaveheldbrokenpackages.root@sunstone:~#apt-cacheshowpkghieraPackage:hieraVersions:ReverseDepends:puppet-common,hiera1.0.0puppet-common,hiera1.0.0Dependencies:Provides:ReverseProvides: /pre {code} Asitshowsabove,puppet-commondependsonvirtualpackagehieraforwhichtherearenoproviders.
Add Comment
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title Geoffrey Hicks commented on an issue Re: Exec checks should be turned into metaparameters Is a custom fact (or even easier, an external fact) that much harder? And wouldn't an external fact allow for a more DRY approach, e.g. if the same conditional logic was needed in more than one place? I'm not trolling; I think I may be missing some pain point. And if so, that makes me wonder if we should work on alleviating that pain point, rather than working around it by adding metaparameters. The specific example that I'm working on currently is an application server profile that will set up an arbitrary number of node.js apps, each one being executed and handled by pm2. I have a defined-type to represent these apps - it takes in things like environment variables, the main script filename, command line parameters, etc., and writes them out to two config files; then it attempts to start the main script using a pm2 command. Within this defined type, it would be extremely easy to add an onlyif to each of those two file declarations in the defined-type, so that they're only written if the main script file is found in the directory. I'm basically doing the same thing with the pm2 start command, since that's an exec. Two quick lines of code added, and the problem is gone for all current and future node apps. I haven't done much with custom facts, but it's my impression that to use them I would need to create a different custom fact for each application that is deployed this way, checking its specific directory to see if that app has been deployed yet. For any future apps, a new custom fact would need to be added - something that our Ops group would probably have to do (or teach), since most of the developers don't work directly with Puppet or Ruby. That makes the solution much less self-service - as it is right now, a developer just needs to put their app's name and arguments into Hiera, and Puppet takes care of all the infrastructure needed for deployment. Maybe this is too obscure a case to justify adding metaparameters for. But it seems like similar situations could apply for almost any defined-type that has this problem; the defined type may be used in a hundred different locations that would each require their own custom fact, when instead you could just bake the check into the defined-type itself and handle the problem for all uses. Add Comment
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title John Bollinger commented on an issue Re: Exec checks should be turned into metaparameters Is a custom fact (or even easier, an external fact) that much harder? And wouldn't an external fact allow for a more DRY approach, e.g. if the same conditional logic was needed in more than one place? I'm not trolling; I think I may be missing some pain point. Indeed, now that external facts are synchronized via plugin-sync, they provide an excellent alternative, almost as easy to create, and more general. And if so, that makes me wonder if we should work on alleviating that pain point, rather than working around it by adding metaparameters. The only functional aspect of any of this that cannot be addressed by facts is one that has not yet been raised: evaluating conditions at the time of the catalog run, in conjunction with syncing a specific resource, rather than beforehand. Beyond that it's on one hand a question of syntax, and on the other a question of the nature of the abstractions Puppet works with. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter.
Jira (PUP-2479) Missing version tag 2.7.11 on github repo
Title: Message Title Andy Parker assigned an issue to Matthaus Owens Matthaus Owens, Melissa Stone, I took a look in the github repo and there isn't a 2.7.11 tag, but there is a 2.7.11-1 tag. Is that the same thing? Puppet / PUP-2479 Missing version tag 2.7.11 on github repo Change By: Andy Parker Assignee: EricSorenson MatthausOwens 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/d/optout.
Jira (PUP-2625) PuppetLabs repo dependencies for Ubuntu Saucy are insufficient
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2625 PuppetLabs repo dependencies for Ubuntu Saucy are insufficient Change By: Charlie Sharpsteen Reporter: redmine.exporter JoRhett 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/d/optout.
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/457/ Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... 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
Jira (PUP-2479) Missing version tag 2.7.11 on github repo
Title: Message Title Matthaus Owens commented on an issue Re: Missing version tag 2.7.11 on github repo Andy Parker Sort of. There was a 2.7.11 tag, but it didn't point at the commit intended. So rather than blowing it away, which is a no-no for public repos, we created a 2.7.11-1 tag, which pointed at the correct commit. I don't know how the 2.7.11 tag got deleted, but 2.7.11-1 points to the commit for the 2.7.11 release. Add Comment Puppet / PUP-2479 Missing version tag 2.7.11 on github repo Is there a special reason why the tag 2.7.11 is missing in https://github.com/puppetlabs/puppet ? I am doing a puppet master upgrade from 2.7.11 - 3.X.X and using Envpuppet ((http://puppetlabs.com/blog/use-envpuppet-test-multiple-puppet-versions)) for testing and I am missing this tag :( 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
Jira (PUP-2639) Increase environment_timeout default.
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2639 Increase environment_timeout default. Change By: Andy Parker Assignee: AndyParker 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/d/optout.
Jira (PUP-836) FFI Puppet::Util::Windows::User module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-836 FFI Puppet::Util::Windows::User module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2554) FFI Puppet::Util::ADSI module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2554 FFI Puppet::Util::ADSI module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-840) FFI Puppet::Util::Colors module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-840 FFI Puppet::Util::Colors module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2657) FFI Puppet::Util::Windows::Error
Title: Message Title
Joshua Cooper commented on an issue
Re: FFI Puppet::Util::Windows::Error
Merged into master in d38153bd7 to be released in 3.7.0
Add Comment
Puppet / PUP-2657
FFI Puppet::Util::Windows::Error
Need to FFI {panel} def initialize(message, code = GetLastError.call, original = nil) {panel}
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-2657) FFI Puppet::Util::Windows::Error
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2657 FFI Puppet::Util::Windows::Error Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2385) FFI Puppet::Util::Windows::File module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2385 FFI Puppet::Util::Windows::File module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-392) Validate win32 gems on x64
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-392 Validate win32 gems on x64 Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2657) FFI Puppet::Util::Windows::Error
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2657 FFI Puppet::Util::Windows::Error Change By: Joshua Cooper Labels: windows 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/d/optout.
Jira (PUP-2389) Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2389 Create ruby 2.x branches for x86 and x64 in puppet-win32-ruby Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-835) FFI native windows code
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-835 FFI native windows code Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2388) Update git setup steps to install architecture specific version of ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2388 Update git setup steps to install architecture specific version of ruby Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-1283) Update win32-service gem
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1283 Update win32-service gem Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2383) Need x64 win-builder to generate both 32 and 64bit MSIs
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2383 Need x64 win-builder to generate both 32 and 64bit MSIs Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-839) FFI Puppet::Util::Windows::Security module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-839 FFI Puppet::Util::Windows::Security module Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-766) FFI native windows root certs code
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-766 FFI native windows root certs code Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2382) Standardize existing FFI code and refactor where necessary
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2382 Standardize existing FFI code and refactor where necessary Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2388) Update git setup steps to install architecture specific version of ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2388 Update git setup steps to install architecture specific version of ruby Change By: Joshua Cooper Labels: windows 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/d/optout.
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency Change By: Joshua Cooper Labels: windows 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/d/optout.
Jira (PUP-1760) Update win32-security gem to latest (after string_to_sid fix)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1760 Update win32-security gem to latest (after string_to_sid fix) Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2656) FFI Puppet::Util::Windows::Registry
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2656 FFI Puppet::Util::Windows::Registry Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2656) FFI Puppet::Util::Windows::Registry
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2656 FFI Puppet::Util::Windows::Registry Change By: Joshua Cooper Labels: windows 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing Per discussion on #puppet-dev, I've downgraded from 3.6.1 to 3.6.0 to see if this stops memory growth. Downgrading also required disabled env dirs so there are two variables that have changed. Assuming this has indeed stopped the memory growth (it will take several hours to know), I believe the next step it to go back to 3.6.1 without enabling env dirs to see if the memory issues return. yum downgrade puppet-3.6.0 puppet-server-3.6.0 Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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
Jira (PUP-2698) Allow multiple hosts in 'host:dir for the mount device in the puppet mount type
Title: Message Title Edson Manners created an issue Puppet / PUP-2698 Allow multiple hosts in 'host:dir for the mount device in the puppet mount type Issue Type: Improvement Assignee: Unassigned Created: 29/May/14 12:48 PM Priority: Normal Reporter: Edson Manners For a mounted lustre FS in my production environment my fstab looks like this: 10.x.y.z1@o2ib:10.x.y.z2@o2ib:/boblstr /lustre lustre defaults,_netdev,flock,noauto 0 0 When I set the 'ensure' attribute to 'mount' in the mount type I get this error: err /Stage[main]/Customize::Lustre/Mount[lustre] Could not evaluate: Execution of '/bin/mount /lustre' returned 32: mount.nfs: remote share not in 'host:dir' format Obviously this line in the fstab works but now we have no redundancy: 10.x.y.z@o2ib:/boblstr /lustre lustre defaults,_netdev,flock,noauto 0 0 It would really help to have our redundant setup be able to be mounted by puppet with using an exec or reboot. Thanks. Please let me know if further information is needed. Add Comment
Jira (PUP-2660) purging ssh_authorized_key fails because of missing user value
Title: Message Title
Ethan Brown commented on an issue
Re: purging ssh_authorized_key fails because of missing user value
Verified reported issue under Ubuntu 14.04. Note for the sake of FR that if the given username does not exist on the system, the keys will not be purged, and output will be similar to the following:
root@998a248f96d2:/home/puppet# bundle exec puppet apply -e 'user { foo: purge_ssh_keys = /tmp/keytest,}'
Notice: Compiled catalog for 998a248f96d2.corp.puppetlabs.net in environment production in 0.07 seconds
Notice: /Stage[main]/Main/Ssh_authorized_key[foreman-122dc11d6-bd1e-43e7-a00d-f8e2d0af54ea]/ensure: removed
Error: /Stage[main]/Main/Ssh_authorized_key[foreman-122dc11d6-bd1e-43e7-a00d-f8e2d0af54ea]: Could not evaluate: User 'foo' does not exist
Notice: /Stage[main]/Main/Ssh_authorized_key[doug]/ensure: removed
Error: /Stage[main]/Main/Ssh_authorized_key[doug]: Could not evaluate: User 'foo' does not exist
Notice: Finished catalog run in 0.03 seconds
When using a name like root for a user that does exist, the keys are properly purged
root@998a248f96d2:/home/puppet# bundle exec puppet apply -e 'user { root: purge_ssh_keys = /tmp/keytest,}'
//.rbenv/plugins/rbenv-vars/bin/rbenv-vars: line 64: /dev/fd/62: No such file or directory
Notice: Compiled catalog for 998a248f96d2.corp.puppetlabs.net in environment production in 0.07 seconds
Notice: /Stage[main]/Main/Ssh_authorized_key[foreman-122dc11d6-bd1e-43e7-a00d-f8e2d0af54ea]/ensure: removed
Notice: /Stage[main]/Main/Ssh_authorized_key[doug]/ensure: removed
Notice: Finished catalog run in 0.04 seconds
root@998a248f96d2:/home/puppet# ls /tmp/keytest
/tmp/keytest
root@998a248f96d2:/home/puppet# cat /tmp/keytest
# HEADER: This file was autogenerated at 2014-05-29 06:55:34 +
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
Merged to stable for release in 3.6.2 as https://github.com/puppetlabs/puppet/commit/d6d98001fe224eb68adc065588f34aa673607ea5
Add Comment
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: A node can't always collect its own exported resources
Also, due to PUP-25, default parameters merged in during the finish stage don't have the same effect as parameters set directly on resources. The values get added to the parameters hash, but secondary effects such as the generation of tags never happen.
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
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
Jira (PUP-837) FFI Puppet::Util::Windows::SID module
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-837 FFI Puppet::Util::Windows::SID module Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg commented on an issue Re: 3.6.1 issues warning message for deprecation Okay after some more discussion we ended up with the idea of a --disable-warnings setting which could take a list of settings but currently only supports deprecations. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... 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 (FACT-545) Puppet specs on windows trigger Excluding C from search path. Fact file paths must be an absolute directory.
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-545 Puppet specs on windows trigger Excluding C from search path. Fact file paths must be an absolute directory. Issue Type: Bug Assignee: Eric Sorenson Created: 29/May/14 1:23 PM Fix Versions: 2.1 Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PUP-2699) Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-2699 Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory Issue Type: Bug Assignee: Unassigned Created: 29/May/14 1:29 PM Priority: Normal Reporter: Kylo Ginsberg Per Josh in HipChat: when using as_platform = 'posix' and running on windows we switch File::PATH_SEPARATOR to ':', which confuses facter on windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2699) Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2699 Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory Change By: Joshua Cooper Labels: windows 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/d/optout.
Jira (PUP-2699) Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2699 Puppet specs on windows triggers Excluding C from search path. Fact file paths must be an absolute directory Change By: Joshua Cooper Component/s: Client 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/d/optout.
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title Brice Figureau assigned an issue to Brice Figureau Puppet / PUP-2569 puppet cert revoke name doesn't always revoke what you expect Change By: Brice Figureau Assignee: ErikDaln BriceFigureau 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/d/optout.
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Tristan Smith created an issue
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
Issue Type:
Bug
Affects Versions:
3.6.1
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
29/May/14 2:23 PM
Environment:
Puppet 3.6.1 server, Puppet 3.6.1 client. Separate puppet server for catalog and puppet fileserver for this content, using passenger for both.
Priority:
Normal
Reporter:
Tristan Smith
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.
Here's a convenient, if ugly, example:
In the Fileserver: [29/May/2014:14:15:18 -0700] GET /production/file_content/puppet/python340/lib/python3.4/site-packages/setuptools/_pycache_/script%2520template%2520(dev).cpython-34.pyc HTTP/1.1 404 147
Jira (PUP-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title
Brice Figureau commented on an issue
Re: puppet cert revoke name doesn't always revoke what you expect
I'm taking ownership of this bug with Erik Daln permission
Add Comment
Puppet / PUP-2569
puppet cert revoke name doesn't always revoke what you expect
When revoking a certificate by name and there is not certificate by that name present (for instance if the certificates were deleted) the puppet cert command falls back to the {{inventory.txt}} file to find the serial number. When it does this it ends up only revoking the first serial number recorded in the file. This leaves the most recent certificate ...
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-2569) puppet cert revoke name doesn't always revoke what you expect
Title: Message Title
Brice Figureau commented on an issue
Re: puppet cert revoke name doesn't always revoke what you expect
Pushed at: https://github.com/puppetlabs/puppet/pull/2704
Add Comment
Puppet / PUP-2569
puppet cert revoke name doesn't always revoke what you expect
When revoking a certificate by name and there is not certificate by that name present (for instance if the certificates were deleted) the puppet cert command falls back to the {{inventory.txt}} file to find the serial number. When it does this it ends up only revoking the first serial number recorded in the file. This leaves the most recent certificate ...
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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
Change By:
Joshua Cooper
Thisone'snewonme.We'reusingfile{:recurse=remote}topulladirectorystructurefromaremotepuppetfileserver.Itwouldappearthatthere'samismatchcausingittomultiplyurlencoderesourcesit'srecursingover,causingittorenderaspace''as%2520inthefile_contentcall.Here'saconvenient,ifugly,example:IntheFileserver: {noformat} [29/May/2014:14:15:18-0700]GET/production/file_content/puppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%2520template%2520(dev).cpython-34.pycHTTP/1.1404147-- {noformat} intheclient: {noformat} Error404onSERVER:NotFound:Couldnotfindfile_contentpuppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pycError:/Stage[main]/.../File[/opt/python340/lib/python3.4/site-packages/setuptools/__pycache__/scripttemplate(dev).cpython-34.pyc]/ensure:changefromabsenttofilefailed:Couldnotset'file'onensure:Error404onSERVER:NotFound:Couldnotfindfile_contentpuppet/python340/lib/python3.4/site-packages/setuptools/__pycache__/script%20template%20(dev).cpython-34.pyc {noformat}
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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph of memory usage after downgrading from 3.6.1 - 3.6.0 Change By: Joshua Hoblitt Attachment: graph-day.png 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph of memory usage puppet 3.6.0 - 3.6.1 - 3.6.0 Change By: Joshua Hoblitt Attachment: graph-week.png 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing About 2 hours after the last restart of the puppet master on 3.6.0, the memory usage and grown much more slowly. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 16889 puppet20 0 624m 503m 4100 S 56.3 4.2 32:52.69 ruby 16734 puppet20 0 618m 496m 4100 S 0.0 4.2 31:25.72 ruby 17930 puppet20 0 613m 491m 4100 S 0.3 4.1 22:21.42 ruby 17921 puppet20 0 596m 476m 4100 S 0.3 4.0 29:30.85 ruby 19965 puppet20 0 576m 457m 4036 S 0.0 3.9 20:47.40 ruby 13824 puppet20 0 569m 448m 4100 S 0.3 3.8 14:12.90 ruby 20897 activemq 20 0 4381m 295m 3612 S 0.3 2.5 3:11.37 java 18123 puppet20 0 403m 281m 4100 S 0.3 2.4 14:20.57 ruby 13762 puppet20 0 400m 279m 4100 S 0.0 2.4 18:51.45 ruby 16530 foreman 20 0 615m 227m 4648 S 0.0 1.9 1:19.78 ruby 18009 foreman 20 0 615m 223m 4648 S 1.3 1.9 2:21.38 ruby 18081 foreman 20 0 628m 213m 4648 S 0.0 1.8 2:17.52 ruby 12089 foreman 20 0 614m 208m 4644 S 0.0 1.8 1:23.78 ruby Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB.
Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Tristan Smith commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
This appears to be server-side, as it did not manifest with puppet 3.4.3 server and does still happen with 3.4.3 clients.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
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-2635) user purge_ssh_keys not purged
Title: Message Title
Felix Frank commented on an issue
Re: user purge_ssh_keys not purged
So, apparently we can solve this by using generate instead of eval_generate in the user type. But I'd really like to know why.
Add Comment
Puppet / PUP-2635
user purge_ssh_keys not purged
I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys. I've added this code to my manifest: {code} user { 'ubuntu': purge_ssh_keys = true, home = '/home/ubuntu', } {code} However, no keys are purged. I do see the following lines in the agent debug output: {noformat} Debug: /Stage[main]/Role...
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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log mike jeski Rudy McComb Brian Wilkins Tamas Szasz Ronald Valente The error definitely originates on the agent side, so ignore my earlier comments about adding --debug and --trace to your puppet master. Part of the confusion is that if the puppet reports setting includes log, then the log messages from the client's report will be written into the master's syslog, as happened here: May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//hostname/Puppet) Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation This makes it appear as though the error came from the master, when in reality it came from hostname. Could you please update your comments to include the following information about your puppet agents only: ruby version puppet version linux distro(s), e.g. Ubuntu 12.04 LTS type of filesystems relevant to puppet, e.g. mount -l how did you install puppet, e.g. rpm, apt, yum, gem, source, etc are there multiple versions of puppet installed, e.g. as package (if so where from), as a gem, as tarball did the issue show up recently after updating puppet? If so, what version were you running previously? How did you update? using puppet itself, package manager, gem update? if you are able to reproduce the problem with a daemonized agent, can you add --trace to the script that launches puppet, e.g. on Ubuntu, edit /etc/default/puppet and restart the puppet service: DAEMON_OPTS=--trace
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing plot of puppet master CPU usage over the last week Change By: Joshua Hoblitt Attachment: graph-cpu-week.png 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/d/optout.
Jira (PUP-2661) Invalid parameter allow_virtual for puppet 3.6.1
Title: Message Title
Shaw Xiao commented on an issue
Re: Invalid parameter allow_virtual for puppet 3.6.1
Yes I have found some puppet clients have not been upgraded to puppet 3.6.1 automatically since they are not subscribed to our spacewalk puppet channel. Thanks for investigation.
Add Comment
Puppet / PUP-2661
Invalid parameter allow_virtual for puppet 3.6.1
I have both master and client puppet machine installed with 3.6.1. {code} Package { allow_virtual = true, } {code} If I put the above setting as release note (http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#puppet-361) suggested, I got error Error: Could not retrieve catalog from remote server: Error 400 on S...
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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph of 3.6.1 w/ env dirs - 3.6.0 w/o - 3.6.1 w/0 Change By: Joshua Hoblitt Attachment: graph-day.png 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/d/optout.
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title Felix Frank updated an issue Puppet / PUP-2635 user purge_ssh_keys not purged Change By: Felix Frank Fix Version/s: 3.6.2 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/d/optout.
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Doug Byrne commented on an issue
Re: user purge_ssh_keys not purged
I applied the patch and the resources are ensured absent. Combined with the patch from PUP-2660, it appears to be working. I tried it on both my minimal test, and on one of my normal hosts.
Add Comment
Puppet / PUP-2635
user purge_ssh_keys not purged
I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys. I've added this code to my manifest: {code} user { 'ubuntu': purge_ssh_keys = true, home = '/home/ubuntu', } {code} However, no keys are purged. I do see the following lines in the agent debug output: {noformat} Debug: /Stage[main]/Role...
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-2689) A node can't always collect its own exported resources
Title: Message Title
Henrik Lindberg commented on an issue
Re: A node can't always collect its own exported resources
I have now also looked at what happens when attempting to set tags via resource defaults.
As with all other defaults, assignment of the default value only takes place if the value is unset
Since the assignment of container inherited and automatic tagging always sets tags on a resource, the default has no effect on the resource itself. What is set in default never reached the resources.
Parameters of a resource are also tagged. They inherit the tags explicitly set on a resource (not what the resource itself inherits from its container / is auto generated)
Thus, the fix is to conduct the collection search using both explicit tags, and the tags that will be set in the resulting catalog. As these tags never include tags set via the resource default mechanism, we do not have to search those.
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
Jira (PUP-2701) Add acceptance tests for PMT build metadata.json support
Title: Message Title John Duarte created an issue Puppet / PUP-2701 Add acceptance tests for PMT build metadata.json support Issue Type: Task Assignee: Unassigned Created: 29/May/14 5:38 PM Priority: Normal Reporter: John Duarte Add acceptance tests to validate the `puppet module generate` command and its use of metadata.json and Modulefile deprecation. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title Felix Frank commented on an issue Re: user purge_ssh_keys not purged Got it now. It's a graph traversal order issue. The crux is Transaction#prefetch_if_necessary. It is invoked during the evaluation of prefetchable resources such as ssh_authorized_keys (parsedfile provider) or package. When using eval_generate, this can go wrong: package resource gets evaluated before user prefetch_if_necessary calls Transaction#resources_by_provider, populating its cache user gets evaluated and generates ssh_authorized_key resource generated key gets evaluated and calls prefetch_if_necessary key list from resources_by_provider is from cache, so the generated key is still missing provider has no resource to populate during prefetch Therefor it appears that the agent cannot find the resource it is supposed to purge. I stand by the option to use generate instead of eval_generate to avoid this issue. There shall be a discussion wether the described effect must be considered a bug in the transaction code. Even if not, it might be sensible to implement a workaround (to protect us from similar surprises in the future). Add Comment Puppet / PUP-2635 user purge_ssh_keys not purged
Jira (PUP-2701) Add acceptance tests for PMT build metadata.json support
Title: Message Title John Duarte commented on an issue Re: Add acceptance tests for PMT build metadata.json support Please review and merge PR 2709 if it meets with your approval. Add Comment Puppet / PUP-2701 Add acceptance tests for PMT build metadata.json support Add acceptance tests to validate the `puppet module generate` command and its use of metadata.json and Modulefile deprecation. 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-2687) File Names with ? cause failures with recursive copies
Title: Message Title
Kylo Ginsberg commented on an issue
Re: File Names with ? cause failures with recursive copies
Rmi this issue (with ?) seems to be an older issue, i.e. it pre-dates 3.5.1. The example you mentioned is apparently a regression between 3.5.1 and 3.6.1 and involves a space rather than a ?. If so, it may actually be PUP-2700.
Add Comment
Puppet / PUP-2687
File Names with ? cause failures with recursive copies
File names that contain ? cause runs to fail and reports that it can't find a file name by section before the ?, and seemingly drops the ? and anything after. Example code: pre file { '/tmp/foo': ensure = directory, recur...
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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
Charlie Sharpsteen if you get a chance to look at this one, that would be great. We had another report of this added as a comment to PUP-2687 but I think those are separate issues. If this one is a regression in the 3.6.x series, it would be nice to verify that.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
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
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x Woot, the latest run is clean of that nagging issue with with_supported_pe_version.rb and ran the gauntlet of CI infra snags: http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/87/#showFailuresLink There are 23 failures remaining. Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph showing 3.6.1 + env dir + environment_timeout = unlimited appearing to be memory stable. Change By: Joshua Hoblitt Attachment: graph.php.png 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing It's looking pretty good for 3.6.1 + environmentpath = $confdir/environments environment_timeout = unlimited Per prior discussion on #puppet-dev, I'm going to change the timeout to 180s for the rest of the night. Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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
