Jira (PUP-7647) All Puppet components should support SCEP
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-7647 All Puppet components should support SCEP Issue Type: New Feature Assignee: Jeremy Barlow Components: AIO, Server Created: 2017/06/09 7:11 PM Priority: Normal Reporter: Trevor Vaughan In addition to rolling it's own CA, the Puppet infrastructure should be able to use SCEP to request certificates from a pre-existing PKI infrastructure to easily support Enterprise PKI Policies. Add Comment
Jira (PUP-7646) Environment_timeout should be configurable per environment but not from a file inside of the environment
Title: Message Title Nick Walker created an issue Puppet / PUP-7646 Environment_timeout should be configurable per environment but not from a file inside of the environment Issue Type: Bug Assignee: Unassigned Created: 2017/06/09 4:11 PM Priority: Normal Reporter: Nick Walker The Problem I'd like to set `environment_timeout = unlimited` for my production environment and any other long lived environments I may have. I'd like all of my feature branch environments to have a much lower environment_timeout so they do no consume memory long after I've stopped using them. Since environment.conf is in my control-repo I cannot change environment_timeout to a different value without eventually causing that value to become a merge conflict. Suggested Solution I should be able to set environment_timeout ( and possibly other puppet.conf settings ) for an environment in a file outside of the environment. The environment sections in puppet.conf would have probably been fine if they hadn't been removed when directory environments were introduced. https://docs.puppet.com/puppet/3.5/config_file_main.html#environment-config-sections
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Thomas Hallgren assigned an issue to John Duarte Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Change By: Thomas Hallgren Assignee: John Duarte 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-7645) Ensure that MO files are available in released puppet gems
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7645 Ensure that MO files are available in released puppet gems Change By: Maggie Dreyer Fix Version/s: PUP 5.1.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-7645) Ensure that MO files are available in released puppet gems
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7645 Ensure that MO files are available in released puppet gems Issue Type: Task Assignee: Unassigned Created: 2017/06/09 1:15 PM Priority: Normal Reporter: Maggie Dreyer We do not currently commit any MO files to the Puppet repo: they are built in vanagon packaging and installed along with the Agent. If we want to support i18n in the Puppet gem, we need to make sure we compile these files during gem packaging as well. Alternatively, we need to revisit the decision to not commit these files. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1351) Facter on Alpine Linux requires root permissions
Title: Message Title Igor Galić commented on FACT-1351 Re: Facter on Alpine Linux requires root permissions given that we have the puppet-agent build-chain open sourced now, some enterprising entity might wanna try to build the puppet-agent themselves. 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) Gracefully fail and/or downgrade when newer agents to talk to older masters
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7255
Gracefully fail and/or downgrade when newer agents to talk to older masters
Change By:
Josh Cooper
If a newer agent speaks JSON by default and the older master speaks PSON by default when an agent submits its report to the master the first time it may send a JSON report the master cannot understand.*Options to consider** Some sort of initial protocol negotiation before the report is sent establishing the mutually agreed upon format* Leverage {{preferred_serialization_format}} setting (or another applicable setting) to switch the agent to speaking an older format by default*UPDATED** During a normal agent run, if we detect that the server is pre-5, and we're not currently using pson, then fallback to pson as the preferred serialization format for all future rest requests, e.g. {{file_metadata}}, {{report}}, and emit a warning.* During a cached catalog run, if the agent's {{report}} PUT request is the first request to the master for that run, eg there isn't a {{file_metadata}} request, then the {{report}} request will fail. Emit an error indicating that `preferred_serialization_format=pson` must be specified.* During all runs, if {{preferred_serialization_format=pson}}, then the agent should always prefer and use pson instead of json.
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+un
Jira (PUP-7255) Gracefully fail and/or downgrade when newer agents to talk to older masters
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7255
Gracefully fail and/or downgrade when newer agents to talk to older masters
Change By:
Josh Cooper
If a newer agent speaks JSON by default and the older master speaks PSON by default when an agent submits its report to the master the first time it may send a JSON report the master cannot understand.*Options to consider** Some sort of initial protocol negotiation before the report is sent establishing the mutually agreed upon format* Leverage {{preferred_serialization_format}} setting (or another applicable setting) to switch the agent to speaking an older format by default *UPDATED** During a normal agent run, if we detect that the server is pre-5, and we're not currently using pson, then fallback to pson as the preferred serialization format for all future rest requests, e.g. {{file_metadata}}, {{report}}, and emit a warning.* During a cached catalog run, if the agent's {{report}} PUT request is the first request to the master for that run, eg there isn't a {{file_metadata}} request, then the request will fail. Emit an error indicating that `preferred_serialization_format=pson` must be specified.* During all runs, if {{preferred_serialization_format=pson}}, then the agent should always prefer and use pson instead of json.
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...@go
Jira (PDB-3494) Determine if we need to replace the multi-host test removed by PDB-3491
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3494 Determine if we need to replace the multi-host test removed by PDB-3491 Change By: Rob Browning i.e. centos6-64mda-centos6-64a-ubuntu1204-64a This may or may not belong in the Puppet 5 epic, but I'm putting it there for now, and will discuss it with Russ next week . 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) Gracefully fail and/or downgrade when newer agents to talk to older masters
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7255 Gracefully fail and/or downgrade when newer agents to talk to older masters Change By: Josh Cooper Summary: SPIKE: Gracefully fail and/ or downgrade when newer agents to talk to older masters 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-3497) Drop support for JVM 7 from pdb itself
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3497 Drop support for JVM 7 from pdb itself Change By: Rob Browning Summary: Drop support for JVM7 JVM 7 from pdb itself 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-3497) Drop support for JVM7 from pdb itself
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3497 Drop support for JVM7 from pdb itself Change By: Rob Browning Summary: Document dropped Drop support for JDK7 JVM7 from pdb itself 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-1646) Update Add tests and TestRail ID's for specific facts tests
Title: Message Title John Duarte commented on FACT-1646 Re: Update Add tests and TestRail ID's for specific facts tests This is failing CI on all AIX systems in the acceptence/tests/facts/partitions.rb test. Expected partition '/dev/hd4' fact 'label' to match _expression_. Expected /\w+/ to match "/". 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-1646) Update Add tests and TestRail ID's for specific facts tests
Title: Message Title John Duarte assigned an issue to Eric Delaney Facter / FACT-1646 Update Add tests and TestRail ID's for specific facts tests Change By: John Duarte 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 (PDB-2398) PuppetDB should enable emergency deletion of historical data
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2398 PuppetDB should enable emergency deletion of historical data Change By: Russell Mull Sprint: Hopper 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-7644) puppet installing pip rather than pip3 packages using the pip3 provider only on the first run
Title: Message Title Morgan Rhodes moved an issue Puppet / PUP-7644 puppet installing pip rather than pip3 packages using the pip3 provider only on the first run Change By: Morgan Rhodes Key: CPR PUP - 426 7644 Project: Community Package Repository Puppet 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-7194) on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Branan Riley commented on PUP-7194 Re: on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters yeah. IIRC we don't actually have unicode locale files installed on them. It's something we should look in to, but I don't expect unicode or other i18n-related things to work right on AIX right now. 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Gary Larizza commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout I'm not sure how much work you think it would be, Henrik Lindberg, but if it's anything more than a trivial change, then probably not for 5. Would this be considered a backwards-incompatible change? Would it need to be in a major revision? 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-7194) on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Josh Cooper commented on PUP-7194 Re: on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters I believe the AIX hosts are not capable of full Unicode support, as we've had other issues. I'm inclined to close this unless Branan Riley thinks it should 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Josh Cooper commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings PMT fix merged to stable in https://github.com/puppetlabs/puppet/commit/8b8ee50e7748c73f256fb3d33438c519d41abf0a. 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-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title R.I.Pienaar commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] It pretty much does behave as you say. If you set in main it applies to all sections unless otherwise set specifically in a section. The non obvious thing is that config print is consulting only the main and user sections. Because it's a user utility it does that. It could perhaps print some hint but they would break a bunch of things as scripts will parse this output. You have to pick 1 section or run mode. Picking user seems correct but I can see how people might expect agent to be default - unless they happen to be on a master and then they expect master or something. Best to just specify what you want section/runmode wise 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-7194) on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Sean Griffin commented on PUP-7194 Re: on aix-71, aix-53: puppet lookup / hiera fails with key that contains utf-8 characters Josh CooperEthan Brown This was a CI failure. The acceptance test was modified to skip this test on this on this platform: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/utf8/utf8-in-function-args.rb#L7 and as far as I know has not run since. The same failure was happening on a few other platforms too. If you need help reproducing this, assign it to me. 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-7642) A Report containing rich-data should allow presence of unresolved custom types.
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7642 A Report containing rich-data should allow presence of unresolved custom types. Change By: Eric Delaney QA Risk Assessment Reason: change includes spect test QA Risk Assessment: Needs Assessment No Action QA Contact: 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 (PUP-7611) Can't turn off deprecation warnings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7611 Can't turn off deprecation warnings Change By: Eric Delaney QA Risk Assessment Reason: We should verify this works correctly now QA Risk Assessment: Needs Assessment Manual QA Contact: 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 (PUP-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6395 file type documentation does not have quotes around modes in doc comments Change By: Eric Delaney QA Risk Assessment: No Action 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-7643) acceptance tests fail recieving bracket array values
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-7643 acceptance tests fail recieving bracket array values Change By: John Duarte Assignee: John Duarte 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-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title John Duarte commented on PUP-7616 Re: Fix broken implementation of Property#change_to_s method This caused acceptance test failures on solaris 10. Example error: rg7rvyocyr2m076.delivery.puppetlabs.net (solaris10-64-1) 14:58:53$ puppet apply --verbose /tmp/apply_manifest.pp.INa4Tb Notice: Compiled catalog for rg7rvyocyr2m076.delivery.puppetlabs.net in environment production in 0.04 seconds Info: Applying configuration version '1497020334' Notice: /Stage[main]/Main/Zone[tstzone]/dataset: dataset changed tstpool/xx to ['tstpool/yy'] Notice: Applied catalog in 0.07 seconds rg7rvyocyr2m076.delivery.puppetlabs.net (solaris10-64-1) executed in 1.79 seconds Minitest::Assertion: err: rg7rvyocyr2m076.delivery.puppetlabs.net. Expected /dataset changed 'tstpool.xx'.* to .'tstpool.yy'./ to match "\e[mNotice: Compiled catalog for rg7rvyocyr2m076.delivery.puppetlabs.net in environment production in 0.04 seconds\e[0m\n\e[0;32mInfo: Applying configuration version '1497020334'\e[0m\n
Jira (PUP-7642) A Report containing rich-data should allow presence of unresolved custom types.
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7642 A Report containing rich-data should allow presence of unresolved custom 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-7642) A Report containing rich-data should allow presence of unresolved custom types.
Title: Message Title Thomas Hallgren commented on PUP-7642 Re: A Report containing rich-data should allow presence of unresolved custom types. Merged to master at 0ce345e. 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-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Paul Schaffer commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] It's admittedly an unlikely case, but I discovered this after a customer opened a ticket because they'd set the certname of the system to something other than the FQDN through declaring the certname in both the [agent] and [master] sections of puppet.conf prior to installing the agent. Though the system is reachable via mco at the certname and all of the contents of the ssl directory have the correct certname 'puppet config print certname' returns the FQDN, which is an inaccurate description of the state of the machine. One (or both) of the values in [agent] and [master] were sufficient to generate the desired certnames for the system, but the print command ignores them both unless you specifically designate the section. It would seem more accurate to default to the value set in [main], but to then return the value if set in any other section before defaulting to the FQDN. 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Nick Walker commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout Henrik Lindberg Without knowing most of the variables around when Puppet 5 is expected and how many other things need to get in, I'll just say that I'd rather us take our time and not rush a solution just to get it into Puppet 5. So, I guess I don't think it has to be 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-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Craig Dunn commented on PUP-7641 Re: Hiera 5 Global level is looked up even when not configured Henrik Lindberg Thanks for the clarification. Whilst I agree this can be solved by documentation, I would suggest that this should also be behaviour that should be changed. As a user it would make more sense to me if Puppet did nothing if there was no global level hiera.yaml and Puppet initially shipped/installed with a default hiera.yaml that the user can remove if they do not want any global level lookup. The fix you suggest (touching an empty hiera.yaml file) doesn't feel like a clean way going forward to me. 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-7643) acceptance tests fail recieving bracket array values
Title: Message Title John Duarte created an issue Puppet / PUP-7643 acceptance tests fail recieving bracket array values Issue Type: CI Blocker Assignee: John Duarte Created: 2017/06/09 7:45 AM Priority: Normal Reporter: John Duarte Acceptance tests expecting catalog application notices to return array elements are now failing due to language changes that return arrays in bracketed notation. Example error: Expected /ip changed 'ip.if.1:1.1.1.1'.* to .'ip.if.1:1.1.1.1', 'ip.if.2:1.1.1.2'./ to match "\e[mNotice: Compiled catalog for sviz1kae5v49d6z.delivery.puppetlabs.net in environment production in 0.04 seconds\e[0m\n\e[0;32mInfo: Applying configuration version '1496988604'\e[0m\n\e[mNotice: /Stage[main]/Main/Zone[tstzone]/ip: ip changed ip.if.1:1.1.1.1 to ['ip.if.1:1.1.1.1', 'ip.if.2:1.1.1.2']\e[0m\n\e[mNotice: Applied catalog in 0.17 seconds\e[0m\n". Job link
Jira (PUP-7642) A Report containing rich-data should allow presence of unresolved custom types.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7642 A Report containing rich-data should allow presence of unresolved custom types. Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/06/09 6:49 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Thomas Hallgren When an agent that deals with custom rich-data types (Objects) sends a report to the server, the server will not have a correct environment/loaders configured to instantiate the values that are contained in the report events. It currently does, which results in an error. The desired behavior is to retain the hash that is the result of serializing such objects. Add Comment
Jira (PUP-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7641
Hiera 5 Global level is looked up even when not configured
Change By:
Henrik Lindberg
I recently got stumped doing a training course trying to demonstrate moving global data to the environment layer and came across this behaviour - If this is intended behaviour then it really needs to be documented well because (for me) this was seems really confusing.h1. SummaryLookups will always prioritise data found in /etc/puppetlabs/puppet/data/ even if no global level lookup has been configured.h2. Set upVersion 4.10.1{code}[root@devagent puppetlabs]# puppet -V4.10.1{code}One hiera.yaml file at the environment level - no global configuration file.{code}[root@devagent puppetlabs]# find /etc/puppetlabs -name hiera.yaml/etc/puppetlabs/code/environments/production/hiera.yaml[root@devagent puppetlabs]# cat /etc/puppetlabs/code/environments/production/hiera.yamlversion: 5hierarchy: - name: "test"path: "common.yaml"data_hash: yaml_datadatadir: hieradata{code}h2. Steps1) Populate the environment data{code}[root@devagent puppetlabs]# echo -n "foo::bar: from the environment" > /etc/puppetlabs/code/environments/production/hieradata/common.yaml[root@devagent puppetlabs]# puppet lookup foo::bar--- from the environment...{code}2) ... so far so good ... now if we leave some data in the global layer, which we've not configured anywhere, it's used by default{code}[root@devagent puppetlabs]# echo -n "foo::bar: WTF?" > /etc/puppetlabs/puppet/data/common.yaml[root@devagent puppetlabs]# puppet lookup foo::bar--- WTF?...{code}With explain turned on{code}[root@devagent puppetlabs]# puppet lookup foo::bar --explainSearching for "lookup_options" Global Data Provider (hiera configuration version 5)Hierarchy entry "Common" Path "/etc/puppetlabs/puppet/data/common.yaml"Original path: "common.yaml"No such key: "lookup_options" Environment Data Provider (hiera configuration version 5)Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml"Hierarchy entry "test" Path "/etc/puppetlabs/code/environments/production/hieradata/common.yaml"Original path: "common.yaml"No such key: "lookup_options" Module data provider for module "foo" not foundSearching for "foo::bar" Global Data Provider (hiera configuration version 5)Hierarchy entry "Common" Path "/etc/puppetlabs/puppet/data/common.yaml"Original path: "common.yaml"Found key: "foo::bar" value: "WTF?"{code}So it seems the global level will always get looked up even when the user hasn't configured it and will use defaults - so if old / obsolete data is found in the global default datadir then it gets prioritised over whats configured and this, to me, is confusing behaviour.
Jira (PUP-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Henrik Lindberg commented on PUP-7641 Re: Hiera 5 Global level is looked up even when not configured Craig Dunn Puppet behaves as intended - we need to point out the behaviour in documentation. 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-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7641 Hiera 5 Global level is looked up even when not configured Change By: Henrik Lindberg Component/s: DOCS 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-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7641 Hiera 5 Global level is looked up even when not configured Change By: Henrik Lindberg Priority: Major Normal 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-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Henrik Lindberg commented on PUP-7641 Re: Hiera 5 Global level is looked up even when not configured What needs to be documented is that there is the need to have an empty global hiera.yaml as a default hiera.yaml will be used otherwise. Ping Jorie Tappa / Jean Bond - not sure who maintains docs for hiera/lookup. 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-7641) Hiera 5 Global level is looked up even when not configured
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7641 Hiera 5 Global level is looked up even when not configured Change By: Henrik Lindberg Summary: Hiera 5 Global level is looked up even when not configured 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-7641) Global level is looked up even when not configured
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-7641 Global level is looked up even when not configured Change By: Henrik Lindberg Key: HI PUP - 573 7641 Project: Hiera Puppet 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 (HI-573) Global level is looked up even when not configured
Title: Message Title Craig Dunn created an issue Hiera / HI-573 Global level is looked up even when not configured Issue Type: Bug Assignee: Unassigned Created: 2017/06/09 2:51 AM Priority: Major Reporter: Craig Dunn I recently got stumped doing a training course trying to demonstrate moving global data to the environment layer and came across this behaviour - If this is intended behaviour then it really needs to be documented well because (for me) this was seems really confusing. Summary Lookups will always prioritise data found in /etc/puppetlabs/puppet/data/ even if no global level lookup has been configured. Set up Version 4.10.1 [root@devagent puppetlabs]# puppet -V 4.10.1 One hiera.yaml file at the environment level - no global configuration file.
Jira (PUP-7632) FreeBSD package providers are outdated
Title: Message Title
Helmut Ritter commented on PUP-7632
Re: FreeBSD package providers are outdated
Hello Josh,
package { $package:
ensure => installed,
#provider => 'ports'
provider => 'portupgrade'
#provider => 'pkgng'
}
pkg_info does not exist (is deprecated since FreeBSD >=10) which results in
Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/pkg_info does not exist Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/sbin/
Jira (PUP-7620) Add a `unique` function that works with all kinds of iterables
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7620 Add a `unique` function that works with all kinds of iterables 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.
