Jira (PUP-1963) Generated resources never receive dependency edges
Title: Message Title
Josh Cooper commented on PUP-1963
Re: Generated resources never receive dependency edges
This also causes a regression in tidy:
$ mkdir -p /tmp/tidy/foo/bar/baz
$ git checkout fd3732b3328134f145e68ddfda2a5273abe9dd12
...
$ bundle exec puppet apply -e 'tidy { "/tmp/tidy/foo": matches => "*", recurse => true, rmdirs => true}' --graph --trace
Notice: Compiled catalog for XXX in environment production in 0.07 seconds
Notice: /Stage[main]/Main/Tidy[/tmp/tidy/foo]: Tidying 3 files
Error: Failed to apply catalog: Could not find dependency File[/tmp/tidy/foo/bar] for File[/tmp/tidy/foo]
/Users/josh/work/puppet/lib/puppet/util/errors.rb:106:in `fail'
/Users/josh/work/puppet/lib/puppet/type.rb:1491:in `block in validate_relationship'
/Users/josh
Jira (PUP-4748) Allow resources to be purged even when they have dependency relationships
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4748 Allow resources to be purged even when they have dependency relationships Change By: Josh Cooper Summary: Allow resources to be purged even whey when they have dependency relationships Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2471) (MAINT) Don't use table stats for HyperSQL dashboard queries
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2471 (MAINT) Don't use table stats for HyperSQL dashboard queries Change By: Ryan Senior Scope Change Category: Found Scope Change Reason: Fix a failure after merging the table stats change Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2471) (MAINT) Don't use table stats for HyperSQL dashboard queries
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2471 (MAINT) Don't use table stats for HyperSQL dashboard queries Issue Type: Bug Assignee: Unassigned Created: 2016/02/22 7:39 PM Priority: Normal Reporter: gepetto-bot Table stats (and vacuum) should only be used when running on Postgres. This was changed (on Postgres) for performance reasons. These same performance tweaks aren't available on HyperSQL, so we should just default back to the original query behavior in those cases. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2471) (MAINT) Don't use table stats for HyperSQL dashboard queries
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2471 (MAINT) Don't use table stats for HyperSQL dashboard queries Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5114) Inline file metadata and retrieve content using content_uri
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5114 Inline file metadata and retrieve content using content_uri Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Henrik Lindberg commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Zachary Smith Thanks for the sleuthing... that looks like something we can go on. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes Also Henrik Lindberg a git grep 'function_.*ldap' across the code shows only this module ever calling this function. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5930) If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes
Title: Message Title Zachary Smith commented on PUP-5930 Re: If a 3.x function calls a 4.x function via the new function API with the same name, Puppet server crashes So I was able to work on this a little more today and yeah this for sure an issue, I just need to build a reproducible case. After renaming the functions , the memory leak goes away. One interesting note, when I went through are renamed the 4.x function to not conflict with the 3.x wrapper , I actually forgot to rename the method with the same name in the 4.x function. At that point the memory leak continued. This to me states that the code path of the memory leak is likely directly linked to this method. i.e. Puppet::Functions.create_function(:renamed_get_ldap_group) do dispatch :renamed_get_ldap_group do ... end ... def get_ldap_group(foo,bar,baz) end Once I renamed the method, it stop OOM'ing
Jira (PUP-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher commented on PUP-5533 Re: (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Ping Sean Griffin I'm done validating this from the perspective of the server / puppet-db. I'm PE-14264 is ready to merge. I'm assigning this to you. Please let me know if you'd prefer a different course of action. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5533 (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Change By: Erik Dasher QA Contact: Erik Dasher Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher assigned an issue to Sean Griffin Puppet / PUP-5533 (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Change By: Erik Dasher Assignee: Erik Dasher Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5898) Data types seems to be messed up on hash parameters
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5898 Data types seems to be messed up on hash parameters Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5925) Optional data type and data binding with undef as default value
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5925 Optional data type and data binding with undef as default value Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5953) Puppetserver 2.2.1 (PC1 release) and gem handling
Title: Message Title Kylo Ginsberg commented on PUP-5953 Re: Puppetserver 2.2.1 (PC1 release) and gem handling This relates to SERVER-571. Note that the workaround discussed there might be effective here. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5953) Puppetserver 2.2.1 (PC1 release) and gem handling
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5953 Puppetserver 2.2.1 (PC1 release) and gem handling Change By: Kylo Ginsberg Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5905 transient test failures in common_package_name_in_different_providers.rb test Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5958) Docs: Update installer screenshots when branding work is finished
Title: Message Title Kylo Ginsberg commented on PUP-5958 Re: Docs: Update installer screenshots when branding work is finished Ping Ethan Brown. Not actually sure who will pick this up? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5958) Docs: Update installer screenshots when branding work is finished
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5958 Docs: Update installer screenshots when branding work is finished Change By: Kylo Ginsberg Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) Service resource ignoring status override.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5926 Service resource ignoring status override. Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5932) Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5932 Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux) Change By: Kylo Ginsberg Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5926) Service resource ignoring status override.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5926 Service resource ignoring status override. Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5932) Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux)
Title: Message Title Kylo Ginsberg commented on PUP-5932 Re: Error: Package: puppet-3.8.6-1.el7.noarch (puppetlabs-products) Requires: ruby(selinux) Ping Michael Stahnke Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5938) windows, user to groupassign to local administrators failed
Title: Message Title Kylo Ginsberg commented on PUP-5938 Re: windows, user to groupassign to local administrators failed Ping Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5938) windows, user to groupassign to local administrators failed
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5938 windows, user to groupassign to local administrators failed Change By: Kylo Ginsberg Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2424) DELETE FROM edges is extremely slow
Title: Message Title Ryan Senior commented on PDB-2424 Re: DELETE FROM edges is extremely slow Daniele Sluijters I looked at this and I don't see the issue. We have a unique index on (certname, source, target, type). Our current delete edges code, calls a delete using (certname, source, target). This still hits the unique index. There's only a few types of edges that we support, so it doesn't seem like that would ever be slow. One thing I do see is that we issue seperate deletes for each edge, which is really slow. Instead we should issue one delete statement that includes all the edges we need to delete. That doesn't seem to match up with what you're seeing. Do you have any more info on the issue? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Henrik Lindberg assigned an issue to Andrey Galkin Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Change By: Henrik Lindberg Assignee: Thomas Hallgren Andrey Galkin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5916) Arista transient test failure on puppet_mcollective_service_management.rb
Title: Message Title Scott Garman assigned an issue to Scott Garman Puppet / PUP-5916 Arista transient test failure on puppet_mcollective_service_management.rb Change By: Scott Garman Assignee: Scott Garman Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5916) Arista transient test failure on puppet_mcollective_service_management.rb
Title: Message Title Scott Garman commented on PUP-5916 Re: Arista transient test failure on puppet_mcollective_service_management.rb I can dig into this starting tomorrow. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title
Thomas Hallgren commented on PUP-5952
Re: Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Well, at least we now know that we're testing the same Puppet version and the same code. I don't get the empty element. What happens if you use puppet apply, like this:
# puppet apply --confdir=/home/thhal/git/puppet-testbench/pup_5952/etc/puppet -e "notice lookup('classes',Any,'unique')"
Notice: Scope(Class[main]): [someclass]
Notice: Compiled catalog for home.tada.se in environment production in 0.15 seconds
Notice: Applied catalog in 0.06 seconds
Also, if you convey the result of doing a could do a lookup with --explain. Here's what I get:
# puppet lookup --confdir=/home/thhal/git/puppet-testbench/pup_5952/etc/puppet --merge unique --explain classes
Merge strategy unique
Data Binding "hiera"
No such key: "classes"
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Henrik Lindberg commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation Thanks Jonathan Gray, we chalk that up to the Sun and Moon aligning with Jupiter and Mars Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Change By: Henrik Lindberg Assignee: Andrey Galkin Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5916) Arista transient test failure on puppet_mcollective_service_management.rb
Title: Message Title Michael Stahnke commented on PUP-5916 Re: Arista transient test failure on puppet_mcollective_service_management.rb Scott Garman or Rick Sherman want to look at this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Jonathan Gray commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation Yes. Maybe someday in the future if someone else runs into this, google will point them here and a more reliable reproduce case can be found. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Andrey Galkin commented on PUP-5952 Re: Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Actually, I was moving to lookup() from hiera_classes() and spotted the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title
Andrey Galkin commented on PUP-5952
Re: Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
That's interesting. I have taken exactly your example with no modification and got the following results:
"target": "Notify['[, someclass]']"
The empty element, I guess is Undef. Please tell me how I can help you to reproduce the problem.
Full output:
{
"tags": ["settings","default","node"],
"name": "default",
"version": 1456183739,
"code_id": null,
"environment": "production",
"resources": [
{
"type": "Stage",
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Henrik Lindberg commented on PUP-5952 Re: Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Andrey Galkin Are you by any chance using hiera_classes function? It will not work with lookup and data in environments and modules; none of the hiera_xxx function does that. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Henrik Lindberg commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation Jonathan Gray Does that mean we can close this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2456) Is the code ready for release? (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2456 Is the code ready for release? (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.2.4%22
Jira (PDB-2458) Update version number in source (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2458 Update version number in source (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PDB-2466) Packages pushed (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2466 Packages pushed (PDB 3.2.4) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (PDB-2460) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2460 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X
Jira (PDB-2464) Go/no-go meeting (before 4pm) (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2464 Go/no-go meeting (before 4pm) (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Andrew Roetker Nicholas Fagerlund Beth Cornils Kurt Wall Morgan Rhodes
Jira (PDB-2439) PDB-2439 : Provide a better defaults for the broker's memory usage
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2439 PDB-2439 : Provide a better defaults for the broker's memory usage Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2462) Tag the release and create packages (PDB 3.2.4)
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-2462
Tag the release and create packages (PDB 3.2.4)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/02/22 3:27 PM
Priority:
Normal
Reporter:
Wyatt Alt
(Initial planned release date: 2016-02-24)
Tag and create packages
Developer provides the SHA - Andrew Roetker - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PDB-2457) Reconcile git commits and JIRA tickets (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2457 Reconcile git commits and JIRA tickets (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earl
Jira (PDB-2463) Smoke test packages (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2463 Smoke test packages (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (PDB-2469) Update dujour to notify users to use 3.2.4 (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2469 Update dujour to notify users to use 3.2.4 (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Update dujour to notify users to use 3.2.4. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2470) Close all resolved tickets in Jira (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2470 Close all resolved tickets in Jira (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.2.4%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PDB-2439) PDB-2439 : Provide a better defaults for the broker's memory usage
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2439 PDB-2439 : Provide a better defaults for the broker's memory usage Change By: Rob Browning Scope Change Category: Adopted Scope Change Reason: Time available, and may want for stable release Story Points: 1 Sprint: PuppetDB 2016- 03 02 - 09 24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.g
Jira (PDB-2468) Send out announcements (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2468 Send out announcements (PDB 3.2.4) Issue Type: Sub-task Assignee: Beth Cornils Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Morgan Rhodes: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependen
Jira (PDB-2459) Merge master into stable (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2459 Merge master into stable (PDB 3.2.4) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git che
Jira (PDB-2467) Docs pushed (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2467 Docs pushed (PDB 3.2.4) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2461) Prepare long form release notes and short form release story (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2461 Prepare long form release notes and short form release story (PDB 3.2.4) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2465) Push tag (PDB 3.2.4)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2465 Push tag (PDB 3.2.4) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/22 3:27 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-02-24) The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment
Jira (PUP-5771) Add introduction to Iterable and Iterator to Pre-docs for PUP-5648
Title: Message Title Henrik Lindberg commented on PUP-5771 Re: Add introduction to Iterable and Iterator to Pre-docs for PUP-5648 And I have pushed changes to correct what Thomas found. Ping Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2455) puppetdb 3.2.4 2016-02-24 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2455 puppetdb 3.2.4 2016-02-24 Release Issue Type: Task Assignee: Andrew Roetker Created: 2016/02/22 3:26 PM Priority: Normal Reporter: Wyatt Alt puppetdb 3.2.4 2016-02-24 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PUP-5114) Inline file metadata and retrieve content using content_uri
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-5114
Inline file metadata and retrieve content using content_uri
Change By:
Michael Smith
**Updated**This ticket was repurposed to handle reworking how the compiler inlines metadata and how the agent uses that information to retrieve versioned file content. This ticket does the following:* Inlines file metadata into the catalog in a new {{metadata}} section.* Inlines recursive file metadata into the catalog in a new {{recursive_metadata}} section.* Deletes the {{content_uri}} file parameter and moves it into the {{FileMetadata}} object where it belongs. This isn't a breaking change, because we never released a version of puppet with {{content_uri}} as a file parameter.* Ensures {{source}} is set on metadata objects that the fileserver returns in the {{metadata}} section (but not the {{recursive_metadata}} section) . This is necessary so that we know which source file_metadata came from, in the situation you have multiple sources, and puppet selects the first non-nil one.* Modifies the agent to look in the catalog when resolving metadata. If no metadata exists for a file resource, it falls back to its previous behavior, requesting data from the server.* If the agent needs to retrieve file content, and the file resource has metadata containing a {{content_uri}} parameter, then it uses it to download file content.**Original**Modify the catalog building process to inline {{content_uri}} for files. It should be of the form:{noformat}content_uri => 'puppet:///modules/ntp/files/ntp.conf'{noformat}Note the path is rooted in the per-environment directory, e.g. {{/etc/puppetlabs/code/environments/production}}. By default, {{content_uri}} should not specify a host and port in the URI, e.g. {{puppet:///modules/...}}. However, if {{source => 'puppet://:'}}, then those values should be preserved in the {{content_uri}}.Modify the catalog application process to retrieve content for {{file}} resources using the {{content_uri}} parameter instead of {{source}}. If the {{content_uri}} parameter is absent (for example because source refers to a local file or custom mount point), then the agent should fallback to using {{source}} and retrieve latest file content like it does now.The agent should send the REST request of the form:{noformat}https://server:port/puppet/v3/static_file_content/?code_id={noformat}where {{}} is that path of the file to download, e.g. {{modules/ntp/files/ntpd.conf}}, and {{code_id}} is obtained from the catalog. Also note the endpoint is called {{static_file_content}}, a recent development, and it's in the {{v3}} namespace.The agent may send {{environment=production}} as a query param due to the indirector, but it is not necessary since that information will be contained in {{code_id}}.The agent should stream the response back, reading chunks of the response body like we do for {{file_content}}: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/file/content.rb#L216-L221. In other words, we don't want to read the entire file into a memory.The agent should use DNS SRV records like it does for {{file_content}} requests. This is accomplished by following the {{file_content}} example above.Also add rspec tests under spec/integration simulating the server responding with va
Jira (PUP-5696) Add content_uri parameter to the file type
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5696 Add content_uri parameter to the file type Change By: Josh Cooper Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5696) Add content_uri parameter to the file type
Title: Message Title Josh Cooper commented on PUP-5696 Re: Add content_uri parameter to the file type We ended up reverting this behavior change in PUP-5114. Changing to Wont Do. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5114) Inline file metadata and retrieve content using content_uri
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5114
Inline file metadata and retrieve content using content_uri
Change By:
Josh Cooper
**Updated**This ticket was repurposed to handle reworking how the compiler inlines metadata and how the agent uses that information to retrieve versioned file content. This ticket does the following:* Inlines file metadata into the catalog in a new {{metadata}} section.* Inlines recursive file metadata into the catalog in a new {{recursive_metadata}} section.* Deletes the {{content_uri}} file parameter and moves it into the {{FileMetadata}} object where it belongs. This isn't a breaking change, because we never released a version of puppet with {{content_uri}} as a file parameter.* Ensures {{source}} is set on metadata objects that the fileserver returns. This is necessary so that we know which source file_metadata came from, in the situation you have multiple sources, and puppet selects the first non-nil one.* Modifies the agent to look in the catalog when resolving metadata. If no metadata exists for a file resource, it falls back to its previous behavior, requesting data from the server.* If the agent needs to retrieve file content, and the file resource has metadata containing a {{content_uri}} parameter, then it uses it to download file content.**Original** Modify the catalog building process to inline {{content_uri}} for files. It should be of the form:{noformat}content_uri => 'puppet:///modules/ntp/files/ntp.conf'{noformat}Note the path is rooted in the per-environment directory, e.g. {{/etc/puppetlabs/code/environments/production}}. By default, {{content_uri}} should not specify a host and port in the URI, e.g. {{puppet:///modules/...}}. However, if {{source => 'puppet://:'}}, then those values should be preserved in the {{content_uri}}.Modify the catalog application process to retrieve content for {{file}} resources using the {{content_uri}} parameter instead of {{source}}. If the {{content_uri}} parameter is absent (for example because source refers to a local file or custom mount point), then the agent should fallback to using {{source}} and retrieve latest file content like it does now.The agent should send the REST request of the form:{noformat}https://server:port/puppet/v3/static_file_content/?code_id={noformat}where {{}} is that path of the file to download, e.g. {{modules/ntp/files/ntpd.conf}}, and {{code_id}} is obtained from the catalog. Also note the endpoint is called {{static_file_content}}, a recent development, and it's in the {{v3}} namespace.The agent may send {{environment=production}} as a query param due to the indirector, but it is not necessary since that information will be contained in {{code_id}}.The agent should stream the response back, reading chunks of the response body like we do for {{file_content}}: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/file/content.rb#L216-L221. In other words, we don't want to read the entire file into a memory.The agent should use DNS SRV records like it does for {{file_content}} requests. This is accomplished by following the {{file_content}} example above.Also add rspec tests under spec/integration simulating the server responding with valid content, and with HTTP 404. The latter case should cause the resource to f
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Jonathan Gray commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation I've wondered about that Thomas. The reason why is that before I lost my reproduction case, the last catalog that applied for the voxpupuli/puppetboard module had an error in it with a duplicate parameter name yet it wasn't failing (started being a failing error in 4.3.2). Once I restarted the puppetserver in debug mode and the lookup started working that problem showed up. So my thought is that somehow I was running an earlier version in the daemon than what was reported with just a `puppet master --version` command (as that would be a new instance/process). I'm not sure how that would have happened, but it would explain some things. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x
Title: Message Title Ryan Gard updated an issue Facter / FACT-1348 Remove usage of win32-security gem in Facter 2.x Change By: Ryan Gard QA Risk Assessment: Low QA Status: Reviewed QA Contact: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Thomas Hallgren assigned an issue to Andrey Galkin Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment Change By: Thomas Hallgren Assignee: Andrey Galkin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5952) Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5952 Lookup in global Hiera injects Undef/nil with unique merge strategy, if key exists only in environment I am not able to reproduce this using puppet apply or puppet master compile on any version of Puppet >= 4.3.0 (lookup didn't exist prior to that). I'm attaching the simple example that I used for the tests. View the resulting catalog using: puppet master --confdir /etc/puppet --compile default or run to see the output using: puppet apply --confdir /etc/puppet -D Andrey Galkin, can you please alter that example so that it provokes the problem? Change By: Thomas Hallgren Attachment: pup_5952.zip
Jira (PDB-2439) PDB-2439 : Provide a better defaults for the broker's memory usage
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2439 PDB-2439 : Provide a better defaults for the broker's memory usage Change By: Wyatt Alt Summary: t PDB-2439 : Provide a better defaults for the broker's memory usage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2439) t
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2439 t Change By: Wyatt Alt Summary: Provide a better defaults for the broker's memory usage t Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5114) Inline file metadata and retrieve content using content_uri
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5114 Inline file metadata and retrieve content using content_uri Change By: Josh Cooper Summary: Retrieve Inline file metadata and retrieve content using content_uri Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title Henrik Lindberg commented on PUP-5924 Re: The default hiera.yaml file does not include the '::' prefix for the environment variable Rob Nelson I am not sure I understand what you are saying. Is it that you have to use "puppet agent" to trigger the problem, or that you need to use both "puppet agent" and that the master is running on "puppet server" ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5924) The default hiera.yaml file does not include the '::' prefix for the environment variable
Title: Message Title Rob Nelson commented on PUP-5924 Re: The default hiera.yaml file does not include the '::' prefix for the environment variable Thomas Hallgren Henrik Lindberg This does not happy with puppet apply, only with puppet agent. Maybe it's only in the puppetserver code. That was what was frustrating - puppet apply and hiera cli interaction looked smooth, but running puppet agent failed find anything at all since it wasn't reading the datadir properly. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-5921
Deprecate source_permissions
Change By:
Michael Smith
We are steering people away from {{source_permissions}} for two reasons:# it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)# -it is not fully supported/supportable by static_catalogs- no longer true , it will now be fully supported in static_catalogs It is still used by pluginsync for external facts however, and we will need to find a replacement mechanism for that, see linked PUP-5920.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Facter / FACT-1348 Remove usage of win32-security gem in Facter 2.x Change By: Glenn Sarti Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-5921
Deprecate source_permissions
Change By:
Michael Smith
We are steering people away from {{source_permissions}} for two reasons:# it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)# - it is not fully supported/supportable by static_catalogs - no longer true It is still used by pluginsync for external facts however, and we will need to find a replacement mechanism for that, see linked PUP-5920.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x
Title: Message Title Glenn Sarti updated an issue Facter / FACT-1348 Remove usage of win32-security gem in Facter 2.x Change By: Glenn Sarti Scope Change Category: Found Scope Change Reason: Create as part of PUP-5735. As this is a Facter fix, a FACT ticket was created Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5771) Add introduction to Iterable and Iterator to Pre-docs for PUP-5648
Title: Message Title Thomas Hallgren commented on PUP-5771 Re: Add introduction to Iterable and Iterator to Pre-docs for PUP-5648 I added my review comments to commit 8764543. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x
Title: Message Title Glenn Sarti created an issue Facter / FACT-1348 Remove usage of win32-security gem in Facter 2.x Issue Type: Task Affects Versions: FACT 2.4.6 Assignee: Glenn Sarti Components: Windows Created: 2016/02/22 2:16 PM Fix Versions: FACT 2.4.7 Labels: windows i18n Priority: Normal Reporter: Glenn Sarti As part of the work in PUP-5735 it was discovered that Facter uses the win32-security gem. This gem uses ANSI API calls and can cause issues with unicode characters. This ticket will port the required code from Puppet into Facter and then remove usage of the win32-security gem.
Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x
Title: Message Title Glenn Sarti updated an issue Facter / FACT-1348 Remove usage of win32-security gem in Facter 2.x Change By: Glenn Sarti Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5878) acceptance: agent can reconnect after master failure
Title: Message Title Josh Cooper commented on PUP-5878 Re: acceptance: agent can reconnect after master failure Verifying this in an automated acceptance test is proving to be difficult. Marking as won't do, and go with the manual verification that has already been done when the original fix was merged. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2355) Deprecate import/export CLJ CLI in favor of puppetdb-cli
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2355 Deprecate import/export CLJ CLI in favor of puppetdb-cli Change By: Wyatt Alt Fix Version/s: PDB 3.2.x Fix Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5698) Inline directory metadata
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5698 Inline directory metadata Change By: Josh Cooper Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5698) Inline directory metadata
Title: Message Title Josh Cooper commented on PUP-5698 Re: Inline directory metadata We are going to fix the issue a different way, see PUP-5114. When static catalogs are enabled, file metadata will be inlined in the catalog, separate from the resources section. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1341) Facter Throws Unhandled Exception when Run Under Unicode User
Title: Message Title Michael Smith commented on FACT-1341 Re: Facter Throws Unhandled Exception when Run Under Unicode User LTH-84 was merged, should just require a version bump, and maybe a test case. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1341) Facter Throws Unhandled Exception when Run Under Unicode User
Title: Message Title Michael Smith updated an issue Facter / FACT-1341 Facter Throws Unhandled Exception when Run Under Unicode User Change By: Michael Smith Story Points: 1 Sprint: Client 2016-03-09 (Burn CF) Scrum Team: Windows Client Platform Fix Version/s: FACT 3.1.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions
Title: Message Title Henrik Lindberg commented on PUP-5569 Re: acceptance: to ensure Resource Collectors can use resource references in search expressions merged to master at: 89dd468 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5569 acceptance: to ensure Resource Collectors can use resource references in search expressions Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-5569 acceptance: to ensure Resource Collectors can use resource references in search expressions Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Henrik Lindberg commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation I found issues reported for JRuby relating to symlinks and require / require relative. Perhaps far-fetched, but is puppet being symlinked to the location used by puppet server ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5771) Add introduction to Iterable and Iterator to Pre-docs for PUP-5648
Title: Message Title Henrik Lindberg commented on PUP-5771 Re: Add introduction to Iterable and Iterator to Pre-docs for PUP-5648 Jorie Tappa I don't think Thomas has reviewed that yet - I don't think that what I wrote is off mark but it may contain typos. I don't expect any major changes. Just saying if you want to start reading and asking questions before thomas has reviewed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Thomas Hallgren commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation I've gone through the Puppet code-base in an attempt to figure out how this could have happen. The only way I can think of that could cause this problem is if some part of the code base is missing, or originates from a version < 4.2.3, and another part of the code base is >= 4.2.3 at the time when Puppet Server loaded it and it has since been corrected which made the problem go away after the master restarted but there's of course no way to be certain. Jonathan Gray, is there any chance that what I described might have happened? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5955) uninitialized constant Puppet::Pops::Lookup::Invocation
Title: Message Title Henrik Lindberg commented on PUP-5955 Re: uninitialized constant Puppet::Pops::Lookup::Invocation Thanks Chris Price, thought you may have seen something similar before... We will just have to wait and see if it happens again. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5933) Don't set pluginsync in puppet.conf on Windows
Title: Message Title Josh Cooper commented on PUP-5933 Re: Don't set pluginsync in puppet.conf on Windows Install an MSI from http://builds.puppetlabs.lan/puppet-agent/bbb9b2a68b85c9137c531dec9b920698df72c127/artifacts/windows/puppet-agent-1.3.5.277.gbbb9b2a-x64.msi (where puppet.conf doesn't exist) and run puppet agent -t and make sure we don't get a deprecation warning. There is a separate ticket to make sure property is removed during an upgrade. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5884) Internationalization for Windows
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5884 Internationalization for Windows Change By: Craig Gomes Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5933) Don't set pluginsync in puppet.conf on Windows
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-5933 Don't set pluginsync in puppet.conf on Windows Change By: Josh Cooper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2381) Write a script to collect enough stats from customer DBs to define 'representative data'
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2381 Write a script to collect enough stats from customer DBs to define 'representative data' Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2381) Write a script to collect enough stats from customer DBs to define 'representative data'
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2381 Write a script to collect enough stats from customer DBs to define 'representative data' Change By: Wyatt Alt Sprint: PuppetDB 2016- 03 02 - 09 24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5889) Add a --strict flag to Puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5889
Add a --strict flag to Puppet
Change By:
Henrik Lindberg
Add a flag {{\--strict}} to puppet settings. When in effect this will turn on --strict_variables, and will also enable other "helpful" but undesirable behavior. (Each such behavior to be defined in a separate ticket). The semantics of this flag should be:* --strict=ignore; no strictness checks are to be performed, nothing is reported.* --strict=warn; strictness checks are performed, they are reported as warnings, individually configurable warnings follow their own setting (i.e. if they are added to disabled_warnings).-- strict=errors; strictness checks are performed, they are reported as errors and stop the execution. Further configuration to error individually is not supported.When we add this we promise to not change the set of things that lead to warning/error in .z releases, but we reserve the right to do so for .x releases. The idea being is that you can safely accept updates for .z without having to do anything. For .x releases you may need to step back to {{\--strict=warning}} and then correct the problem before going back to {{\--strict=error}}. This scheme should cater to those that are pedantic about following best practises and not using deprecated features while those that only care at major version boundaries can do so in peace without being bothered with lots of deprecation warnings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google
Jira (PUP-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title Anderson Mills commented on PUP-5734 Re: Value of the key dependencies in the metadata.json of modules isn't checked Build 97 went green — https://jenkins.puppetlabs.com/job/platform_puppet_intn-van-sys_master/97/ SHA aeb2bf633ac48604803e1f8d2dac04c1f64d3eb8 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5960) Document static catalog responses for catalog and file_metadata
Title: Message Title
Michael Smith created an issue
Puppet / PUP-5960
Document static catalog responses for catalog and file_metadata
Issue Type:
Task
Assignee:
Unassigned
Created:
2016/02/22 1:07 PM
Fix Versions:
PUP 4.4.1
Priority:
Normal
Reporter:
Michael Smith
Update api/docs for catalog (and possibly file_metadata) to document the new responses that can occur with static catalogs. Main additions are the metadata and recursive_metadata properties of the catalog, and within those the file_metadata objects can now include source} and {{content_uri properties.
Add Comment
Jira (PUP-5959) Derive static catalog metadata lookup defaults from File type
Title: Message Title Michael Smith updated an issue Puppet / PUP-5959 Derive static catalog metadata lookup defaults from File type Change By: Michael Smith Fix Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5959) Derive static catalog metadata lookup defaults from File type
Title: Message Title Michael Smith created an issue Puppet / PUP-5959 Derive static catalog metadata lookup defaults from File type Issue Type: Improvement Assignee: Unassigned Created: 2016/02/22 12:12 PM Priority: Normal Reporter: Michael Smith The static catalog work in PUP-5114 hard-codes some defaults from the file type that are used to query the FileServing::Metadata terminus. We should query those from the file type instead to ensure they stay in-sync. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
