Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Henrik Lindberg commented on PUP-3985 Re: With `storeconfigs = false` there are no warnings or errors about exported resources I cannot reproduce this: Which version of puppet are you seeing this on? How can the problem be reproduced? puppet apply -e 'File | | ' results in Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored at line 1:1 Warning: Not collecting exported resources without storeconfigs If I set storeconfigs = false in master section in puppet.conf I get the same result. The above is tested on master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3985 With `storeconfigs = false` there are no warnings or errors about exported resources Change By: Henrik Lindberg 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-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3985 With `storeconfigs = false` there are no warnings or errors about exported resources Change By: Henrik Lindberg 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 (PUP-3991) scanf only implemented for future parser
Title: Message Title David Schmitt created an issue Puppet / PUP-3991 scanf only implemented for future parser Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/02/10 7:21 AM Priority: Normal Reporter: David Schmitt The scanf function is only implemted or the future parser, but not the classic one. This leads to the possibility of non-backwards compatible code using this function. As the implementation is trivial, I'd suggest adding the function to the classic parser. Alternatively, the function could be extracted into the stdlib module, where consumers can take a versioned dependency. Add Comment
Jira (PUP-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position Again our old friend Ruby 1.8.7 gives us surprises. The solution does not work there because ruby recreates the Proc rather than passing it by reference. This means that information is lost. Since we want to have the same API on 3.7.x and 4.0.0 we needed to come up with a solution for Ruby 1.8.7. The problem is that when a Proc is used to carry information, it has no access to detailed information about the closure since the information about arity and parameters is derived from the puppet evaluator closure. All we have in Ruby 1.8.7 is the arity, and this arity is hardcoded into how Proc works. In practice, it is (currently) only the slice function that introspects the arity of the block. If users write 4x functions that need this, they need to be aware of the differences between Proc in Ruby 1.8 and later (where Proc has richer support - it has correct arity and knows the names of the parameters, and we can return the puppet evaluator closure). The caveat for Ruby 1.8.7 implementations seems like a reasonable trade off as the alternatives are that the API is radically different between 3x with future parser and 4.0.0 when it comes to calling and introspecting code blocks. Now there is only a small difference motivated by the difference in ruby itself. Users of functions naturally does not see the change at all Implementors of functions should change to using yield and implict blocks if they have written functions accepting blocks. (ping Charlie Sharpsteen, Erik Daln) this has better performance it easier to write tests since a ruby block can be given instead of a Puppet evaluator closure (and those are somewhat elaborate to create in tests). Add Comment
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) 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-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Henrik Lindberg assigned an issue to Zachary Stern Puppet / PUP-3985 With `storeconfigs = false` there are no warnings or errors about exported resources Change By: Henrik Lindberg Assignee: ZacharyStern 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-774) $::augeasversion empty : puppet 2.7.19, facter 2.3.0, augeas 1.3.0
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-774 $::augeasversion empty : puppet 2.7.19, facter 2.3.0, augeas 1.3.0 Change By: Kylo Ginsberg Fix Version/s: FACT2.3.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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Matthaus Owens commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Jeff McCune It's where the shared puppet ruby code that the puppetserver service uses lives. I believe puppetserver (the uberjar) would live upder /opt/puppetlabs/server in this world. (Rob Braden Eric Sorenson correct me if I'm misstating here). 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Yes that's correct 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-3991) scanf only implemented for future parser
Title: Message Title David Schmitt commented on PUP-3991 Re: scanf only implemented for future parser Just created https://github.com/puppetlabs/puppet/pull/3593 Fast enough? 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-3982) Ensure puppet service supports conditional restart
Title: Message Title Branan Purvine-Riley commented on PUP-3982 Re: Ensure puppet service supports conditional restart I based this on nate wolfe's branch, but he doesn't want to merge it in (trying to keep his branch focused on just making things work). Once his code is merged I'll rebase this and open a PR against puppetlabs master 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-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Eric Thompson or Kurt Wall just a heads up that this ticket seems like a candidate for an acceptance test (spec tests can't really test the user contract here) to ensure we don't regress. 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg commented on PUP-3991 Re: scanf only implemented for future parser What, almost 4 minutes ?! Looks good - added comment on the PR about a quirk in how documentation for the function reference guide is generated. Great if you can fix 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Branan Purvine-Riley updated an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Branan Purvine-Riley Issue Type: Bug Task 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg 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 (PUP-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params Linking to some things also dealing with true/false/nil, it appears to my uneducated eyes that similar issues have cropped up before. 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg Fix Version/s: PUP3.7.5 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg Sprint: Language2015-02-18 Story Points: 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-3992) yaml nulls break data binding for class params
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-3992
yaml nulls break data binding for class params
Change By:
Christopher Wood
Assumingthisclass:classtesting::cwood1($param1){#stuff}Andhavingayamlnullinmyhieradata,orakeywithnovalue,likeeitherofthese:testing::cwood1::param1:nulltesting::cwood1::param1:~testing::cwood1::param1:Igeterrorsabouthowtheclassneedsaparameter.Feb1011:14:05puppetmaster2devpuppet-master[7546]:Mustpassparam1toClass[Testing::Cwood1]at/etc/puppet/environments/production/modules/testing/manifests/init.pp:3onnodept1.me.comWithanexplicitlyemptystringIdonotseethiserror,theclassparameterisaccepted.testing::cwood1::param1:''Theproblemisthattheclassdoesn'tpickuphowI'vedefinedthehierakeytesting::cwood1::param1.NeverthelessthekeyisthereandIampassingsomething,evenifIampassingarepresentationofnothing.Iexpectedthatthismighthavethesameresultasdoing$param1=undefsincetheundefthereistheclosestthinginpuppettorubynil,yamlnull.Thatsaid,thereareanumberofinterestingticketsabouttrue/truthy/false/nilhandlingandIwilllinkthoseheresinceit'sprobablyasubsetofthoseissues.Further,astraightcommand-linehieralookupappearstorepresenttheseasnil. a [root@puppetmaster2dev~]#greptesting::cwood1::param1/etc/puppet/environments/production/hieradata/nodes/pt1.me.com.eyamltesting::cwood1::param1:null[root@puppetmaster2dev~]#hieratesting::cwood1::param1environment=productionfqdn=pt1.me.comnil[root@puppetmaster2dev~]#greptesting::cwood1::param1/etc/puppet/environments/production/hieradata/nodes/pt1.me.com.eyamltesting::cwood1::param1:~[root@puppetmaster2dev~]#hieratesting::cwood1::param1environment=productionfqdn=pt1.me.comnilAquickyamlreadpickstheseupasnil,aswell.#!/usr/bin/envrubyrequire'pp'require'yaml'data=File.read(ARGV[0])yaml=YAML.load(data)ppyamlYAMLnulls:http://yaml.org/type/null.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3993) PMT Acceptance Test Failure in CI
Title: Message Title Ryan Gard created an issue Puppet / PUP-3993 PMT Acceptance Test Failure in CI Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Ryan Gard Components: PMT Created: 2015/02/10 9:48 AM Priority: Blocker Reporter: Ryan Gard The tests/modules/build/build_ignore_module_file.rb PMT acceptance test is failing. Currently it appears to be a behavior change in PMT itself that is causing the problem. Add Comment
Jira (PUP-3991) scanf only implemented for future parser
Title: Message Title David Schmitt commented on PUP-3991 Re: scanf only implemented for future parser Updated the PR 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-3992) yaml nulls break data binding for class params
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-3992
yaml nulls break data binding for class params
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Unassigned
Created:
2015/02/10 8:39 AM
Environment:
puppetmaster runs on:
[root@puppetmaster2dev ~]# cat /etc/redhat-release CentOS release 6.2 (Final) [root@puppetmaster2dev ~]# rpm -qa | egrep '^(puppet|hiera)' puppet-3.7.2-1.el6.noarch hiera-eyaml-1.3.4-1.el6.re.noarch hiera-1.3.4-1.el6.noarch puppetdb-terminus-2.2.2-1.el6.noarch
Priority:
Normal
Reporter:
Christopher Wood
Assuming this class:
class testing::cwood1 ( $param1 ) { # stuff }
And having a yaml null in my hieradata, or a key with no value, like either of these:
testing::cwood1::param1: null testing::cwood1::param1: ~ testing::cwood1::param1:
I get errors about how the class needs a parameter.
Feb 10 11:14:05 puppetmaster2dev puppet-master[7546]: Must pass param1 to Class[Testing::Cwood1] at /etc/puppet/environments/production/modules/testing/manifests/init.pp:3 on node pt1.me.com
With an
Jira (HI-46) Hiera should support alternate environments
Title: Message Title David Chute commented on HI-46 Re: Hiera should support alternate environments Is this really a bug in the enterprise pricing model? As far as I can tell if you want to make guaranteed safe changes to the hiera backend (or indeed your enc, if you have one) then IMO you are best off having a separate puppetmaster per environment. This gives you a place to test changes to hiera (and enc) before rolling out onto higher environments, then eventually live. With a few soft links and multiple puppermaster service definitions you can probably easily have this in one environment, but why would you do that? Do you really want the new guy applying a change to your dev hiera/modules/enc on the same server as you host your live code. And how do you test OS patch updates to the puppetmaster server itself without multiple puppetmasters? We are aiming for the same release process for puppetmaster and related modules and config as we have for any other application in our organisation. So we can take a tagged version from SVN, build it into a tar file, and promote the same tar file through the environments. Then looking in SVN, hiera is then the only place that has environment specific information. Do organisations put all environments onto one box because of costs associated to the Enterprise pricing model? I appreciate this seems to go against the vision of Puppet 4.0, but I personally think the vision is either flawed or I have misunderstood it. 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
Jira (PUP-3845) Windows Unified Installer should track internal component versions
Title: Message Title Rob Reynolds assigned an issue to Ryan Gard Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Rob Reynolds Assignee: RyanGard 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-3845) Windows Unified Installer should track internal component versions
Title: Message Title Ryan Gard commented on PUP-3845 Re: Windows Unified Installer should track internal component versions I'm currently busy with end of sprint activities, but I will FR this ticket sometime tomorrow. 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-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params Related thread: https://groups.google.com/forum/#!topic/puppet-users/0l3m4VCHjOg 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg commented on PUP-3991 Re: scanf only implemented for future parser It is fine to add it as a 3x function - if future parser is used (or in 4.0.0) the 4x implementation will be selected instead of the 3x version. David Schmitt if you are fast with a PR with a 3x implementation it will make it into 3.7.5. I think this is better than adding it to stdlib since the 4x version lives in puppet. 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3991 scanf only implemented for future parser 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-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title
Karmo Rosental updated an issue
Puppet / PUP-3480
Puppet does not have Python 3 package provider (pip3)
Change By:
Karmo Rosental
Thereisnowaytoinstallpython3packageinpuppetwithoutlongexecblocksorsomeotherhacks.Python2packageproviderispresentinPuppetandworkswell.Python2packageproviderinPuppetmaster:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip.rbOpenstack-InfrahavemadePython3providerthatbasesonPython2provider:https://github.com/openstack-infra/ config puppet-pip /blob/master/ modules/pip/ lib/puppet/provider/package/pip3.rbItestedPython3packageproviderfromopenstack-infrawithfollowingmanifestanditworked:package{['django==1.7']:ensure=present,provider=pip3,require=Package['python3-pip'],}package{['uwsgi==2.0']:ensure=present,provider=pip3,require=Package['python3-pip'],}
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-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Kenneth Barber commented on PDB-1136 Re: communicate v4 API changes to stakeholders ahead of release One idea, is that we could start to write up the release notes now for master. And as we do major changes like this, we could just update that doc as part of the patch. This is something I've been considering for a while as a better way to incrementally do release notes (as opposed to at release time), and since we have automatic updating of the docs website for master, it can be quite presentable: https://docs.puppetlabs.com/puppetdb/master/release_notes.html You can see a reasonable example of how we did this for the new features in 2.2.0 for example: https://docs.puppetlabs.com/puppetdb/master/release_notes.html#section-2 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-3990) The Service Startup Type for the Puppet Enterprise for Windows Agent
Title: Message Title redmine.exporter created an issue Puppet / PUP-3990 The Service Startup Type for the Puppet Enterprise for Windows Agent Issue Type: New Feature Assignee: Unassigned Created: 2015/02/10 5:50 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The service startup type of the Windows Puppet agent is set to Automatic, with no service dependencies. While it is an uncommon occurrence, it is possible for the Puppet Agent to start before the network components are available e.g. It would be possible for the Puppet Agent to start before the DHCP Client has finished configuring the network adapters. As I have only started using Puppet recently I have not seen this specific issue with Puppet in the wild but I have seen similar timing issues with other windows programs in the past, particularly with 802.1x authenticated networks. I see two ways that this issue could be avoided: 1 . Change the Startup Type As of Server 2008 (I think?) and Vista an additional Startup type was added; Automatic (Delayed) From http://en.wikipedia.org/wiki/Windows_service Automatic: The service starts at system logon. Automatic (Delayed): The service starts a short while after the system has finished starting up. This option was introduced in Windows Vista in an attempt to reduce the boot-to-desktop time. However, not all services support delayed start It seems that ...a short while after... is roughly 120 seconds after the last Automatic Service is started. This would ensure that the
Jira (PUP-3845) Windows Unified Installer should track internal component versions
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Ryan Gard QA Contact: RyanGard 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-3994) Verify Windows Unified Installer Versions Tracking File
Title: Message Title Ryan Gard created an issue Puppet / PUP-3994 Verify Windows Unified Installer Versions Tracking File Issue Type: Task Affects Versions: PUP 4.0.0 Assignee: Ryan Gard Components: Windows Created: 2015/02/10 10:07 AM Due Date: 2015/02/11 Priority: Major Reporter: Ryan Gard Validate the behavior added in PUP-3845. Add Comment
Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title
Zachary Stern commented on PUP-3985
Re: With `storeconfigs = false` there are no warnings or errors about exported resources
Alright, so in puppet.conf on my master, I have storeconfigs == false
[root@pe-371-master ~]# puppet master --configprint storeconfigs
false
Exported resource in site.pp:
[root@pe-371-master ~]# tail /etc/puppetlabs/puppet/environments/production/manifests/site.pp -n 2
@@notify { 'foo': }
Notify | |
Restart pe-puppetserver for santiy:
[root@pe-371-master ~]# service pe-puppetserver restart
Stopping pe-puppetserver: [ OK ]
Jira (PUP-3993) PMT Acceptance Test Failure in CI
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3993 PMT Acceptance Test Failure in CI Change By: Ryan Gard Priority: Blocker 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-3821) Use of cfacter on Windows causes error
Title: Message Title Alexander Johnson updated an issue Puppet / PUP-3821 Use of cfacter on Windows causes error Change By: Alexander Johnson Scrum Team: Windows 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 (FACT-797) Fix KVM detection when run as non-root
Title: Message Title Kylo Ginsberg commented on FACT-797 Re: Fix KVM detection when run as non-root Re test, we aren't set up to test this readily, so skipping in-house test. 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-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Hailee Kenney assigned an issue to Hailee Kenney
Puppet / PUP-3863
hiera('some::key', undef) returns empty string
Change By:
Hailee Kenney
Assignee:
HaileeKenney
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-3845) Windows Unified Installer should track internal component versions
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Ryan Gard QA Status: Reviewed 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-3993) PMT Acceptance Test Failure in CI
Title: Message Title Ryan Gard commented on PUP-3993 Re: PMT Acceptance Test Failure in CI Anderson Mills Tracking PMT test failure in this ticket. I talked with Josh Cooper and apparently we aren't breaking Puppet Master acceptance and he doesn't consider this to be blocking for the FOSS team. I'll wait until you're free and we can figure out what is going on with this test. 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-3837) Work around Ruby string encoding behavior exercised during registry calls in win32/registry
Title: Message Title Josh Cooper commented on PUP-3837 Re: Work around Ruby string encoding behavior exercised during registry calls in win32/registry Looks good to me, marking 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 (FACT-797) Virtual fact on Linux does not work
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-797 Virtual fact on Linux does not work 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 (FACT-797) Virtual fact on Linux does not work
Title: Message Title Peter Huene updated an issue Facter / FACT-797 Virtual fact on Linux does not work Change By: Peter Huene Story Points: 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 (FACT-806) facter 2.4.1 2015.02.10 Release
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-806 facter 2.4.1 2015.02.10 Release Change By: Peter Huene Assignee: ReleaseEngineering PeterHuene 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-2037) Switch rpm/deb package manifest dir to default directory environment.
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-2037 Switch rpm/deb package manifest dir to default directory environment. Change By: Matthaus Owens Sprint: RE2015-02-25 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-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Wyatt Alt commented on PDB-1136 Re: communicate v4 API changes to stakeholders ahead of release Steve Axthelm the extract one was wrong but it's all fixed now. Kenneth Barber That seems reasonable to me. 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-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1136 communicate v4 API changes to stakeholders ahead of release Change By: Wyatt Alt Sincewe'redroppingv2andv3forthenextrelease,andv4isundergoingsomechanges,thereisnoAPIversioninPDB2.2.2thatmatchesrealityin3.0.WeneedtomakesureotherteamsusingPDBareawareofthechangesoccurringtov4inthenextrelease,beforethereleaseoccurs.Weshouldsendoutanemailoncewehaveacompletelistofchanges.Anincompletelistis:-dashesincommandandAPIendpointfieldnamesconvertedtounderscores(PDB-698)-reportsendpointnowsuppliesresourceevents(PDB-1072 ? )-toplevelextract(PDB- 1043 207 )-catalogsnowqueryable(PDB-1028)-makethe/v4/catalogsendpointusecertnamekeyinsteadofname(PDB-1099) 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-800) facter returns sensitive information about EC2 IAM tokens
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-800 facter returns sensitive information about EC2 IAM tokens Change By: Kylo Ginsberg Security: Internal 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-797) Fix KVM detection when run as non-root
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-797 Fix KVM detection when run as non-root Change By: Kylo Ginsberg Summary: FixKVMdetectionwhenrunasnon- rot root 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-797) Fix KVM detection when run as non-rot
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-797 Fix KVM detection when run as non-rot Change By: Kylo Ginsberg Summary: VirtualfactonLinuxdoesnotwork FixKVMdetectionwhenrunasnon-rot 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-3090) Packaging for puppet masters should include always_cache_features set to true.
Title: Message Title Matthaus Owens commented on PUP-3090 Re: Packaging for puppet masters should include always_cache_features set to true. It looks like the work here got lost in a rebase. I'll reapply once we have nate's branch merged into master. 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Matthaus Owens commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Eric Sorenson Yea, it has been updated since the version that was available for contrib summit. rpm -qpl /opt/jenkins-builds/puppet-agent/0.2.4/artifacts/el/7/products/x86_64/puppet-agent-0.2.4-1.x86_64.rpm | grep hiera /etc/puppetlabs/agent/code/hiera.yaml 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-797) Virtual fact on Linux does not work
Title: Message Title Peter Huene updated an issue Facter / FACT-797 Virtual fact on Linux does not work Change By: Peter Huene Sprint: Client2015-02-18 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 updated an issue PuppetDB / PDB-1225 Update fact storage and querying to use the new path column in the facts table Change By: Ryan Senior Issue Type: NewFeature Bug 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-1227) Test new table structure and fact path/value GC at scale
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1227 Test new table structure and fact path/value GC at scale Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 12:58 PM Priority: Normal Reporter: Ryan Senior Once we have PDB-1224 and PDB-1225 in place and know what the query will look like for PDB-1226 (even when the background process isn't complete), we should test the new structure and queries at a heavy load level. We can run the disassociated value as a separate cronjob like process for now, just to simulate the effect of the query on the running system. We should be able to use Kenneth Barber's setup for this Add Comment This message was sent by
Jira (PUP-3996) Potential issue with rspec resource matcher
Title: Message Title Hailee Kenney created an issue Puppet / PUP-3996 Potential issue with rspec resource matcher Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 1:34 PM Priority: Normal Reporter: Hailee Kenney When writing some spec tests I noticed an issue with the output of my failed tests. I was constantly seeing this as my error message: undefined method `[]' for nil:NilClass I think this is coming from this portion of code puppet/spec/lib/matchers/resource.rb: match do |actual_catalog| @mismatch =
Jira (HI-334) fix reference to deep merge gem
Title: Message Title Henrik Lindberg created an issue Hiera / HI-334 fix reference to deep merge gem Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 1:34 PM Priority: Normal Reporter: Henrik Lindberg There is a reference in the source to an older deep merge gem that is no longer in use - please update the URL to this https://github.com/danielsdeleo/deep_merge (it is a fork of the original). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3996) Potential issue with rspec resource matcher
Title: Message Title Hailee Kenney commented on PUP-3996 Re: Potential issue with rspec resource matcher /cc Kylo Ginsberg because I believe you were doing some work on switching to the new version of Rspec 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg Priority: Normal Trivial 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg commented on PUP-3991 Re: scanf only implemented for future parser Kylo Ginsberg I did not notice that it was targeting master instead of stable as intended. I am fixing that up manually. 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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg Fix Version/s: PUP4.0.0 Fix Version/s: PUP3.7.5 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-3991) scanf only implemented for future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Kylo Ginsberg Fix Version/s: PUP3.7.5 Fix Version/s: PUP4.0.0 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-1228) investigate a paging solution for multi-row responses
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1228 investigate a paging solution for multi-row responses Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 1:13 PM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Wyatt Alt Currently we jump through some hoops to implement limit and offset for reports and factsets: https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/jdbc.clj#L177-209 Catalogs should have the same issue, but it doesn't because it hasn't been implemented (see PDB-1083) The way we're doubling up the queries ruins the streaming response, so the approach is not performant at scale. We need to think of a better way to implement this. Part of a solution could be to push top-level extract down to database so resource-events can be toggled in the reports response. This would not solve the issue with factsets but would get the problem off the reports endpoint. There also may be something we can do using postgres window functions – needs more exploration.
Jira (FACT-815) Smoke test packages
Title: Message Title Kurt Wall commented on FACT-815 Re: Smoke test packages Kurt Wall takes OS X and gem for smoke testing 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-3996) Potential issue with rspec resource matcher
Title: Message Title
Hailee Kenney updated an issue
Puppet / PUP-3996
Potential issue with rspec resource matcher
Change By:
Hailee Kenney
WhenwritingsomespectestsInoticedanissuewiththeoutputofmyfailedtests.Iwasconstantlyseeingthisasmyerrormessage:{noformat}undefinedmethod`[]'fornil:NilClass{noformat}Ithinkthisiscomingfromthisportionofcode[puppet/spec/lib/matchers/resource.rb|https://github.com/puppetlabs/puppet/blob/master/spec/lib/matchers/resource.rb]:{noformat}matchdo|actual_catalog|@mismatch=ifresource=actual_catalog.resource(expected_resource)resource_match(expected_resource,resource)else@mismatch=expected#{@actual.to_dot}toinclude#{@expected[0]}falseendend{noformat}I'mnotsureifthematchersneedtobeupdatedtoworkwithanewversionofRspecorifsomethingelseisatplay.ButitseemslikesomethingwecouldfixbecauseIfoundmyselftryingtotrackdownsomewhereIwascalling[]onanilclass,whenthatmessagewasactuallycomingfromthematcher.
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-3991) scanf only implemented for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3991 scanf only implemented for future parser Change By: Henrik Lindberg Priority: Trivial Normal 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Branan Purvine-Riley assigned an issue to Branan Purvine-Riley Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Branan Purvine-Riley Assignee: BrananPurvine-Riley 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-1226) Create GC code for disassociated fact paths/values
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1226 Create GC code for disassociated fact paths/values Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 12:54 PM Priority: Normal Reporter: Ryan Senior Although we currently remove disassociated fact paths/values as we go, it's possible, if there are two concurrent transactions that each are pointing to the same fact path and value and they are simultaneously changing to a different value, their original value could be left behind. This process would clean those up. This seems to be pretty rare that it happens, so the number of fact values left behind is pretty low. These extra values don't actually cause problems (with the new table structure created in PDB-1224), but are just extra rows that will never be surfaced to the user. Care needs to be taken on the complexity of this query, how often it runs, how many records it would actually delete and the impact to the running system. Add Comment
Jira (PDB-1102) Upgrade to the latest ActiveMQ Jars
Title: Message Title Rob Browning commented on PDB-1102 Re: Upgrade to the latest ActiveMQ Jars After encountering instability with 5.10 and 5.11, we've decided to shelve this work for now. To test for the problem, you can checkout this branch and run lein test in a loop: https://github.com/rbrw/puppetdb/tree/ticket/master/pdb-1102-upgrade-activemq Here it nearly always prints various warning messages during (for example) services_test.clj, and outright fails on a fraction of the runs (last time, it failed perhaps one of ten times). See also: https://github.com/puppetlabs/puppetdb/pull/1231 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-3991) scanf only implemented for future parser
Title: Message Title Kylo Ginsberg commented on PUP-3991 Re: scanf only implemented for future parser Merged to master in https://github.com/puppetlabs/puppet/commit/b0f0bf0ceb0635c05978a58ff0dc693e6ca5d399. I'll mark as fixed in 4.0. 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-814) Tag the release and create packages
Title: Message Title Melissa Stone commented on FACT-814 Re: Tag the release and create packages tag 2.4.1 Tagger: Melissa Stone meli...@puppetlabs.com Date: Tue Feb 10 12:30:27 2015 -0800 2.4.1 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAABCgAGBQJU2mpjAAoJEBBUt6JL1uwwnOAP/A4ldOU7EdJj4UhDpnrjolJU Ss/VLiJB6mwgHxnCZsxfeOoUwBdaSDgsUWwQCiGjMU5UaulOK3C7+dvCVxfwzd2e
Jira (HI-334) fix reference to deep merge gem
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-334 fix reference to deep merge gem Change By: Henrik Lindberg Priority: Normal Trivial 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-3854) Update the automation in puppet_for_the_win to retrieve cfacter from the right location
Title: Message Title Melissa Stone commented on PUP-3854 Re: Update the automation in puppet_for_the_win to retrieve cfacter from the right location What else does this ticket need in order to move forward through the workflow so we can close it? 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-810) Update version number in source
Title: Message Title Peter Huene commented on FACT-810 Re: Update version number in source Merged in 9bd00be23f6a0e854e4577a92ddf647d4974b5d4. 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-812) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Peter Huene assigned an issue to Kylo Ginsberg Facter / FACT-812 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Peter Huene 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-3995) Prevent node resource names from potentially overlapping with other resources
Title: Message Title
Hailee Kenney created an issue
Puppet / PUP-3995
Prevent node resource names from potentially overlapping with other resources
Issue Type:
Bug
Assignee:
Henrik Lindberg
Components:
DSL, Language, Server
Created:
2015/02/10 12:02 PM
Priority:
Normal
Reporter:
Hailee Kenney
Before the pull request for PUP-3167 was submitted, if a node with a regex name matched the name of of another resource (like a class), then it was possible that the two would step on each other. This is pretty clearly illustrated by the example given in the original ticket:
class foo {
$bar = 'one'
}
Jira (FACT-808) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Peter Huene commented on FACT-808 Re: Is there a JIRA ticket targeted at the release for every commit? There is a ticket targeted for this release for every commit. 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-807) Is the code ready for release?
Title: Message Title Peter Huene commented on FACT-807 Re: Is the code ready for release? All spec and acceptance tests are passing. 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-808) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-808 Is there a JIRA ticket targeted at the release for every commit? Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-809) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-809 Is there a commit for every JIRA ticket targeted at the release? Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-811) Merge master into stable
Title: Message Title Peter Huene commented on FACT-811 Re: Merge master into stable Merge with https://github.com/puppetlabs/facter/commit/9bd00be23f6a0e854e4577a92ddf647d4974b5d4 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-814) Tag the release and create packages
Title: Message Title Peter Huene commented on FACT-814 Re: Tag the release and create packages SHA is 9bd00be23f6a0e854e4577a92ddf647d4974b5d4. 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-3995) Prevent node resource names from potentially overlapping with other resources
Title: Message Title Henrik Lindberg commented on PUP-3995 Re: Prevent node resource names from potentially overlapping with other resources We tried mangling the name with severe side effects. The solution is probably t debug where the search for a class 'foo' to find the node 'foo' - that should simply not happen. 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-822) Update Facter to use the virt-what vendored in the AIO agent.
Title: Message Title Geoff Nichols created an issue Facter / FACT-822 Update Facter to use the virt-what vendored in the AIO agent. Issue Type: Task Assignee: Eric Sorenson Created: 2015/02/10 11:58 AM Priority: Normal Reporter: Geoff Nichols Update Facter to use the virt-what vendored in the AIO agent at /opt/puppetlabs/agent/bin. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (FACT-807) Is the code ready for release?
Title: Message Title Peter Huene assigned an issue to Unassigned Facter / FACT-807 Is the code ready for release? Change By: Peter Huene Assignee: PeterHuene 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-807) Is the code ready for release?
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-807 Is the code ready for release? Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-808) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-808 Is there a JIRA ticket targeted at the release for every commit? Change By: Peter Huene Assignee: PeterHuene 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-1224) Move fact path reference from the fact_values table to the facts table
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1224 Move fact path reference from the fact_values table to the facts table Issue Type: Bug Assignee: Unassigned Created: 2015/02/10 12:38 PM Priority: Normal Reporter: Ryan Senior Although our current table structure is more efficient from a space perspective, it's more costly to query. We should create a migration that drops the fact path id from the fact_values table and instead have the facts table point at both the fact value and the fact path along with the factset. A quick first pass at this migration will allow the fact diffing logic to be updated in parallel. Care needs to be taken that we do this migration efficiently and quickly as it will be adding a new (populated, non-null) column on a table that is potentially very large. Add Comment
Jira (PDB-1225) Update fact storage and querying to use the new path column in the facts table
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1225 Update fact storage and querying to use the new path column in the facts table Issue Type: New Feature Assignee: Unassigned Created: 2015/02/10 12:45 PM Priority: Normal Reporter: Ryan Senior In storage.clj we should be able to diff fact paths like we currently diff fact values. As part of this the delete queries can change to use the new column, which should be significantly faster. The query engine and existing endpoints will also likely need to be updated to reflect the new structure. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1224) Move fact path reference from the fact_values table to the facts table
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1224 Move fact path reference from the fact_values table to the facts table Change By: Ryan Senior Sprint: PuppetDB2015-02-25 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-807) Is the code ready for release?
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-807 Is the code ready for release? Change By: Peter Huene Assignee: PeterHuene 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-809) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Peter Huene commented on FACT-809 Re: Is there a commit for every JIRA ticket targeted at the release? There is a commit for every JIRA ticket targeted for this release. 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-811) Merge master into stable
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-811 Merge master into stable Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-810) Update version number in source
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-810 Update version number in source Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-813) Prepare long form release notes and short form release story
Title: Message Title Peter Huene commented on FACT-813 Re: Prepare long form release notes and short form release story Nicholas Fagerlund Looks like there's only two tickets for this .z release. 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-812) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Peter Huene commented on FACT-812 Re: Is the Jira tidy-up done for this release and prepared for the next one? Kylo Ginsberg do we need a 2.4.2? 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-815) Smoke test packages
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-815 Smoke test packages Change By: Peter Huene Assignee: KyloGinsberg PeterHuene 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-3934) Environment used before set in Resource.initialize (regression?)
Title: Message Title Kurt Wall commented on PUP-3934 Re: Environment used before set in Resource.initialize (regression?) I'm going to pull this through to Done. It seems well-tested in spec and doesn't require further FR. 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.
