Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows
Title: Message Title Jeremy Adams commented on PUP-6447 Re: Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows Recently when doing an integration in _javascript_ that wrote a facter fact in JSON, I encountered this issue. Facter would not tolerate UTF-8 with a BOM for the structured JSON fact. var command = "New-Item -path '" + factsDir + "' -type directory -force \n" + "$MyPath = '" + factsFile + "' \n" + "$MyFile = " + oneLineFacts + " \n" + "$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding($False) \n" + "[System.IO.File]::WriteAllLines($MyPath, $MyFile, $Utf8NoBomEncoding)"; Add Comment
Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows
Title: Message Title Erick Banks commented on PUP-6447 Re: Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows Encountered this again in Windows UTF-8 testing. Saved DSC manifest "UTF-8 w/ BOM" and errored out with: Error: Could not parse for environment production: Syntax error at '∩' at C:/Use rs/Administrator/Desktop/blah.pp:1:1 on node x9bshj31wdcfefy.delivery.puppetlabs .net Saved to "UTF-8" and executed same manifest successfully. 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-6967) Reload puppetserver in puppet acceptance tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6967 Reload puppetserver in puppet acceptance tests Change By: Josh Cooper Labels: maintenance 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Rob Mattson commented on PUP-6960 Re: Puppet language error during agent run (success during apply) A comment in three sections; 1. Hi Henrik, Thankyou for your assistance. Are you using future parser? No Does the catalog contain what is expected? yes, we used puppet module install to determine what pre-reqs were required. The certs class has sane defaults, which are implemented correctly by apply. Are the required resource types synced to the agent as they should? Yes. we've compared the sha1sums of the libs. both type and provider. they are the same checksums. What happens if you have a catalog in a file (containing what is expected) and then applying it on the agent? i believe this is covered by Eric in his post above. 2. I was lucky to catch Eric in on IRC. Thankyou Eric. 3. My results of downlgrading the puppet rpm are journaled below, and done twice. Firstly with diff applied from above, then repeaded with the default init.pp from the katelo upstream module. In both cases i've left Erics code to help highlight the issue. https://gist.github.com/ahpook/4eaf2e1fa00891377dec3107230ce2d4 with the further change of .inspect to .class in the example code hyperlinked in this line. yum downgrade puppet-3.8.6-1.el7; reboot Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected Ca resource, got String at /etc/puppet/modules/certs/manifests/init.pp:156 #yum downgrade puppet-3.8.5-1.el7 Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected
Jira (PUP-6494) exec resources leak the command string when execution fails
Title: Message Title Josh Cooper commented on PUP-6494 Re: exec resources leak the command string when execution fails For this specific issue, can we just not echo the executed command if the command fails? Is it acceptable to only echo the command if debug is enabled (which also prints out the commands being executed)? 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Eric Sorenson commented on PUP-6960 Re: Puppet language error during agent run (success during apply) I got a reproduction setup, thanks for the detailed instructions Rob. Things i have tried so far: future parser turned on, no difference running under webrick 'puppet master' instead of puppetserver in case there was a difference between MRI and jruby renamed the 'ca' parameter to 'ca_reference' in case there was a collision between the type named 'ca' and its parameter named 'ca' run puppet master --compile > /tmp/catalog.json puppet apply --catalog /tmp/catalog.json - the item is indeed serialized in the catalog as a string, but so is every other resource reference. 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-6967) Reload puppetserver in puppet acceptance tests
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-6967 Reload puppetserver in puppet acceptance tests Change By: Josh Cooper Assignee: Josh Cooper 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT Change By: Moses Mendoza Assignee: Moses Mendoza 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-6967) Reload puppetserver in puppet acceptance tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6967 Reload puppetserver in puppet acceptance tests Change By: Josh Cooper Fix Version/s: PUP 4.8.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-6967) Reload puppetserver in puppet acceptance tests
Title: Message Title Josh Cooper created an issue Puppet / PUP-6967 Reload puppetserver in puppet acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2016/12/01 4:52 PM Priority: Normal Reporter: Josh Cooper We spend ~30 mins starting puppetserver across the full acceptance test suite. Now that BKR-703 is fixed, we should update our beaker dependency and use reload. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza commented on PUP-4742 Re: Bring semantic_puppet library into Puppet this has made it successfully through the puppet component CI: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_pkg-van-promote_master/12/ - i expect puppet-agent suite to pick this up tonight so we should hopefully be able to resolve this tomorrow 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Rob Mattson commented on PUP-6960 Re: Puppet language error during agent run (success during apply) note for reference from IRC; --- init.pp-backup 2016-12-02 10:02:01.445127469 +1100 +++ init.pp 2016-12-02 10:03:11.601126587 +1100 @@ -147,25 +147,16 @@ generate => $certs::generate, deploy=> $certs::deploy, password_file => $ca_key_password_file, - } - - $default_ca = Ca[$default_ca_name] - - if
Jira (PUP-6948) generate() should allow calls with variable number of arguments
Title: Message Title Henrik Lindberg commented on PUP-6948 Re: generate() should allow calls with variable number of arguments Great. That means I will close this as a "won't do". 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-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-1534 Acceptance: Facter seg faults on Cisco XR during some config file tests Change By: Kurt Wall Assignee: Kurt Wall 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-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title
Kurt Wall updated an issue
Facter / FACT-1534
Acceptance: Facter seg faults on Cisco XR during some config file tests
Change By:
Kurt Wall
Comment:
Re-opening. That doesn't give me a warm feeling. This used to work and suddenly it doesn't. What's changed? [~stan] and I kicked it around and he found that it started failing after facter 3.5.0-12-ge8a11ca, that is, at facter 3.5.0-33-g01c09a2. {{git diff}} says:{code}$ LESS="-R -X" git diff e8a11ca 01c09a2diff --git a/CMakeLists.txt b/CMakeLists.txtindex 487aecb..fdeaa18 100644--- a/CMakeLists.txt+++ b/CMakeLists.txt@@ -130,9 +130,6 @@ set(FACTER_CXX_FLAGS "${LEATHERMAN_CXX_FLAGS}") add_definitions(${LEATHERMAN_DEFINITIONS})-# Include vendor libraries-set(RAPIDJSON_INCLUDE_DIRS "${PROJECT_SOURCE_DIR}/vendor/rapidjson-0.11/include")- # # Add cpplint and cppcheck targets #{code}Would that removed {{include}} produce this?
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-6965) Improve parser error messages
Title: Message Title Henrik Lindberg assigned an issue to Tim Purkerson Puppet / PUP-6965 Improve parser error messages Change By: Henrik Lindberg Assignee: Tim Purkerson 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-6965) Improve parser error messages
Title: Message Title Henrik Lindberg commented on PUP-6965 Re: Improve parser error messages Those 4 errors were logged for sure. The line numbers are there. The number of errors to log before giving up is set to 10. It can be set to one to only report the first - in which case there is no aggregate error message like the one in the Description above. When there is an aggregation of errors - we could naturally include all the files/lines and messages in the message for the aggregate. Would that be a better solution than saying "giving up" ? And in this case. Didn't "puppet parser validate params.pp" reveal the individual errors? 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 Russell Mull commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators From a different system, which is much fresher, but showing the same issue. In this case, it's trying to copy into clientbucket/9/e/: PS C:\ProgramData\PuppetLabs\puppet\cache> Get-Acl . | select * Get-Acl . | select * PSPath : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet\cache PSParentPath: Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\PuppetLabs\puppet PSChildName : cache PSDrive : C PSProvider : Microsoft.PowerShell.Core\FileSystem CentralAccessPolicyId :
Jira (PUP-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
Title: Message Title Henrik Lindberg commented on PUP-6953 Re: Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency We could do a fallback where instead of an error, there would be a warning telling the user that it would be best to add a dependency. The function call would still be made as if the dependency was there (only resolved a bit more slowly, and with the exposure to the potential problem of not finding the right function if there are multiple functions with the same global name in modules on the module path). What PUP-6964 suggests (remove the restriction) seems like giving up on striving for quality... 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency I am ambivalent though since right now it is only 4.x functions (ruby or puppet) that requires the dependencies. I also fear that the decision to allow no-dependencies to mean "all/any" has the effect that people remove rather than correct the list of dependencies. I would however like us to move in the opposite more strict direction and rather evolve the metadata.json capabilities with things like optional dependencies. But maybe the route there is to take a step back first, and increase the strictness in sync with better capabilities in metadata.json. Here I am not sure what the right balance between strictness/quality and usability is. Ping Eric Sorenson (in response to your 0.02$ on PUP-6953). Also note - as long as we allow any module to contain top scope named definitions (functions as well as other) there is always the issue of potential clashes. Strictly using metadata.json gives modules a chance to tell which thing they actually want rather than having to rely on the undefined (somewhat random) order to search modules that is obtained by stepping through modulepath. The current implementation is deterministic because it searches in the order the dependencies are listed. 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-6966) Tidy (and File) cannot remove (fifo and) socket files
Title: Message Title Thomas Kishel created an issue Puppet / PUP-6966 Tidy (and File) cannot remove (fifo and) socket files Issue Type: Bug Assignee: Unassigned Components: Types and Providers Created: 2016/12/01 2:35 PM Priority: Normal Reporter: Thomas Kishel Problem: (Reported to Customer Support) The Tidy resource throws an error: "Error: Could not back up files of type socket." when managing /tmp and it encounters a socket file. Tidy then fails to remove anything else after it errors. However, Tidy should not be backing up any files given the backup attribute. That kind of defeats the purpose of using the Tidy resource, doesn't it? I understand about not being able to ensure special file existence (creation), but I would think special file absence should be easy. I was hoping Tidy would be the answer (it sure seems like it should) especially since I'm telling Puppet to not backup anything it's deleting. Word. Example: Create a test file: python -c "import socket as s; sock = s.socket(s.AF_UNIX);
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency The behavior is there to keep everyone honest. What is the point of having metadata if it not enforced? You can lie as much as you like without any consequences. Where should a user be looking for the functions and possibly other constructs named in the global namespace? If strict module namespacing was enforced it would never be a problem. The case I am thinking about is the user that consumes a module. That module makes use of a function foo(). Where did it come from? At least with having to declare module dependencies the list of modules to explore is greatly reduced. Also, the author of a module should be very much aware of making the module depend on another. It is a conscious design and maintenance decision. The current design of allowing no dependencies in metadata.json to mean "look everywhere" is because we interpret that as the module author saying "I did not bother helping you - go fish". I think that is bad. 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-3035) PDB should use gzip when replicating data
Title: Message Title Chris Cowell updated an issue PuppetDB / PDB-3035 PDB should use gzip when replicating data Change By: Chris Cowell QA Risk Assessment: Needs Assessment QA Contact: Sam Woods 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
Russell Mull commented on PUP-6729
Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
As (I think) a consequence of this issue, if you sometimes run puppet from the service (or from the orchestrator) but sometimes run 'puppet agent -t' as Administrator, the permissions can get mixed up. The case I encountered a few times was corruption of the permissions on puppet/cache/clientbucket: (named .bak here) {pre} C:\ProgramData\PuppetLabs\puppet\cache\clientbucket.bak>ls -l ls -l total 0 drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:38 1 drwxr-x---+ 1 Administrator None 0 Dec 1 20:43 3 drwxr-x---+ 1 Administrator None 0 Dec 1 20:58 4 drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:31 5 drwxr-x---+ 1 Administrator None 0 Dec 1 21:09 6 drwxr-x---+ 1 Administrator None 0 Dec 1 17:25 7 drwxr-x---+ 1 Administrator None 0 Dec 1 21:11 8 drwxr-x---+ 1 Administrator None 0 Dec 1 21:02 9 drwxr-x---+ 1 Administrator None 0 Dec 1 20:54 a drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 21:39 b drwxr-x---+ 1 Administrators SYSTEM 0 Dec 1 18:27 c{pre}
This resulted in getting 'permission denied' errors when trying to copy a config file into clientbucket before changing it.
This is a very common workflow, and if it can so easily bork the agent installation, we should fix it.
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-6965) Improve parser error messages
Title: Message Title Tim Purkerson created an issue Puppet / PUP-6965 Improve parser error messages Issue Type: Improvement Assignee: Unassigned Created: 2016/12/01 2:23 PM Priority: Normal Reporter: Tim Purkerson Add more detail to the error messages that will allow much quicker debugging. Such as line numbers where the error occurs or suggested diagnostic flags. For example, received the error message: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment pr001: Found 4 errors. Giving up in /app/puppet/environments/apps/test/pr001/manifests/params.pp on node pr.server.com Those four errors took several hours to track down in the very large params.pp file. Having line numbers would have made the debugging task much easier. Add Comment
Jira (PUP-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
Title: Message Title Nick Walker commented on PUP-6953 Re: Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency Eric Sorenson I created PUP-6964 to change the behavior completely and marked it as blocking this ticket. If we choose to implement that ticket then I believe this ticket is just an incompatible change. I would like to advocate for the prioritization of one of the tickets as the current behavior is quite confusing. 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Nick Walker created an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Issue Type: Improvement Assignee: Unassigned Created: 2016/12/01 1:47 PM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem See PUP-6952 and PUP-6953 for backgound but essentially, puppet can't find puppet 4.x functions in other modules unless they are declared as a dependency of the module trying to use the function. OR if the module just doesn't declare any dependencies. The Change The behavior of finding functions should not be dependent on the modules dependencies as defined in metadata.json for the module. We should search the entire modulepath for a function and not just in the declared dependencies. We can retain some of the optimization by searching in declared dependencies first and then if not found extend the search to all modules. This makes the optimization opt-in and not required.
Jira (PUP-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Ethan Brown commented on PUP-6741 Re: When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Merged to master in https://github.com/puppetlabs/puppet/commit/7ba780bfa787197eba48e64236a3d3b9987870fd 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-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
Title: Message Title Eric Sorenson commented on PUP-6953 Re: Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency My €0.02 - I feel like this implementation has overloaded the semantics of metadata.json Dependencies to bad effect. Up till now, the only usage of the Dependencies field has been to *download dependent modules from the forge. Now the field is also used at **runtime*, in the critical path of catalog compilation. While I agree with the general principle that "things should explicitly declare dependencies", I think this behaviour is wrong, especially since it's primarily in service of a performance optimization. (As an aside, since the type_of() function is not a namespaced function, how would a user – or the puppetmaster, for that matter – know that it came from stdlib?) 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Moses Mendoza commented on PUP-4742 Re: Bring semantic_puppet library into Puppet merged (again) to master at https://github.com/puppetlabs/puppet/commit/61e715c0468f4c39a22ac8f46b7594f4a2202d99 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-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title Stan Duffy assigned an issue to Kurt Wall Facter / FACT-1534 Acceptance: Facter seg faults on Cisco XR during some config file tests Change By: Stan Duffy Assignee: Stan Duffy Kurt Wall 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-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title Michael Smith commented on FACT-1534 Re: Acceptance: Facter seg faults on Cisco XR during some config file tests That should've had absolutely no effect on anything. The directory it pointed to no longer existed. 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-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title
Kurt Wall commented on FACT-1534
Re: Acceptance: Facter seg faults on Cisco XR during some config file tests
That doesn't give me a warm feeling. This used to work and suddenly it doesn't. What's changed? Stan Duffy and I kicked it around and he found that it started failing after facter 3.5.0-12-ge8a11ca, that is, at facter 3.5.0-33-g01c09a2. git diff says:
$ LESS="-R -X" git diff e8a11ca 01c09a2
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 487aecb..fdeaa18 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -130,9 +130,6 @@ set(FACTER_CXX_FLAGS "${LEATHERMAN_CXX_FLAGS}")
add_definitions(${LEATHERMAN_DEFINITIONS})
-# Include vendor libraries
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6963
Puppet doesn't detect systemd as default service provider on CoreOS
Change By:
William Hopper
Acceptance Criteria:
Puppet should use the systemd service provider to query and interact with services in CoreOS. This can be verified by running {{puppet resource service --param provider}} to see which provider is being used to manager services.
Release Notes Summary:
Previously, the systemd service provider did not specify itself as the default for CoreOS systems. Since systemd is the default service manager in CoreOS, this change updates the provider to add the CoreOS family to its defaults.
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
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Change By: William Hopper Assignee: William Hopper Team: Puppet Developer Support Sprint: PDS 2016-12-14 Fix Version/s: PUP 4.9.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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title William Hopper updated an issue Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Change By: William Hopper Labels: maintenance Story Points: 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Eric Sorenson commented on FACT-1538 Re: Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't IMO these top-level 'ipaddress' and 'ipaddress6' facts are somewhat doomed to fail because they try to divine user intent and thus will never get it 100% right. See also: FACT-380 FACT-1167 FACT-1468 etc etc. Now that we present the whole network interface info as a structured fact, please change the logic in your 'whereami' fact to use that structure rather than relying on facter to guess. 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-6616) Acceptance: Catalog concurrency test consistently fails on Cisco XR
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6616 Acceptance: Catalog concurrency test consistently fails on Cisco XR Change By: Kenn Hussey Team: Agent & Platform 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-6616) Acceptance: Catalog concurrency test consistently fails on Cisco XR
Title: Message Title Kenn Hussey commented on PUP-6616 Re: Acceptance: Catalog concurrency test consistently fails on Cisco XR Stan Duffy ping. 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1538 Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't Change By: Geoff Nichols Labels: maintenance 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1538 Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't Change By: Geoff Nichols Team: Agent & Platform 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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove commented on PUP-6963 Re: Puppet doesn't detect systemd as default service provider on CoreOS I've opened a PR with the relevant changes to address this at https://github.com/puppetlabs/puppet/pull/5402 I've tested it successfully with the following image https://hub.docker.com/r/garethr/puppet-agent-coreos/ which was built from the following Dockerfile: from puppet/puppet-agent RUN sed -i "/defaultfor :osfamily => :suse/a \ \ defaultfor :osfamily => :coreos" /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb 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,
Jira (PUP-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title Eric Sorenson commented on PUP-6951 Re: No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted” Hi Jens - there is a module which I think will help your use-case. Can you check out the puppetlabs-mount_providers module which will let you manage the mounted state separately from the fstab entry? This separation can help prevent spurious events like the one you're seeing: https://forge.puppet.com/puppetlabs/mount_providers/types 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-6959) Puppet::FileSystem.open / exclusive_open / replace_file should use Windows file system support for setting `mode`
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6959 Puppet::FileSystem.open / exclusive_open / replace_file should use Windows file system support for setting `mode` Change By: Geoff Nichols Sprint: AP Triage Grooming 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-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title Eric Sorenson assigned an issue to Jens Offenbach Puppet / PUP-6951 No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted” Change By: Eric Sorenson Assignee: Jens Offenbach 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-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6951 No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted” Change By: Geoff Nichols Sprint: AP 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-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6951 No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted” Change By: Geoff Nichols Team: Agent & Platform 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-6944) Reduce the windows spec matrix
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6944 Reduce the windows spec matrix Change By: Geoff Nichols Story Points: 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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title Gareth Rushgrove created an issue Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Issue Type: Bug Assignee: Unassigned Created: 2016/12/01 10:44 AM Priority: Normal Reporter: Gareth Rushgrove CoreOS is correctly identified by facter (https://github.com/puppetlabs/facter/blob/11288d2a33caec577fe696bd02e4bed12e5ac12d/lib/inc/internal/facts/linux/os_coreos.hpp) but when trying to manage services Puppet detects both init.d and systemd and defaults to init.d. In reality CoreOS uses systemd for all service management. Expected behaviour: The service provider should use systemd as the default provider for CoreOS Add Comment This
Jira (PUP-6944) Reduce the windows spec matrix
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6944 Reduce the windows spec matrix Change By: Geoff Nichols Sprint: AP Triage Grooming 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-1537) Facter 3.5.0 tarball is broken
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1537 Facter 3.5.0 tarball is broken Change By: Geoff Nichols Sprint: AP Triage 2016-12-14 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-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Geoff Nichols Team: Agent & Platform 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-6932) Gem Provider Windows Ruby Path
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6932 Gem Provider Windows Ruby Path Change By: Geoff Nichols Sprint: AP Triage Grooming 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-6927) Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename
Title: Message Title Moses Mendoza commented on PUP-6927 Re: Recursively copying a directory to Windows 7 nodes fails on files with tilde in the filename Hi Colin Conway - just checking in to see if you'd figured this o 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-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Geoff Nichols Labels: maintenance needs_repro testing vagrant 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-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Geoff Nichols Sprint: AP 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 (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Geoff Nichols Environment: Vagrant (virtualbox) on Windows, Facter 3. 2 5.x , Custom ( Ruby ) facts. 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-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Change By: Geoff Nichols Story Points: 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-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5993 Possible intermittent test failure in registry_spec.rb Change By: Geoff Nichols Sprint: AP Triage Grooming 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-6962) Create Jenkins jobs for running puppet test tiers
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6962 Create Jenkins jobs for running puppet test tiers 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-6962) Create Jenkins jobs for running puppet test tiers
Title: Message Title John Duarte created an issue Puppet / PUP-6962 Create Jenkins jobs for running puppet test tiers Issue Type: Task Assignee: Unassigned Created: 2016/12/01 10:08 AM Priority: Normal Reporter: John Duarte Create Jenkins jobs to execute puppet acceptance test suite in a tiered fashion based on risk tags. Tags should be mapped to job execution in the following manner: tag 'risk:high' should be run on a per commit basis tag 'risk:medium' should be run on a nightly basis tag 'risk:low' should be run on a weekly basis The JJB definition for these jobs should include the appropriate line to execute tests based on beaker tag. This line looks like the following: - project: <<:
Jira (FACT-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests
Title: Message Title Stan Duffy assigned an issue to Stan Duffy Facter / FACT-1534 Acceptance: Facter seg faults on Cisco XR during some config file tests Change By: Stan Duffy Assignee: Stan Duffy 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-6961) Add test tier tags to puppet acceptance tests
Title: Message Title John Duarte commented on PUP-6961 Re: Add test tier tags to puppet acceptance tests Moses Mendoza, I will work with you to ratify the correct risk classification of the puppet acceptance tests for tiered execution. 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-6961) Add test tier tags to puppet acceptance tests
Title: Message Title John Duarte created an issue Puppet / PUP-6961 Add test tier tags to puppet acceptance tests Issue Type: Task Assignee: John Duarte Created: 2016/12/01 8:56 AM Priority: Normal Reporter: John Duarte In order to accommodate the tiered execution of puppet acceptance tests, the tests themselves must be tagged with the appropriate beaker risk tag. These tags will then be used to determine which tests will be run in CI by cadence. tag 'risk:high' will be run on a per commit basis tag 'risk:medium' will be run on a nightly basis tag 'risk:low' will be run on a weekly basis This ticket is specifically for the task of adding the appropriate risk tag to all of the beaker acceptance tests for the puppet repo. Add Comment
Jira (PUP-6949) generate() should optionally fail if program writes to stderr
Title: Message Title Henrik Lindberg commented on PUP-6949 Re: generate() should optionally fail if program writes to stderr Yes, that is what I meant (updated my comment). 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-6948) generate() should allow calls with variable number of arguments
Title: Message Title Matthias Hörmann commented on PUP-6948 Re: generate() should allow calls with variable number of arguments The splat operator seems to be exactly what I need for my use case. Thanks for the explanation. I wasn't aware of it. 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-6949) generate() should optionally fail if program writes to stderr
Title: Message Title Matthias Hörmann commented on PUP-6949 Re: generate() should optionally fail if program writes to stderr Assuming you mean stdout, stderr and exitcode, that would give us even more flexibility. I like the idea. 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-6949) generate() should optionally fail if program writes to stderr
Title: Message Title Henrik Lindberg commented on PUP-6949 Re: generate() should optionally fail if program writes to stderr I can imagine changing generate to a 4x API so it accepts a lambda. That lambda could take 3 parameters (or variable amount of them) and giving it the stdout, stdin and exitcode values from the executed program. Would that work? Then it is possible to decide what to use as the result, or if should error. 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-6948) generate() should allow calls with variable number of arguments
Title: Message Title
Henrik Lindberg commented on PUP-6948
Re: generate() should allow calls with variable number of arguments
The generate() function already takes a variable number of arguments. Don't understand what you are proposing.
If you mean you want to expand a number of arguments in an array as if they are extra arguments you can do so in 3.x with future parser and in 4.x using the so called "splat" operator.
Example using puppet function as illustration
# capture a variable number of arguments into an array
function example(*$args) {
notice $args
}
$arr = [4,5,6]
example(1,2,3,*$arr)
puppet apply pup6948.pp
Notice: Scope(Class[main]): [1, 2, 3, 4, 5, 6]
Jira (PUP-6948) generate() should allow calls with variable number of arguments
Title: Message Title Henrik Lindberg assigned an issue to Matthias Hörmann Puppet / PUP-6948 generate() should allow calls with variable number of arguments Change By: Henrik Lindberg Assignee: Matthias Hörmann 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title Henrik Lindberg commented on PUP-6960 Re: Puppet language error during agent run (success during apply) The differences between an apply and one where the catalog comes from a master compile are: in apply the created catalog is not serialized and deserialized the apply takes place in the same environment as the compilation - will everything loaded into memory intact with a remote compilation, the catalog is deserialized and resources are created and acted on Since this is failing during the apply of the remote catalog there are a couple of things to look at: Are you using future parser? Does the catalog contain what is expected? Are the required resource types synced to the agent as they should? What happens if you have a catalog in a file (containing what is expected) and then applying it on the agent? You may get faster help by hopping onto Slack or IRC as you can get interactive help from members of the community to help you pinpoint what is going wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6960) Puppet language error during agent run (success during apply)
Title: Message Title Henrik Lindberg assigned an issue to Rob Mattson Puppet / PUP-6960 Puppet language error during agent run (success during apply) Change By: Henrik Lindberg Assignee: Rob Mattson 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-6960) Puppet language error during agent run (success during apply)
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6960
Puppet language error during agent run (success during apply)
Change By:
Henrik Lindberg
We are trying to deploy an instance centos that uses puppet to install and configure services. We use puppet apply to setup and configure the system until passenger is available to serve responses from apache.We receive the following error * {code} Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected Ca resource at /etc/puppet/modules/certs/manifests/init.pp:167 * {code} Running this code with puppet agent *fails*, however a puppet apply works as expected.The failure is perplexing. This code is verbatim from upstream katello so it is widely used. The failure is repeatable.To reproduce this issue;1. We install and configure networking on a bare CentOS host from an ISO.2. Yum update.3. sudo rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm4. yum install puppetserver5. puppet module install katello-certs –verboseoutput:{code}Notice: Preparing to install into /etc/puppet/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Info: Resolving dependencies ...Info: Preparing to install ...Notice: Installing -- do not interrupt .../etc/puppet/modules└─┬ katello-certs (v0.7.2) ├─┬ evenup-trusted_ca (v1.99.0) │ └── puppetlabs-stdlib (v4.13.1) ├── katello-common (v0.2.0) ├── puppet-extlib (v0.11.3) ├── puppetlabs-concat (v2.2.0) └─┬ theforeman-foreman (v6.0.0)├── puppetlabs-apache (v1.10.0)├── puppetlabs-apt (v2.3.0)├── puppetlabs-postgresql (v4.8.0)└─┬ theforeman-tftp (v1.8.2) └── puppetlabs-xinetd (v2.0.0){code}6. Configure dnsmasq locally to point the names ‘foreman’ and ‘puppet’ to 127.0.0.1.7. Configure manifest{code}# cat <> /etc/puppet/manifests/site.ppnode puppet {class{ 'certs':}}{code}8. Systemctl start puppetserver9. Puppet agent–t –debug –trace Output{code}...snip...Debug: /File[/etc/pki/katello/private/katello-default-ca.pwd]/seltype: Found seltype default 'cert_t' for /etc/pki/katello/private/katello-default-ca.pwdDebug: /File[/etc/pki/katello/private/katello-default-ca.pwd]/selrange: Found selrange default 's0' for /etc/pki/katello/private/katello-default-ca.pwd*Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected Ca resource at /etc/puppet/modules/certs/manifests/init.pp:167*/var/lib/puppet/lib/puppet/type/certs_common.rb:44:in `block (3 levels) in '/usr/share/ruby/vendor_ruby/puppet/parameter.rb:465:in `validate'/usr/share/ruby/vendor_ruby/puppet/parameter.rb:500:in `value='/usr/share/ruby/vendor_ruby/puppet/type.rb:654:in `[]='/usr/share/ruby/vendor_ruby/puppet/type.rb:2272:in `block in set_parameters'...snip...{code}Specific questions to IRC at #theforeman, #theforeman-dev and theforeman@googlegroups has yielded no response.I suspect it is a puppet language/ruby issue whereby the parameter 'ca' is not of the type Puppet::Resource for an agent run but is for an apply?More generally, we are invoking classes in the style of katello-answers.yaml to install and configure other components. Which works well with puppet apply, however fails with puppet agent. The above instructions are to reproduce the issue we experience.
Jira (PUP-6960) Puppet language error during agent run (success during apply)
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6960
Puppet language error during agent run (success during apply)
Change By:
Henrik Lindberg
We are trying to deploy an instance centos that uses puppet to install and configure services. We use puppet apply to setup and configure the system until passenger is available to serve responses from apache.We receive the following error *Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected Ca resource at /etc/puppet/modules/certs/manifests/init.pp:167*Running this code with puppet agent *fails*, however a puppet apply works as expected.The failure is perplexing. This code is verbatim from upstream katello so it is widely used. The failure is repeatable.To reproduce this issue;1. We install and configure networking on a bare CentOS host from an ISO.2. Yum update.3. sudo rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm4. yum install puppetserver5. puppet module install katello-certs –verbose output: {code} Notice: Preparing to install into /etc/puppet/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Info: Resolving dependencies ...Info: Preparing to install ...Notice: Installing -- do not interrupt .../etc/puppet/modules└─┬ katello-certs (v0.7.2) ├─┬ evenup-trusted_ca (v1.99.0) │ └── puppetlabs-stdlib (v4.13.1) ├── katello-common (v0.2.0) ├── puppet-extlib (v0.11.3) ├── puppetlabs-concat (v2.2.0) └─┬ theforeman-foreman (v6.0.0)├── puppetlabs-apache (v1.10.0)├── puppetlabs-apt (v2.3.0)├── puppetlabs-postgresql (v4.8.0)└─┬ theforeman-tftp (v1.8.2) └── puppetlabs-xinetd (v2.0.0) {code} 6. Configure dnsmasq locally to point the names ‘foreman’ and ‘puppet’ to 127.0.0.1.7. Configure manifest {code} # cat <> /etc/puppet/manifests/site.ppnode puppet {class{ 'certs':}} EOF {code} 8. Systemctl start puppetserver9. Puppet agent–t –debug –trace Output ; < {code}... snip /> ... Debug: /File[/etc/pki/katello/private/katello-default-ca.pwd]/seltype: Found seltype default 'cert_t' for /etc/pki/katello/private/katello-default-ca.pwdDebug: /File[/etc/pki/katello/private/katello-default-ca.pwd]/selrange: Found selrange default 's0' for /etc/pki/katello/private/katello-default-ca.pwd*Error: Failed to apply catalog: Parameter ca failed on Ca[katello-server-ca]: Expected Ca resource at /etc/puppet/modules/certs/manifests/init.pp:167*/var/lib/puppet/lib/puppet/type/certs_common.rb:44:in `block (3 levels) in '/usr/share/ruby/vendor_ruby/puppet/parameter.rb:465:in `validate'/usr/share/ruby/vendor_ruby/puppet/parameter.rb:500:in `value='/usr/share/ruby/vendor_ruby/puppet/type.rb:654:in `[]='/usr/share/ruby/vendor_ruby/puppet/type.rb:2272:in `block in set_parameters' < ... snip /> ... {code} Specific questions to IRC at #theforeman, #theforeman-dev and theforeman@googlegroups has yielded no response.I suspect it is a puppet language/ruby issue whereby the parameter 'ca' is not of the type Puppet::Resource for an agent run but is for an apply? More generally, we are invoking classes in the style of katello-answers.yaml to install and configure other components. Which works well with puppet apply, however fails with puppet agent. The above instructions are to reproduce the issue we
Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)
Title: Message Title Henrik Lindberg commented on PUP-6538 Re: deprecate hiera_xxx functions (in favour of lookup) Thomas Hallgren This should be actionable now. Nicholas Fagerlund We expect the hiera_xxx functions to be removed in Puppet 6.0.0 (unless things happen along the way that makes us make a different decision and keep them in deprecated stated longer than that). 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-6907) Don't provide $name (and perhaps others) in EPP scope
Title: Message Title Henrik Lindberg commented on PUP-6907 Re: Don't provide $name (and perhaps others) in EPP scope Unfortunately, I think that it has to be a "tricky gotcha", since there are cases where you want to use the meta variables in your template. The "gotcha" here is simply that you have to know that there are meta parameters and what their names are, and in this case you also have to know that a node is a resource (just like everything else) and that it has a wonky mangled name when it defined based on a regexp. There are other tickets about getting rid of the node _expression_, or the idea that node should be represented differently (not a resource). Don't think there will be action on those for quite some time. I am going to close this ticket as a won't do. 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-6950) scope.function_getparam does not work in ERB templates (future parser)
Title: Message Title Henrik Lindberg commented on PUP-6950 Re: scope.function_getparam does not work in ERB templates (future parser) That approach is ok as long as they refer to the variables of classes in that module. Referring to the attributes of resources that it creates means you are open to issues caused by the order of evaluation. What I think you should do if you want to do as little as possible is to simply look up qualified variables in your ERB. In your example, when you are evaluating the line: $server = Servers::Information::Server[$server_name] The resource 'Servers::Information::Server['foo']' has not yet been evaluated. It will not be evaluated until the class foo has finished its work (and those that included it). Read more here: http://puppet-on-the-edge.blogspot.com.mt/2014/04/getting-your-puppet-ducks-in-row.html In 4.x you have many other options for managing your data that are better. 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
Jira (PUP-6950) scope.function_getparam does not work in ERB templates (future parser)
Title: Message Title
Rowan Ruseler commented on PUP-6950
Re: scope.function_getparam does not work in ERB templates (future parser)
Henrik Lindberg, thanks for the reply.
How it works with parser future disabled is that it takes the specific information from another module where I've information stored. Multiple modules cherry pick from this module for the information they need. It makes it easy to manage the server overview of database ips, fingerprints, keys, etc.
It is kinda like this: init.pp
class foo {
include servers::information
$server_name = "${server_id}"
$server= Servers::Information::Server[$server_name]
}
servers::information,
class servers::information {
define server(
