Jira (PUP-3542) Write statefile in JSON
Title: Message Title Mike Hall updated an issue Puppet / PUP-3542 Write statefile in JSON Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3544) Write lastrunreport in JSON
Title: Message Title Mike Hall updated an issue Puppet / PUP-3544 Write lastrunreport in JSON Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3543) Write lastrunfile in JSON
Title: Message Title Mike Hall updated an issue Puppet / PUP-3543 Write lastrunfile in JSON Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3541) Remove client and server yaml directories
Title: Message Title Mike Hall updated an issue Puppet / PUP-3541 Remove client and server yaml directories Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Puppet does make a distinction between warnings and errors, we can change the errors to warnings easily (and it is also easy to make them configurable). In the past we have erred on the side of being too permissive and people keep asking about having a strict mode. Being relaxed leads to sloppy, buggy programs. While I agree that this is a linting kind of thing, it has the unfortunate side effect of accepting gibberish programs: [1,2,3] [4,5,6] 1 2 3 ooops would be a valid Puppet Program if the validations are removed. Before we had this validation, we found that we made mistakes/typos that were not caught and it was difficult to spot the error (typically punctuation missing somewhere, a whitespace in the wrong place, a missing brace/bracket (while still having them balanced), etc.). Now, should we treat some expressions that have no effect differently? I am not so sure that is a good idea. The one possibly valid use case so far is the commenting out the body of an if when debugging case - I would argue that you can just as well comment out the entire if _expression_ (note that if the test _expression_ has effect; assigns to variable, makes a call or invokes any other _expression_ that may changes system state, then, conservatively the if _expression_ is considered to have effect, also, if there is an else part and it has effect, the then part can be empty). I think the very small cost of commenting out an extra line or two is a price worth paying since having the validation raise an error is likely to catch real mistakes in areas that those that are the least familiar with the language will make (and have a hard time finding the cause of), and will catch typos for the rest of us without having to search logs, turn on debugging flags etc. to find those problems.
Jira (PUP-3997) Audit and update puppet acceptance tests that assume the puppet user and group are present
Title: Message Title Josh Cooper commented on PUP-3997 Re: Audit and update puppet acceptance tests that assume the puppet user and group are present Merged in 22724996 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-380) Private ipaddress is used as ipaddress fact
Title: Message Title Jason Hane commented on FACT-380 Re: Private ipaddress is used as ipaddress fact This is a huge showstopper but an easy fix. I agree with using the default route's IP address. I think that is the most logical solution. Can we get a commitment for resolution? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-380) Private ipaddress is used as ipaddress fact
Title: Message Title Jason Hane updated an issue Facter / FACT-380 Private ipaddress is used as ipaddress fact Change By: Jason Hane Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4058) autoload.loadall does not use current environment
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4058 autoload.loadall does not use current environment Change By: Kylo Ginsberg Component/s: CatalogApplication Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4058) autoload.loadall does not use current environment
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Henrik Lindberg you may have more context on this. Puppet / PUP-4058 autoload.loadall does not use current environment Change By: Kylo Ginsberg Assignee: KyloGinsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-155) PostgreSQL Tuning Guide
Title: Message Title Mike Hall updated an issue PuppetDB / PDB-155 PostgreSQL Tuning Guide Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2080) Support functions written in pp
Title: Message Title Mike Hall updated an issue Puppet / PUP-2080 Support functions written in pp Change By: Mike Hall Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1271) PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug
Title: Message Title gepetto-bot commented on PDB-1271 Re: PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/751/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hello, Wyatt Alt. We already raised the limit. What we seeing is: du -sh /var/lib/puppetdb/mq/localhost/* 4.2M /var/lib/puppetdb/mq/localhost/KahaDB 33G /var/lib/puppetdb/mq/localhost/scheduler while [command-processing] store-usage = 10240 temp-usage = 5120 and exceptions like this: 2015-02-22 05:44:29,330 WARN [o.a.a.b.T.Service] Async error occurred: java.lang.IllegalStateException: PageFile is not loaded
Jira (PUP-4053) puppet always returns an empty catalogue when is default_manifest =
Title: Message Title Henrik Lindberg commented on PUP-4053 Re: puppet always returns an empty catalogue when is default_manifest = Also, if you got debug output that the catalog was empty, that does not really tell you anything about the cause. Would some other debug output have helped you find the problem faster? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker senior commented: @ajroetker needs a rebase Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4054
create_resources() error messages are less useful in 3.x then they were in 2.x
Change By:
Henrik Lindberg
When{{create_resources()}}functioncausespuppetlogictobeevaluated,certainerrorsarenotdisplayedwiththepuppetcontext(file/line)thattheyappearin.Thiscanbeobservedwiththissimplesample:{code}classbreaking{$x='foo'+'bar'}$classes={'breaking'={}}create_resources('class',$classes){code}TheresultonPuppet3.7.4(withcurrentparser)is:{code}Error:leftoperandof+isnotanumberat/Users/henrik/git/puppet/foo.pp:5onnode...{code}TheresultwithPuppet3.7.4(withfutureparser)andpuppet4.0.0is:{code}Error:EvaluationError:Thevalue'foo'cannotbeconvertedtoNumeric.at/Users/henrik/git/puppet/foo.pp:2:8onnode...{code}Thus,theproblemisatleastfixedinnewerversions.ORIGINALREPORT InPE2.8(Puppet2.7.x)thisfunctionwillshowthefile/linenumberdetailofthePuppetDSLcodewheretheexceptionoccurred.InPE3.x(includingPE3.7/Puppet3.7)itshowsthefile/linenumberofthePuppetDSLwherethecreate_resources()functionwasinvoked-whichisnothelpful.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Henrik Lindberg commented on PUP-4054 Re: create_resources() error messages are less useful in 3.x then they were in 2.x There is no simple work around that I can think of. There is also no simple fix since pinning down all cases where errors are raised in a context without associating them with file/line (and re-raising an error with this information) is a time consuming effort that may easily miss corner cases. The future parser implementation has one place only that raised errors pass through but this is not the case for the 3x current implementation. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Henrik Lindberg commented on PUP-4054 Re: create_resources() error messages are less useful in 3.x then they were in 2.x It was kind of difficult at first to figure out what the loss of fidelity is about - is it when creating resources that in turn means evaluating puppet code? i.e. something like this: puppet code a = create_resources(...) = puppet code b Such as an error in 'puppet code b' is caught and reported as an error in the evaluation of create_resources ? Not sure if this can occur for anything but classes since other resources are lazily evaluated, but I can imagine that there are some checks in place that could raise errors when the request is made to later evaluate a resource. (It looks like the reported use case is for classes). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1259) Specify specific date format when converting from string to DateTime
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-1259 Specify specific date format when converting from string to DateTime Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4033) add puppet-agent path acceptance tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4033 add puppet-agent path acceptance tests Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4037) Windows AIO path changes
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-4037 Windows AIO path changes Change By: Josh Cooper Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4037) Windows AIO path changes
Title: Message Title Josh Cooper commented on PUP-4037 Re: Windows AIO path changes CI passed and builds promoted to http://nightlies.puppetlabs.com/puppet-agent/1d70ebfbb804228080dcbc29e81810f70eb702fa/repos/windows/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1259) Specify specific date format when converting from string to DateTime
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1259 Specify specific date format when converting from string to DateTime Change By: Ryan Senior Sprint: PuppetDB2015-03- 25 11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker ajroetker commented: @senior rebased! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone assigned an issue to QA Puppet / PUP-4001 Packaging should create default module directories for puppet Change By: Melissa Stone Status: Readyfor CI Test Assignee: MelissaStone QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3043) 100% CPU usage
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3043 100% CPU usage Change By: Henrik Lindberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2023) Debian/Ubuntu service provider improvements
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2023 Debian/Ubuntu service provider improvements Change By: Kylo Ginsberg Scrum Team: ReleaseEngineering Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4053) puppet always returns an empty catalogue when is default_manifest =
Title: Message Title Igor Galić created an issue Puppet / PUP-4053 puppet always returns an empty catalogue when is default_manifest = Issue Type: Bug Assignee: Unassigned Created: 2015/02/27 4:46 AM Priority: Normal Reporter: Igor Galić this was really unintuitive and hard to debug. especially because of our infrastructure specific red-herring of: all data comes from hiera, we're not seing a single hiera() call in the debug log. this must be it! well it wasn't. puppet was ignoring our other (directoryenvironment, et al) directives entirely because, because it was looking for the manifests dir in… i don't even know where… i'm not sure this behaviour is useful, although it really speeds up catalogue compiles and puppet runs… when the catalogue is entirely empty… it can also not break anything… but it would really be useful to error out instead btw, this behaviour is consistent between puppetserver and puppetmaster (3.7.4) Add Comment
Jira (PUP-3043) 100% CPU usage
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3043 100% CPU usage Change By: Henrik Lindberg Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Can not really warn on the space because it is ambiguous - it would issue false positives. Agree that non productive is a not a very self explanatory phrase. Open to suggestions. We considered empty-_expression_, _expression_ without effect, (it is not meaningless - we do understand it), vacuous _expression_, void _expression_ (but associates more to _expression_ not resulting in a value, which is not the case here, there may be a value, but that value is immediately thrown away), discarded value _expression_, unproductive, useless, worthless, unworthwhile, unreasonable (as in 'you cannot possibly mean that...'). Tyler Pace Nicholas Fagerlund - any thoughts on this? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2023) Debian/Ubuntu service provider improvements
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-2023 Debian/Ubuntu service provider improvements Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4053) puppet always returns an empty catalogue when is default_manifest =
Title: Message Title Henrik Lindberg assigned an issue to Igor Galić Puppet / PUP-4053 puppet always returns an empty catalogue when is default_manifest = Change By: Henrik Lindberg Assignee: IgorGalić Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2023) Debian/Ubuntu service provider improvements
Title: Message Title Apollon Oikonomopoulos updated an issue Puppet / PUP-2023 Debian/Ubuntu service provider improvements The patch by Gaudenz made it to the Debian package, but some fixes are still needed for the service enable/disable logic. The attached patch fixes the enable/disable logic by checking what the running init is and taking the appropriate actions using either systemctl, or invoke-rc.d/update-rc.d. For more info on why this is actually needed, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775795#84 Change By: Apollon Oikonomopoulos Attachment: 0001-Fix-service-listing-and-enable-disable-in-Debian.patch Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4053) puppet always returns an empty catalogue when is default_manifest =
Title: Message Title Henrik Lindberg commented on PUP-4053 Re: puppet always returns an empty catalogue when is default_manifest = Not sure what you are asking for here. Sounds like you want debugging output of something, but what exactly? Empty catalog? I don't think we want to make an empty catalog an error. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4034) Update MSI for AIO
Title: Message Title Ethan Brown assigned an issue to Rob Reynolds Puppet / PUP-4034 Update MSI for AIO Change By: Ethan Brown Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1269) Extractable only fields are not supported in the query_eng/engine.clj
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1269 Extractable only fields are not supported in the query_eng/engine.clj Issue Type: Bug Assignee: Unassigned Created: 2015/02/27 10:07 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: AJ Roetker The query engine currently validates extractable fields by checking the `:queryable-fields` for the queries in there, which means we cannot subselect on report-logs|metrics|events (extractable but not queryable because they are stored as text/json). A reasonable solution for things in their current form (as of writing this ticket) would probably consist of have `:queryable` `:queryable-only` and `:extractable-only` keys for each query that needs them and preform validation using those subsets. Add Comment
Jira (PUP-4041) Investigate DSC's Invoke-DSCResource
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-4041 Investigate DSC's Invoke-DSCResource Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4034) Update MSI for AIO
Title: Message Title Ethan Brown assigned an issue to Rob Reynolds Puppet / PUP-4034 Update MSI for AIO Change By: Ethan Brown Assignee: EthanBrown RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4034) Update MSI for AIO
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-4034 Update MSI for AIO Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-400) Manage hidden windows packages
Title: Message Title Rob Reynolds assigned an issue to Unassigned Puppet / PUP-400 Manage hidden windows packages Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4034) Update MSI for AIO
Title: Message Title Ethan Brown commented on PUP-4034 Re: Update MSI for AIO Latest builds from AIO pipeline to test with are at: http://builds.puppetlabs.lan/puppet-agent/1d70ebfbb804228080dcbc29e81810f70eb702fa/nightly_repos/windows/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I created a sample gist to auto setup a puppet dev environment on windows. It could require a few more tweaks but it was created to suit my needs. This is useful for bootstrapping an environment. https://gist.github.com/logicminds/fa774e01862ef3ae1156 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone commented on PUP-4001 Re: Packaging should create default module directories for puppet This was verified in http://builds.puppetlabs.lan/puppet-agent/1d70ebfbb804228080dcbc29e81810f70eb702fa/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4055) Support DNF package manager (yum successor)
Title: Message Title Hunter Haugen created an issue Puppet / PUP-4055 Support DNF package manager (yum successor) Issue Type: New Feature Assignee: Unassigned Created: 2015/02/27 11:00 AM Priority: Normal Reporter: Hunter Haugen Fedora 22 is moving from yum to DNF for its package management (http://www.phoronix.com/scan.php?page=news_itempx=Fedora-22-Alpha-Features) https://github.com/rpm-software-management/dnf We should add support for this with a new package provider. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg commented on PUP-4047 Re: consider 'non productive _expression_' to be warning _expression_ has no effect works. (Will wait a while for additional comments, but I am inclined to just change to that). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Greg Sarjeant commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Would _expression_ has no effect work, or is there a distinction between that and a non-productive _expression_ that makes that wording inappropriate? That phrasing is a bit more self-explanatory, and googling it returns results from other languages which would help people to frame their debugging (Oh, strange, that code should have done something, I wonder what's causing ... oops, I bet it's that space between the variable and the bracket.), if it's not obvious from the message and the line number. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Lee Lowder created an issue Puppet / PUP-4054 create_resources() error messages are less useful in 3.x then they were in 2.x Issue Type: Bug Assignee: Unassigned Created: 2015/02/27 7:20 AM Labels: support customer Priority: Normal Reporter: Lee Lowder In PE 2.8 (Puppet 2.7.x) this function will show the file/line number detail of the Puppet DSL code where the exception occurred. In PE 3.x(including PE 3.7 / Puppet 3.7) it shows the file/line number of the Puppet DSL where the create_resources() function was invoked - which is not helpful. Add Comment
Jira (PDB-694) Retire short name http stat querying in metrics
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-694 Retire short name http stat querying in metrics Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1225) Update fact storage and querying to use the new path column in the facts table
Title: Message Title Ryan Senior commented on PDB-1225 Re: Update fact storage and querying to use the new path column in the facts table There's two pieces to this, updating storage and updating queries. I can't test this (unless I dummy a bunch of data) until the storage is done, but there's a commit here with the changes we'll need on the query side. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title
Henrik Lindberg commented on PUP-4047
Re: consider 'non productive _expression_' to be warning
Just changed the two error messages to this:
This #{label.label(semantic)} has no effect. A value producing _expression_ without other effect may only be placed last in a block/sequence
This #{label.label(semantic)} has no effect. #{label.a_an_uc(container)} can not end with a just a value producing _expression_
The first is the general case, the second when placing a value _expression_ last in something like a class or define - e.g.
define foo() {
# ...
3
}
Can change them again if someone comes up with better ideas.
Jira (PUP-4056) Audit acceptance tests for assumed ruby location
Title: Message Title John Duarte created an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location Issue Type: Task Assignee: John Duarte Created: 2015/02/27 12:18 PM Priority: Normal Reporter: John Duarte Acceptance tests should not assume that ruby is in a particular location. Example agent['puppetbindir']/ruby /usr/bin/ruby /usr/bin/env ruby Tests making this assumption need to be identified.
Jira (PUP-4034) Update MSI for AIO
Title: Message Title Rob Reynolds commented on PUP-4034 Re: Update MSI for AIO So the only thing I've noticed is that it doesn't clean up the older hiera directory. Should we put in code to move/remove the older hiera.yaml file? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Tyler Pace commented on PUP-4047 Re: consider 'non productive _expression_' to be warning I agree with Greg Sarjeant recommendation. 'has no effect' is wonderfully self-explanatory and also sidesteps issuing any particular judgments about the _expression_ in question. I'm probably exposing my own lack of knowledge here, but how would this message be presented to the user? Is it an 'Error' or a 'Warning'? I don't know if Puppet 4 makes those distinctions, but if it does then I would suggest 'Warning'. Error implies that the code they just tried to compile is more or less non-functional, but I can see a lot of situations where users are actively debugging or fleshing out their code and have empty 'if' statements, functions with no logic, etc. This is the stuff that a user would typically check via a linter and might safely ignore depending on the context of their work, but because it's possible for some non productive expressions in Puppet 4 to have an impact beyond poor syntax or style then we probably shouldn't rely on optional linting to surface the warning. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4034) Update MSI for AIO
Title: Message Title Josh Cooper commented on PUP-4034 Re: Update MSI for AIO Migration is going to be handled later, the start of which is PUP-3884, though there will likely be many tickets filed to make that actually work Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1254) move latest_report to the certnames table
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1254 move latest_report to the certnames table Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1192) Metrics: Get metrics storage and retrieval working
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1192 Metrics: Get metrics storage and retrieval working Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-298) Update FS layout for hiera
Title: Message Title Josh Cooper commented on HI-298 Re: Update FS layout for hiera Hiera specs and acceptance passed in both pipelines, including promoting rhel7 and win2012r2 to nightlies. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1271) PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug
Title: Message Title gepetto-bot commented on PDB-1271 Re: PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug haus commented: :+1: Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4057) Acceptance tests should not rely on the puppetpath beaker option
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-4057
Acceptance tests should not rely on the puppetpath beaker option
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/02/27 3:54 PM
Labels:
AIO
Priority:
Normal
Reporter:
Josh Cooper
Several acceptance tests rely on puppetpath for both code and configuration related paths. Historically that setting was the same as puppetconfdir, but with the code/config split, it no longer makes sense.
The acceptance tests should be updated to:
Use beaker's host.puppet['setting'] methods so the test doesn't depend on hard-coded beaker default
Query for codedir or confdir as appropriate.
Take into account the agent vs master application, e.g. host.puppet('master')['confdir']
Jira (PUP-4057) Acceptance tests should not rely on the puppetpath beaker option
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4057 Acceptance tests should not rely on the puppetpath beaker option Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4058) autoload.loadall does not use current environment
Title: Message Title Matt Coffey created an issue Puppet / PUP-4058 autoload.loadall does not use current environment Issue Type: Bug Affects Versions: PUP 3.6.2 Assignee: Kylo Ginsberg Components: Catalog Application Created: 2015/02/27 3:59 PM Environment: OEL 6.5, running puppet master 3.6.2 Priority: Normal Reporter: Matt Coffey According to puppet custom function documentation, if one wanted to call a custom function from within another custom function, `Puppet::Parser::Functions.autoloader.loadall()` is required first. While creating a function library I noticed that older versions of my functions were being run even when restarting my master server. Upon further digging and running puppet from source, I found a few things: 1. It appears that in lib/puppet/util/autoload.rb, line 131 (acd5fd0 Merge branch 'PUP-2478/3.6.1/security_fixes' into stable) `env` is not getting set to the current_environment. 2. A good workaround for me is to use `Puppet::Parser::Functions.autoloader.load(:function)`, although this
Jira (PDB-1270) PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug
Title: Message Title gepetto-bot commented on PDB-1270 Re: PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/750/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2929) Optimize the (function) loader
Title: Message Title Henrik Lindberg assigned an issue to QA Puppet / PUP-2929 Optimize the (function) loader Change By: Henrik Lindberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Henrik Lindberg assigned an issue to QA Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Henrik Lindberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg assigned an issue to QA Puppet / PUP-4017 Make parser an environment specific setting Change By: Henrik Lindberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg assigned an issue to QA Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4047 consider 'non productive _expression_' to be warning Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4047 consider 'non productive _expression_' to be warning Change By: Henrik Lindberg Sprint: Language2015-03- 18 04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg assigned an issue to QA Hiera / HI-274 :merge_behavior with deep_merge gem missing should error instead of falling back Change By: Henrik Lindberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4001) Packaging should create default module directories for puppet
Title: Message Title Josh Cooper commented on PUP-4001 Re: Packaging should create default module directories for puppet The workarounds we had in place were removed in https://github.com/puppetlabs/puppet/commit/b8e567e1ec521d09df058a254f1e2e19cd27f452. Once that goes through, we can mark this as resolved. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4041) Investigate DSC's Invoke-DSCResource
Title: Message Title Ethan Brown commented on PUP-4041 Re: Investigate DSC's Invoke-DSCResource Notes from call WMF 5.0 Feb now available : New cmdlet: Invoke-DscResource Allows external invocation of DSC resources Doesn't go through LCM at all Access individual methods of resource w/ verbose message stream. IE call Set/Get and receive verbose output. Q: Is output structured? A: if invoked via CIM, you get a CIM object back. Powershell returns verbose stream (unstructured) Seems like Puppet would prefer to use the cmdlet for flexibility. also: classes in Powershell! powershell Get - try out find-DscResource Puppet wants to build a module to enable integration with DSC DSC wants to make sure this cmdlet suits Puppet's purposes - please check it out and give us feedback! The sooner the better - within the next 4weeks is prime
Jira (PDB-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker Pull request (maint) Add =-after? macro for import/export testing has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1270) PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug
Title: Message Title gepetto-bot commented on PDB-1270 Re: PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug Pull request (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1270) PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug
Title: Message Title gepetto-bot commented on PDB-1270 Re: PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug shrug commented: Oops, opened against the wrong branch Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1271) PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1271 PR (1287): (re-4060)(packaging) Update terminus install paths for puppet 4 - shrug Issue Type: Task Assignee: Unassigned Created: 2015/02/27 3:43 PM Labels: github Priority: Normal Reporter: gepetto-bot (re-4060)(packaging) Update terminus install paths for puppet 4 Author: Rob Braden Company: Puppet Labs Github ID: shrug Pull Request 1287 Discussion Pull Request 1287 File Diff Pull Request Description Update the terminus installation path for puppet 4 to match the paths specified at https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md, changing agent/ to puppet/
Jira (PDB-1266) All report hashes need to be recomputed during 3.0.0 upgrade
Title: Message Title Wyatt Alt commented on PDB-1266 Re: All report hashes need to be recomputed during 3.0.0 upgrade In the non-HA case I can't see this being an issue, since the only requirement we place on report hashes is that they be unique. We don't use them for diffing like factsets and catalogs. In the HA case the concern is that pre-existing PuppetDB A syncs to new PuppetDB B, and the two end up with identical reports that are hashed differently. I think we may have the same issue with factsets (now that timestamps have been removed from the hash) and catalogs (now that we use certname instead of name). These are more transient because we don't store historical data, but could cause confusion during upgrade. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4037) Windows AIO path changes
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4037 Windows AIO path changes Change By: William Hopper Assignee: QA WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1246) Add V3 API deprecation message
Title: Message Title Brian LaMetterey assigned an issue to Brian LaMetterey PuppetDB / PDB-1246 Add V3 API deprecation message Change By: Brian LaMetterey Assignee: WyattAlt BrianLaMetterey Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Ethan Brown commented on PUP-4050 Re: Acceptance suite and install.rb use incorrect paths on Windows for codedir Acceptance runs succeeded with these changes using MSI packages in the AIO pipeline. Prior to resolution, we should verify that git based acceptance runs work OK with the changes made to install.rb. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4037) Windows AIO path changes
Title: Message Title William Hopper commented on PUP-4037 Re: Windows AIO path changes Functional review using the x64 MSI from http://nightlies.puppetlabs.com/puppet-agent/1d70ebfbb804228080dcbc29e81810f70eb702fa/repos/windows/: Looks good! PS C:\Program Files\Puppet Labs\Puppet\binpuppet agent --configprint codedir C:/ProgramData/PuppetLabs/code PS C:\Program Files\Puppet Labs\Puppet\binpuppet agent --configprint hiera_config C:/ProgramData/PuppetLabs/code/hiera.yaml PS C:\Program Files\Puppet Labs\Puppet\binpuppet agent --configprint confdir C:/ProgramData/PuppetLabs/puppet/etc PS C:\Program Files\Puppet Labs\Puppet\binpuppet agent --configprint vardir
Jira (PDB-1270) PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1270 PR (1286): (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ - shrug Issue Type: Task Assignee: Unassigned Created: 2015/02/27 3:25 PM Labels: github Priority: Normal Reporter: gepetto-bot (re-4060)(packaging) Update puppet 4 paths to match the change from agent/ to puppet/ Author: Rob Braden Company: Puppet Labs Github ID: shrug Pull Request 1286 Discussion Pull Request 1286 File Diff Pull Request Description Update the terminus installation path for puppet 4 to match the paths specified at https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md, changing agent/ to puppet/
Jira (PUP-4041) Investigate DSC's Invoke-DSCResource
Title: Message Title Rob Reynolds commented on PUP-4041 Re: Investigate DSC's Invoke-DSCResource First large issue - Invoke-DSCResource requires the LCM to be in RefreshMode='Disabled' or it won't even run. Second issue - Changing any settings to the LCM cannot be done on the command line completely. It requires applying a dsc configuration file that applies the settings. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
