Jira (PUP-6357) Puppet resource runs appear to be getting slower over time
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6357 Puppet resource runs appear to be getting slower over time Change By: Geoff Nichols Sprint: Agent Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6357) Puppet resource runs appear to be getting slower over time
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-6357 Puppet resource runs appear to be getting slower over time Change By: Geoff Nichols Assignee: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott assigned an issue to Thomas Hallgren Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Jesse Scott Assignee: Jesse Scott Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1617) facter does not detect systemd-nspawn virtualization
Title: Message Title Florian Klink updated an issue Facter / FACT-1617 facter does not detect systemd-nspawn virtualization Change By: Florian Klink facter seems to be unable to detect being run inside a systemd-nspawn container:`facter virtual` returns `physical`, `facter is_virtual` returns false.I digged a bit into [virtualization_resolver.cc|https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/virtualization_resolver.cc#L106], it seems like facter is currently only guessing the container type (virtualization_resolver::get_cgroup_vm) by peeking into `/proc/1/cgroup`, but it's more complex than that.Probably facter should orientate more on the [detect_container() method|https://github.com/systemd/systemd/blob/master/src/basic/virt.c#L395] from systemd, to make the detection less error-prone. We could even use `systemd-detect-virt` if present. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7470) Puppet doesn't run using Bundler's standalone binstubs
Title: Message Title Joshua Spence created an issue Puppet / PUP-7470 Puppet doesn't run using Bundler's standalone binstubs Issue Type: Improvement Affects Versions: PUP 4.10.0 Assignee: Joshua Spence Created: 2017/04/25 4:14 PM Priority: Normal Reporter: Joshua Spence `Gem.loaded_specs['gettext_setup']` doesn't work with Bundler's standalone binstubs, which intentionally avoids a dependency on RubyGems and, instead, manipulates Ruby's `$LOAD_PATH` directly. As such, Puppet 4 doesn't currently work using Bundler's standalone binstubs (Puppet 3, however, works fine): ``` /etc/puppet/vendor/bundle/ruby/2.1.0/gems/puppet-4.10.0/lib/puppet.rb:76:in `singleton class': undefined method `version' for nil:NilClass (NoMethodError) from /etc/puppet/vendor/bundle/ruby/2.1.0/gems/puppet-4.10.0/lib/puppet.rb:55:in `' from /etc/puppet/vendor/bundle/ruby/2.1.0/gems/puppet-4.10.0/lib/puppet.rb:49:in `' from /usr/local/rbenv/versions/2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/rbenv/versions/2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /etc/puppet/vendor/bundle/ruby/2.1.0/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `' from /usr/local/rbenv/versions/2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/rbenv/versions/2.1.5/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /etc/puppet/vendor/bundle/ruby/2.1.0/gems/puppet-4.10.0/bin/puppet:4:in `' from /etc/puppet/bin/puppet:14:in `load' from /etc/puppet/bin/puppet:14:in `' ``` See some relevant context
Jira (FACT-1617) facter does not detect systemd-nspawn virtualization
Title: Message Title Florian Klink created an issue Facter / FACT-1617 facter does not detect systemd-nspawn virtualization Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 4:11 PM Priority: Normal Reporter: Florian Klink facter seems to be unable to detect being run inside a systemd-nspawn container: `facter virtual` returns `physical`, `facter is_virtual` returns false. I digged a bit into virtualization_resolver.cc, it seems like facter is currently only guessing the container type (virtualization_resolver::get_cgroup_vm) by peeking into `/proc/1/cgroup`, but it's more complex than that. Probably facter should orientate more on the detect_container() method from systemd, to make the detection less error-prone. Add Comment
Jira (PDB-3482) consider storing report statuses in the reports table
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3482
consider storing report statuses in the reports table
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/25 4:00 PM
Priority:
Normal
Reporter:
Wyatt Alt
We're seeing very costly joins between reports and report_statuses in the orchestrator scale testing. We've previously seen this behavior in PDB and it caused us to start analyzing small tables. Given all the other stuff we store in the reports table these days, I don't think we have a good justification for two tables anymore, and storing statuses inline will make these queries much faster.
Affected query:
reports[certname,hash,end_time,noop,status,noop_pending,corrective_change] { hash in nodes[latest_report_hash]{ certname in ["foo", "bar", "baz" ...]}
This generates a query like this: https://gist.github.com/nicklewis/b418d8481ff2cbfc72cef8c61812de6e
We should have a full 60k node database dump in the coming days to help with verification.
Jira (PDB-3481) consider replacing certnames.latest_report_id with certnames.latest_report_hash
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3481
consider replacing certnames.latest_report_id with certnames.latest_report_hash
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/25 3:52 PM
Priority:
Normal
Reporter:
Wyatt Alt
certnames.latest_report_id is used to join against reports to get the latest id, and often to get the hash of the latest report. If the hash instead of the id were stored in certnames, some queries such as nodes[latest_report_hash]{} should get much faster. The storage costs would be minimal since certnames is a small table, and I would expect joins between the two hashes to still be fast enough.
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-7224) Replace the Rgen AST model with one generated from a Pcore model
Title: Message Title Josh Cooper commented on PUP-7224 Re: Replace the Rgen AST model with one generated from a Pcore model Commit 3107b59 was backported to stable to fix broken code. The main issue however is fixed in Puppet 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) Add tests for StringConverter#string_PRuntimeType
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7469 Add tests for StringConverter#string_PRuntimeType Change By: Josh Cooper Summary: Add tests for StringConverter#string_PRuntimeType has no tests and appears to be dead code Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3464) Make a deterministic version of the sync convergence test
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-3464
Make a deterministic version of the sync convergence test
Change By:
Rob Browning
These should:{code} - Generate commands to be sent to both puppetdbs - Leverage the generators used for the command commutativity tests - Sometimes send the same command to both, sometimes not - Sometimes send the sae same commands to both, but in different orders - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3464) Make a deterministic version of the sync convergence test
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-3464
Make a deterministic version of the sync convergence test
Change By:
Rob Browning
These should:{code} - Generate commands to be sent to both puppetdbs - Leverage the generators used for the command commutativity tests - Sometimes send the same command to both, sometimes not - Sometimes send the smae sae commands to both, but in different orders - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7469 StringConverter#string_PRuntimeType has no tests and appears to be dead code Change By: Josh Cooper Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7469
StringConverter#string_PRuntimeType has no tests and appears to be dead code
Change By:
Josh Cooper
Commit [3107b59|https://github.com/puppetlabs/puppet/commit/3107b59] landed in puppet#stable, but the ticket PUP-7224 is marked as fixed in 5.0. *Updated*We need to add tests for {{string_PRuntimeType}}. Commit 3107b59 was intentionally cherry-picked back to stable, but due to the ticket number fixVersion mismatch, it is flagged during ticket reconciliation. The important thing is that the old code in stable was broken, and the cherry-pick was correct. So now we just need tests, which the linked PR does.*Original* It appears the {{StringConverter#string_PRuntimeType}} method is dead code, or at least is supposed to be called, but isn't. I commented the method out, and all of the rspec tests pass.If I enter a bogus format string, then the error is raised in {{string_PType}}, not {{string_PRuntimeType}}:{noformat}irb(main):012:0> Puppet::Pops::Types::StringConverter.convert(Puppet::Pops::Types::PRuntimeType::RUBY, "%s")=> "Runtime[ruby, ?]"irb(main):013:0> Puppet::Pops::Types::StringConverter.convert(Puppet::Pops::Types::PRuntimeType::RUBY, "%bogus")Puppet::Pops::Types::StringConverter::FormatError: Illegal format 'b' specified for value of Type type - expected one of the characters 'sp'from /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:1025:in `string_PType' {noformat}So this ticket is to:# Verify commit 3107b59 was supposed to land in stable, and revert it if not# Add tests# Ensure string_PRuntimeType gets called when it's supposed to, or delete the method if it's not needed/cc [~henrik.lindberg], [~kenn], [~geoff.nichols]
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Josh Cooper commented on PUP-7469 Re: StringConverter#string_PRuntimeType has no tests and appears to be dead code After deleting .bundle and Gemfile.lock, I can't repro the original error on stable. I thought I had reset hard on the respective SHA's but perhaps my branch was not up to date. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1616) Updated OS specific fact tests
Title: Message Title Eric Delaney created an issue Facter / FACT-1616 Updated OS specific fact tests Issue Type: Task Assignee: Eric Delaney Created: 2017/04/25 3:19 PM Priority: Normal Reporter: Eric Delaney Update the OS specific facter acceptance tests Code style TestRail ID(s) risk tags Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7469 StringConverter#string_PRuntimeType has no tests and appears to be dead code Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Thomas Hallgren commented on PUP-7469 Re: StringConverter#string_PRuntimeType has no tests and appears to be dead code Josh Cooper, it works for me on both stable and master (I know, because I'm in the process of adding the requested tests). Are you sure you added the method back after removing it in your test? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Josh Cooper commented on PUP-7469 Re: StringConverter#string_PRuntimeType has no tests and appears to be dead code It does that in master: $ git rev-parse HEAD 8f6b590ca7cab8c8d177246808246de331aba2bb $ bundle exec irb ... irb(main):003:0> Puppet::Pops::Types::StringConverter.convert(:sym, "%b") Puppet::Pops::Types::StringConverter::FormatError: Illegal format 'b' specified for value of Runtime type - expected one of the characters 'sqidxof' from /Users/josh/work/puppet/lib/puppet/pops/types/string_converter.rb:554:in `string_PRuntimeType' But not the current HEAD of stable: $ git rev-parse HEAD
Jira (PUP-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title Eric Sorenson commented on PUP-25 Re: Resource defaults aren't completely evaluated by the compiler Looks like it's in Ready for Merge, so let's get it in. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Mark Frost commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Moses Mendoza I can confirm that adding the routes.yaml back into our configuration (we had it for Puppet 3, but had purged it during our Puppet 4 migration) alleviates this bug, at least in the form that I reported it in PUP-7231 . For our particular case, this is a perfectly sufficient workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nicholas Fagerlund commented on PUP-6258 Re: Update Puppet OID lists to add new authorized extensions Well, I'm not going to be owning this page for much longer, I think. It's been updated at various points, but since we copy the Puppet docs for each new version, that history doesn't necessarily show up in the git log. It looks like DOC-2699 was the ticket for doing this, and it must have gotten lost in the mix somehow. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1615) move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test
Title: Message Title Eric Delaney updated an issue Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test Change By: Eric Delaney Summary: move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1615) move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test
Title: Message Title Eric Delaney updated an issue Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test Change By: Eric Delaney Move regression test into the custom_facts directory:ticket_1164_win32ole_custom_fact.rbticket_7039_facter_multiple_facts_one_file.rb Update the load_libfacter.rb test Update code Style, TestRail ID, and risk tag Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Thomas Hallgren commented on PUP-7469 Re: StringConverter#string_PRuntimeType has no tests and appears to be dead code Josh Cooper, the tests you're using are incorrect. They test converting the type into a string, not an instance of the type. An instance of Runtime is any object that isn't recognized as some other type, such as a Symbol. Example: 2.3.1 :002 > Puppet::Pops::Types::StringConverter.convert(:sym, "%s") => "sym" 2.3.1 :003 > Puppet::Pops::Types::StringConverter.convert(:sym, "%b") Puppet::Pops::Types::StringConverter::FormatError: Illegal format 'b' specified for value of Runtime type - expected one of the characters 'sqidxof' from /home/thhal/git/puppet/lib/puppet/pops/types/string_converter.rb:554:in `string_PRuntimeType' Add Comment
Jira (PUP-7468) scheduled_task : user attribute not working
Title: Message Title Josh Cooper commented on PUP-7468 Re: scheduled_task : user attribute not working Hi Lucas Boisserie can you provide the example manifest you are using with redacted password? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7469) StringConverter#string_PRuntimeType has no tests and appears to be dead code
Title: Message Title Josh Cooper created an issue Puppet / PUP-7469 StringConverter#string_PRuntimeType has no tests and appears to be dead code Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/04/25 2:12 PM Priority: Normal Reporter: Josh Cooper Commit 3107b59 landed in puppet#stable, but the ticket PUP-7224 is marked as fixed in 5.0. It appears the StringConverter#string_PRuntimeType method is dead code, or at least is supposed to be called, but isn't. I commented the method out, and all of the rspec tests pass. If I enter a bogus format string, then the error is raised in string_PType, not string_PRuntimeType: irb(main):012:0> Puppet::Pops::Types::StringConverter.convert(Puppet::Pops::Types::PRuntimeType::RUBY, "%s") => "Runtime[ruby, ?]" irb(main):013:0>
Jira (PUP-6357) Puppet resource runs appear to be getting slower over time
Title: Message Title Adam Bottchen assigned an issue to Geoff Nichols Puppet / PUP-6357 Puppet resource runs appear to be getting slower over time Change By: Adam Bottchen Assignee: Adam Bottchen Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Nick Walker Fix Version/s: PDB 4.2.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Sidenote I was incorrect in my original assertion that it is the default to not have a `routes.yaml` file in open source with the cache class set to `yaml` - the open source puppetlabs-puppetdb module configures this file by default and sets the cache this way. I think the only way to end up without it is if you've overridden the module default, or have installed the puppetdb package and configured it manually. Andrey Galkin you do not need to remove this file - your configuration is the recommended one. I believe this issue is still, as we've hypothesized, a race condition, and in this multi-master case I think one piece of the puzzle might be the facts getting cached on the first master but not the second, so the second run queries PDB which might not have been updated yet due to its asynchronous nature. Mark Frost you might try adding a routes.yaml file identical to the one on https://docs.puppet.com/puppet/4.10/config_file_routes.html, and see if this alleviates your issue. As noted above it will change it so facts are cached synchronously to a file on the master rather than asynchronously to puppetdb (note the facts will still be saved to puppetdb, just cached on the master - sorry for the confusing behavior here). It's not guaranteed to always solve the problem as we've seen in Andrey Galkin's scenario, and it will also not help if there is clock drift between the agent and master as the master might find the cache to be expired and search puppetdb anyway. As most commenters have suggested, I think ultimately the root cause to all of these issues is the circuitous (and inefficient) path our facts take during the agent catalog request, resulting in a scenario where the facts submitted by the agent aren't guaranteed to be the facts used by the master for compilation, and that's what I'm working on hopefully addressing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Assignee: Rob Browning Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Mark Frost commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters I'm the reporter on PUP-7231 , and we do not use a routes.yaml file in our environment. Like Andrey, though, I'm not sure if the suggestion is to add or remove the routes.yaml, as a fix. But I'm guessing since Andrey and I appear to be on opposite sides (i.e. he's using it already and I'm not), maybe that's not going to work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Moses Mendoza Regarding 'settings' error, I switched to use unlimited environment_timeout & API calls for refresh during deployment. So, did not pay much attention. Regarding routes.yaml - yes, it it used exactly as in the example. Do you suggest to remove one? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Andrey Galkin Jacky Leung do either of your masters use `/etc/puppetlabs/puppet/routes.yaml` (see https://docs.puppet.com/puppet/4.10/config_file_routes.html) to override any of the puppet's indirection terminii? If you're using Puppet Enterprise this would be the default I believe, but I don't think it is the default to have this file in open source. Just confirming because in Puppet Enterprise the cache class for facts is overridden to `yaml` which is a synchronous cache write, as opposed to `store_configs` (i.e., PDB) which is an asynchronous cache write. If your cache class is `store_configs` this greatly aligns with the hypothesis of a race condition. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Rodney Treweek updated an issue Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Rodney Treweek Attachment: perms_systeminstall.log Attachment: perms_admininstall.log Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Rodney Treweek commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators I'm also seeing this in https://puppetlabs.zendesk.com/agent/tickets/25313. I'm attaching the diff of the permissions after installation of the puppet agent as the SYSTEM user which the customer provided (These permissions issues are the result of automated system builds that install the puppet agent as the SYSTEM user, and thus result in several permissions problems). This is a serious issue when trying to upgrade several thousand Windows nodes. The attached diff does not include permissions issues for mcollective, which are also problematic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7153) Puppet fails with inscrutable errors when logging large messages on Windows
Title: Message Title Curtis Ruck commented on PUP-7153 Re: Puppet fails with inscrutable errors when logging large messages on Windows Can we bump this priority up. Just ran into this after enabling diff output on windows. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1613) Update regression ticket tests
Title: Message Title Branan Riley updated an issue Facter / FACT-1613 Update regression ticket tests Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3480) (maint) Pin concat module to a version that works with puppet 3
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3480 (maint) Pin concat module to a version that works with puppet 3 Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 11:20 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (FACT-1606) split the external_facts/fact_precedence tests into multiple files
Title: Message Title Branan Riley updated an issue Facter / FACT-1606 split the external_facts/fact_precedence tests into multiple files Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1607) split and update external fact test root_users_default_external_fact_dir
Title: Message Title Branan Riley updated an issue Facter / FACT-1607 split and update external fact test root_users_default_external_fact_dir Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1611) Update external fact stderr tests
Title: Message Title Branan Riley updated an issue Facter / FACT-1611 Update external fact stderr tests Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1600) Update the last of the options tests for facter with TestRail numbers, risk tags, code style
Title: Message Title Branan Riley updated an issue Facter / FACT-1600 Update the last of the options tests for facter with TestRail numbers, risk tags, code style Change By: Branan Riley Fix Version/s: FACT 3.6.z Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1604) clean up facter external facts tests
Title: Message Title Branan Riley updated an issue Facter / FACT-1604 clean up facter external facts tests Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1599) Add --color and --no-color acceptance tests
Title: Message Title Branan Riley updated an issue Facter / FACT-1599 Add --color and --no-color acceptance tests Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1595) Add TestRail numbers split files with multiple tests and code style for config file tests
Title: Message Title Branan Riley updated an issue Facter / FACT-1595 Add TestRail numbers split files with multiple tests and code style for config file tests Change By: Branan Riley Fix Version/s: FACT 3.6.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-3467
possible memory leak in reports querying (maybe querying in general)
Change By:
Nick Walker
Using the dataset here, which is from my install at homehttps://drive.google.com/drive/folders/0B324sr-dZ3nLfmhkaFdrT3B3ck1Cd2k2QmxISWFzdXJxcWo5S1JucS1nRlNqYzFBeHZHcTAI can cause PDB to OOM on a 256mb heap by issuing{code}curl -X GET http://localhost:8080/pdb/query/v4/reports > /dev/null{code} the The dataset has about 5800 reports in it, so that should not happen. I haven't dug around to see if there are any super huge reports in there, but I doubt there's anything outside the bounds of normal.The response appears to stream out of the database, since results start coming pretty much immediately. I haven't done any digging beyond that.edit:This is on a centos 7 vm running the latest PDB promoted to PE (along with the rest of the PE services). It has 6 gigs of ram and two vcpus. The underlying system is fairly quiet. Note that 256 mb is the default heap for pe-puppetdb.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1615) move and update 2 regression acceptance tests into the custom_facts directory
Title: Message Title Eric Delaney updated an issue Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory Change By: Eric Delaney Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1615) move and update 2 regression acceptance tests into the custom_facts directory
Title: Message Title Eric Delaney created an issue Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory Issue Type: Task Assignee: Unassigned Created: 2017/04/25 10:32 AM Priority: Normal Reporter: Eric Delaney Move regression test into the custom_facts directory: ticket_1164_win32ole_custom_fact.rb ticket_7039_facter_multiple_facts_one_file.rb Update code Style, TestRail ID, and risk tag Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1615) move and update 2 regression acceptance tests into the custom_facts directory
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-67) Issue with markdown rendering of code using ~~~
Title: Message Title Jean Bond commented on PDOC-67 Re: Issue with markdown rendering of code using ~~~ I don't know why I didn't get/see David Schmitt's previous ping on this ticket; my apologies. It's no longer necessary to use ~~~ instead of ```. With the changes I mentioned in an earlier comment, it doesn't matter which one you use. Personally, I prefer ``` as it's generally more often used. But afaik, it doesn't matter at all one way or the other. WRT Puppet Strings, module documentation guidance now recommends Strings use, but we'll still need Reference sections in READMEs. That will probably remain true until 1) the Forge supports Puppet Strings-generated documents, and 2) the community is very well socialized around the use and implementation of Puppet Strings. I expect the latter to take quite a while. All that said, unless there's some other issue with ~~~ vs. ```, I don't believe we still need this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3284) PQL operators sometimes whitespace sensitive
Title: Message Title David Kramer updated an issue PuppetDB / PDB-3284 PQL operators sometimes whitespace sensitive Change By: David Kramer Sprint: FF 2017-05-17 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Ethan Brown Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7110) Unable to halt Puppet service on Solaris using Puppet
Title: Message Title David Kramer updated an issue Puppet / PUP-7110 Unable to halt Puppet service on Solaris using Puppet Change By: David Kramer Sprint: FF 2017-04-05 , FF 2017-05-17 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Jonathan Newman updated an issue Puppet / PUP-7149 Puppet should include job id in reports and catalogs Change By: Jonathan Newman Summary: Puppet should include job_uuid job id in reports and catalogs Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Hi Andrey Galkin - just letting you know we're still working on this. As a sidenote, as I was reviewing the puppet server logs you included and I noticed this warning: Puppet Class 'settings' is already defined; cannot redefine at : Found that unusual and tracked it to https://tickets.puppetlabs.com/browse/PUP-7328 which should be addressed in puppet 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6250) Remove static compiler terminus
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6250 Remove static compiler terminus Change By: Henrik Lindberg Release Notes Summary: The static compiler functionality was superseded by static catalogsintroduced in 4.4[1]. As a result, the static compiler was deprecated in4.x and it is now removed. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Release Notes Summary: PuppetDB was using more memory than necessary when creating query results, which could occasionally result in out-of-memory errors when performing queries with very large result sets. This fix should eliminate the errors and reduce PuppetDB's overall memory footprint. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Change By: Russell Mull Fix Version/s: PDB 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Geoff Nichols Sprint: Client 2016-09-07, Agent N+ 3 4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6585) Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6585 Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Change By: Geoff Nichols Summary: Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6585) Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6585 Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Change By: Geoff Nichols Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7265) Remove file face
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7265 Remove file face Change By: Henrik Lindberg Release Notes Summary: The face called 'file' (deprecated in Puppet 4.x) has now been removed. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6585) Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6585 Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Change By: Geoff Nichols Acceptance Criteria: Puppet uses `Pathname.new(path).absolute_path?` instead of `Puppet::Util.absolute_path?` everywhere "internally" . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Geoff Nichols Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Geoff Nichols Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Fix Version/s: FACT 4.0.0 Fix Version/s: FACT 3.6.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5975) Remove Range#intersection monkey patch
Title: Message Title Henrik Lindberg commented on PUP-5975 Re: Remove Range#intersection monkey patch Excellent - I see we have PUP 7431 in our sprint and you got push rights. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6060) Change node_cache_terminus default to nil
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6060 Change node_cache_terminus default to nil Change By: Geoff Nichols Sprint: Agent N+ 3 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3479) (maint) (module) Require Puppet 4.7 or greater
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3479 (maint) (module) Require Puppet 4.7 or greater Change By: Russell Mull Summary: (maint) (module) Require Puppet 4.7 or greater Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3479) (maint) Require Puppet 4.7 or greater
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3479 (maint) Require Puppet 4.7 or greater Change By: Russell Mull Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5975) Remove Range#intersection monkey patch
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5975 Remove Range#intersection monkey patch Change By: Henrik Lindberg Sprint: PDE 2017-05-03 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3479) (maint) Require Puppet 4.7 or greater
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3479 (maint) Require Puppet 4.7 or greater Change By: Russell Mull Sprint: PuppetDB 2017-05-03 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7115) Un-vendor semantic_puppet gem for Puppet 5
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7115 Un-vendor semantic_puppet gem for Puppet 5 Change By: Geoff Nichols Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Geoff Nichols Sprint: Agent N+ 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Geoff Nichols Sprint: Agent N+ 1 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7255) SPIKE: Gracefully fail or downgrade when newer agents to talk to older masters
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7255 SPIKE: Gracefully fail or downgrade when newer agents to talk to older masters Change By: Geoff Nichols Sprint: Agent N+ 1 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3479) (maint) Require Puppet 4.7 or greater
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3479 (maint) Require Puppet 4.7 or greater Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 8:45 AM Priority: Normal Reporter: gepetto-bot Modules we depend on require this now. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7261 Add/Honor charset parameter in Content-Type header Change By: Geoff Nichols Sprint: Agent N+ 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3478) facts(value_string) needs an index
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3478 facts(value_string) needs an index Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 8:12 AM Priority: Normal Reporter: Wyatt Alt We've never had a btree index on fact_values(string), which means queries for value equality are not indexed (see F.31.4 https://www.postgresql.org/docs/9.6/static/pgtrgm.html). Somehow this hasn't been an issue for us in the past, likely because fact_values was so deduplicated that unindexed queries against it were performant enough. Now though, with duplicated values in the facts table, there is a much larger search space. In the orchestrator scale environment we saw a query for nodes with a particular fact value equal to "root" go from 180 seconds to around 10 just by adding an index (the table in that case is around 43 million rows). This index took about 45 minutes to build in that environment, so we'll want to use some finesse. One option would be to figure out a way to build indexes concurrently in migrations so that indexing doesn't block startup. This would require handling for the situation where the user shuts PDB down before the index is complete. Add Comment
Jira (PUP-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Henrik Lindberg commented on PUP-6694 Re: The Puppet Data type should be limited to JSON types. We are ending up with multiple concepts shoehorned into one thing. I think that is why this is difficult. The idea behind Data was that it represents the values that can be externally represented - in "data files" or in "serializations". Before Rich Data, this was limited to the data types representable directly in Pson/Json. Now this is not the case. Adding to the complexity is that at the moment, the standard serialization requires Json compliant data values, whereas the rich data support allows what is specified by Puppet/Pcore. This means that validation must be done as part of serialization. At the same time, users are generally unaware of these restrictions (and in particular about the restrictions imposed by Json). We could use names like PcoreData and JsonData (named after the technology), or use symbolic names e.g. Data and RichData, where Data is "what can be expressed in Json", and RichData is "what can be serialized using Puppet technology provided Rich Data Support is on". We do have the types Puppet::LookupValue which then corresponds to RichData, and Puppet::LookupValue which corresponds to the limit hash key allowed in Data. I am not sure if the limited hash key data type needs to have a type name. For the non parameterized Array and Hash it makes more sense if they are taken as Array[Any], and Hash[Any, Any] than trying to guess which of the constrained variants would be best to use. We must in any case perform a validation when serializing since user may attempt to support Rich Data while still using basic Json serialization. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post
Jira (PUP-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6694 The Puppet Data type should be limited to JSON types. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Thomas Hallgren assigned an issue to Jesse Scott Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Jesse Scott Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7465) Pcore ResourceType cannot handle title pattern with multiple entries
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7465 Pcore ResourceType cannot handle title pattern with multiple entries Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-25 Resource defaults aren't completely evaluated by the compiler Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7468) scheduled_task : user attribute not working
Title: Message Title Lucas Boisserie created an issue Puppet / PUP-7468 scheduled_task : user attribute not working Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: Types and Providers, Windows Created: 2017/04/25 6:25 AM Environment: Operating system: Windows 2012R2 Platform: AWS Priority: Normal Reporter: Lucas Boisserie Basic Info *Puppet Version: 4.10 *OS Name/Version: Windows 2012R2 Desired Behavior: We want a scheduled task be created with specific user Actual Behavior: Scheduled task always create with system user. Bad user is detected during the second run but there is no change.
Jira (PUP-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Geoff Nichols Sprint: Agent N+ 3 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Agent N+ 3 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1441 --show_diff causes crashes on files with UTF-8 content Change By: Geoff Nichols Sprint: Agent N+ 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Sprint: Agent N+ 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Sprint: Agent Ready for Engineering N+3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-25 Resource defaults aren't completely evaluated by the compiler Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7042) Mark non-debug messages for externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Geoff Nichols Sprint: AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP 2017-03-08 , Agent N+1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7310) Fix interpolation in externalized strings
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7310 Fix interpolation in externalized strings Change By: Geoff Nichols Sprint: AP 2017-03-08, Agent 2017-03-22 , Agent N+1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5974) Remove IO#binwrite monkey patch
Title: Message Title Geoff Nichols commented on PUP-5974 Re: Remove IO#binwrite monkey patch PR #5807 was merged to puppet#master at https://github.com/puppetlabs/puppet/commit/2e3aa8bd8c24cb337dd449dc9762865a580bff42. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Larsen commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale Duplicate of PUP-1055? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7467) Puppet removes non-managed entries from crontabs if non-ascii character found
Title: Message Title Larsen commented on PUP-7467 Re: Puppet removes non-managed entries from crontabs if non-ascii character found When searching for this bug, I found https://projects.puppetlabs.com/issues/22333 which sounds related. Has not been migrated to JIRA as it seems. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7467) Puppet removes non-managed entries from crontabs if non-ascii character found
Title: Message Title Larsen created an issue Puppet / PUP-7467 Puppet removes non-managed entries from crontabs if non-ascii character found Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 5:26 AM Environment: Debian Jessie puppet 3.7.2-4 Priority: Normal Reporter: Larsen I have three crontab files (root, nobody, www-data) that are managed by Puppet. There are additional entries in some of those files that are not managed by Puppet. One of those three crontabs (nobody) contains a German umlaut like "ö". When Puppet normally runs, it is using a UTF-8 locale and there will be no problems. This time however, Puppet was started via "salt cmd.run" which is resetting the locale to "C" (s. https://github.com/saltstack/salt/issues/19776). This led to this error message: Error: Puppet::Util::FileType::FileTypeCrontab could not read www-data: invalid byte sequence in US-ASCII Error: Could not prefetch
Jira (PUP-3836) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg commented on PUP-3836 Re: cleanup dns-alt-names setting and CLI option Ping Eric Sorenson - this is now more than a "golden oldie"... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
