Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg commented on PUP-5063 Re: Puppet 4 --profile is not complete compared to 3 Thanks R.I.Pienaar Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg commented on PUP-5063 Re: Puppet 4 --profile is not complete compared to 3 Merged to stable: 86343ce Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5063
Puppet 4 --profile is not complete compared to 3
Change By:
Henrik Lindberg
Release Notes Summary:
A regression in the functionality of {{--profile}} has been fixed. This regression caused functions that were transitioned to the 4.x function API to not be included in the profiling information produced by {{--profile}}.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4125) Add migration check for upper case bare word evaluation
Title: Message Title Henrik Lindberg commented on PUP-4125 Re: Add migration check for upper case bare word evaluation Brian Morris The Catalog Preview module helps with finding changes like this one. It is the tool that processes information generated by the "migration checks" that were implemented in Puppet 3.x (this ticket is for one of those checks). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5063 Puppet 4 --profile is not complete compared to 3 Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5592 hiera lookup regression in resource like class definitions with undef parameter Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5590) No error on duplicate parameters on classes and resources
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5590 No error on duplicate parameters on classes and resources Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title Henrik Lindberg commented on PUP-5592 Re: hiera lookup regression in resource like class definitions with undef parameter Merged to stable at: 834556f Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5597) Illegal comma separated argument list
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-5597 Illegal comma separated argument list Issue Type: Bug Assignee: Unassigned Components: Language Created: 2015/12/11 2:10 AM Priority: Normal Reporter: Daniele Sluijters I made the following oopsy in a manifest $var = something, It resulted in the following error message: Error: illegal comma separated argument list in /etc/puppetlabs/code/environments/production/modules/jenkins/manifests/server.pp on node
Jira (PUP-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding Issue Type: Bug Assignee: Unassigned Created: 2015/12/11 4:10 AM Priority: Normal Reporter: Thomas Hallgren If a hiera databinding contains an entry like this: lookup_options: some::hash: merge: deep then while it's impossible to find the key lookup_options it is possible to find the subentry using the key lookup_options.some::hash. This is wrong. Neither the lookup_options hash nor any of its sub-keys should be possible to find using a normal lookup.
Jira (PUP-5437) Explain lookup of lookup_options
Title: Message Title Thomas Hallgren commented on PUP-5437 Re: Explain lookup of lookup_options Actually, a lookup of lookup_options should always fail. It's not considered a real value so something is amiss with the detection of that when a dotted key starting with lookup_options is used. I created PUP-5598 to track that. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding Change By: Thomas Hallgren Assignee: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Easy to fix while I have everything fresh in memory. Story Points: 1 Sprint: Language 2015-12-16 Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5597) Illegal comma separated argument list
Title: Message Title Thomas Hallgren commented on PUP-5597 Re: Illegal comma separated argument list This problem was fixed in Puppet 4.3.0 in PUP-5026 . What version are you using? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5547) Environment is evicted many times during compile
Title: Message Title Thomas Hallgren commented on PUP-5547 Re: Environment is evicted many times during compile Yes and no. I expected all evictions caused by lookup to vanish but I didn't expect there to be others. I wonder where they stem from. Can I borrow your site.pp? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5597) Illegal comma separated argument list
Title: Message Title Daniele Sluijters commented on PUP-5597 Re: Illegal comma separated argument list Ah, sorry, this is on 4.2. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-135) Improve warning message for invalid UTF-8 byte sequences
Title: Message Title Olivier Hanesse commented on PDB-135 Re: Improve warning message for invalid UTF-8 byte sequences Hello Everyone, I think, there is a regression with PR #1640. Indeed, using puppetdb-termini 3.2 (which includes this PR), puppetserver is "hanging" when sending catalog to PuppetDB. Catalog Compilation is working. My catalog contains a binary file (a kerberos keytab in fact), that is the cause of the hanging. If I use the "char_encoding.rb" file from version 3.1, sending catalog to puppetdb is working again. Do you want me to open a new ticket ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-135) Improve warning message for invalid UTF-8 byte sequences
Title: Message Title Kenneth Barber commented on PDB-135 Re: Improve warning message for invalid UTF-8 byte sequences Olivier Hanesse if you can open a new bug on the problematic version, that would be optimal. That way we can focus on the particular problem, this current ticket description and problems it solves are pretty generic. We'll probably want to see the binary file also, so we can replicate it, if thats at all possible, plus any exception thrown in the terminus that you might see. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-486) Remove host specific logic from hiera acceptance setup steps
Title: Message Title Kenn Hussey commented on HI-486 Re: Remove host specific logic from hiera acceptance setup steps Kylo Ginsberg this issue needs to be scheduled into a sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-5599
Add resource type length to validation error output
Issue Type:
Bug
Affects Versions:
PUP 4.3.1
Assignee:
Unassigned
Components:
Language
Created:
2015/12/11 7:25 AM
Priority:
Normal
Reporter:
Julien Pivotto
When the compilation fails because of the lenght of a String not being correct, it would be great to see that in the output.
PP file:
with ('Fooo',) | String[6,10] $foo | {}
Jira (PUP-5599) Add resource type length to validation error output
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output Change By: Julien Pivotto Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Function Calls Change By: Julien Pivotto Summary: Add resource type length to validation error output of Function Calls Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2248) (maint) Upgrade to ActiveMQ 5.13.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2248 (maint) Upgrade to ActiveMQ 5.13.0 Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Function Calls Change By: Julien Pivotto Affects Version/s: PUP 4.3.1 Affects Version/s: PUP 4.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of Function Calls
Title: Message Title Julien Pivotto commented on PUP-5599 Re: Add resource type length to validation error output of Function Calls I was running an 4.2 version of puppet, this was fixed in 4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5599) Add resource type length to validation error output of
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5599 Add resource type length to validation error output of Change By: Julien Pivotto Summary: Add resource type length to validation error output of Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2255) Make services "notable-pdb-event?" configurable and use that in extensions tests
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2255 Make services "notable-pdb-event?" configurable and use that in extensions tests Issue Type: Improvement Assignee: Rob Browning Created: 2015/12/11 8:23 AM Priority: Normal Reporter: Rob Browning Originally notable-pdb-event? wasn't set up to be customized, but now we want that (i.e. PDB-2215 ), so let's make it configurable. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5547) Environment is evicted many times during compile
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5547 Environment is evicted many times during compile Change By: Sean Griffin Attachment: pup-5547-environ-manifest Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5547) Environment is evicted many times during compile
Title: Message Title Sean Griffin commented on PUP-5547 Re: Environment is evicted many times during compile Hi Thomas Hallgren, I have attached a manifest which when run on a newly installed 4.x Puppet, will install the environment, the module (data_module), site.pp and value storage for the lookup command. It takes some modification to make it work with 3.x. For the test, I edited modules/data_modules/init.pp to comment out some or all of the array values on which the lookup function is called. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5598) Subkeys of lookup_options are found when using Hiera data binding
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5598 Subkeys of lookup_options are found when using Hiera data binding Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5597) Illegal comma separated argument list
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5597 Illegal comma separated argument list Change By: Henrik Lindberg Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5502 lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2217) Add multi-part form support to the libcurl wrapper
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2217 Add multi-part form support to the libcurl wrapper Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Josh Cooper updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Josh Cooper Fix Version/s: FACT 3.1.4 Fix Version/s: FACT 3.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps Change By: Josh Cooper Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5583) Remove host specific logic from puppet acceptance setup steps
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5583 Remove host specific logic from puppet acceptance setup steps Change By: Josh Cooper Sprint: QE 2015-12-23 Client Platform Additions Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Chuck Schweizer updated an issue Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: Chuck Schweizer Affects Version/s: PUP 4.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Nicholas Fagerlund commented on PUP-5561 Re: Put accurate information about autoloading in spec for puppet functions They are! I'm going to go ahead and merge. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5572) puppet describe exec does not detail Provider attribute
Title: Message Title Nicholas Fagerlund commented on PUP-5572 Re: puppet describe exec does not detail Provider attribute Gerhardus Geldenhuis https://github.com/puppetlabs/puppetlabs-strings Right now it has rudamentary support for resource types and providers, but it hasn't been expanded and hardened to make sure it works with the core built-in resource types. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Release Notes Summary: Fix a regression in Puppet which would cause generated resources to be retrieved at generation time instead of at evaluation time. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte QA Risk Assessment Reason: Covered by unit test Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte commented on PUP-3149 Re: Removing packages on Suse should use zypper not rpm William Hopper what is the appropriate fix version for this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5592 hiera lookup regression in resource like class definitions with undef parameter Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5063 Puppet 4 --profile is not complete compared to 3 Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title
John Duarte commented on PUP-3149
Re: Removing packages on Suse should use zypper not rpm
Validated on SLES 11 using pre-release version of puppet-agent at SHA 61cb1be containing puppet at SHA d6b75bb
oxmnp50g9z75osz:~ # cat /opt/puppetlabs/puppet/VERSION
1.3.2.97.g61cb1be
oxmnp50g9z75osz:~ # rpm -e emacs
error: Failed dependencies:
emacs = 22.3-4.36.1 is needed by (installed) emacs-nox-22.3-4.36.1.x86_64
oxmnp50g9z75osz:~ # puppet apply -e 'package { "emacs": ensure => absent }'
Notice: Compiled catalog for oxmnp50g9z75osz.delivery.puppetlabs.net in environment production in 0.47 seconds
Notice: /Stage[main]/Main/Package[emacs]/ensure: removed
Notice: Applied catalog in 0.77 seconds
oxmnp50g9z75osz:~ # rpm -e emacs
Jira (PUP-5595) Generated resource state is retrieved prematurely
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title John Duarte updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: John Duarte Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Glenn Matthews updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Glenn Matthews Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2072) Sync efficiency: PE-only reports summary endpoint
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2072 Sync efficiency: PE-only reports summary endpoint Change By: Susan McNerney Scope Change Category: Adopted Scope Change Reason: pulled in from later sprint before staff went out sick. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2243) (MAINT) Use throw+ instead of (throw (ex-info...)) in perform-sync
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2243 (MAINT) Use throw+ instead of (throw (ex-info...)) in perform-sync Change By: Susan McNerney Scope Change Category: Found Scope Change Reason: Discovery made within planned work. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2073) Sync efficiency: use the report summary in sync
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2073 Sync efficiency: use the report summary in sync Change By: Susan McNerney Scope Change Category: Adopted Scope Change Reason: Brought from later sprint, but staff member went out sick. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2159) Caching for faster reports summary query
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2159 Caching for faster reports summary query Change By: Susan McNerney Scope Change Category: Adopted Scope Change Reason: Brought in from later sprint, but key staff member went out sick Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5502 lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Change By: Sean Griffin Attachment: setup-manifest-plus-module Attachment: setup-manifest-no-module Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title
Sean Griffin commented on PUP-5502
Re: lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Tested on centos-6-x86_64. Puppet 4.3.2
Compared the fixed sha (d6b75bbd6016b36651c5013b2e7b692851f9b5bf) with the sha before the fix (5032dc977a1842650cbe5f58670ecab24784342e).
The error message is now more concise and includes the name of the key on which the lookup failed. Both error message contain the name of and the location in the broken yaml file where evaluation failed.
I tried it two ways, (1) with no module defined, invoking 'puppet lookup key_in_hiera' and (2) with a module, data_module, whose init.pp contains a call to lookup("key_in_hiera") and environment/production/site.pp declares the data_module class. Here is what the error message look like:
1: puppet lookup key_in_module Message from before fix:
[root@vd1vgu8266rdkp0 environments]# puppet lookup key_in_hiera
Error: Could not run: Error from DataBinding 'hiera' while looking up 'lookup_options': (/etc/puppetlabs/code/hiera.yaml): found character that cannot start any token while scanning for the next token at line 2 column 5 in (/etc/puppetlabs/code/hiera.yaml): found character that cannot start any token while scanning for the next token at line 2 column 5
Wrapped exception:
(/etc/puppetlabs/code/hiera.yaml): found character that cannot start any token while scanning for the next token at line 2 column 5 in (/etc/puppetlabs/code/hiera.yaml): found character that cannot start any token while scanning for the next token at line 2 column 5
[root@vd1vgu8266rdkp0 environments]#
Message from after fix:
Jira (PUP-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5502 lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Change By: Sean Griffin QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5502 lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Change By: Sean Griffin Release Notes Summary: When the hiera.yaml file is not correct, lookup error messages are improved. The error message now more concise and includes the name of the key, the location of the broken hiera.yaml file and the location in hiera.yaml where the evaluation failed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1763) Puppet run continues despite failed Pluginsync
Title: Message Title Josh Cooper commented on PUP-1763 Re: Puppet run continues despite failed Pluginsync If the master doesn't have at least one module/lib directory, pluginsync will fail (and I think the same is true for facts.d for pluginfactsync) due to PUP-2608. So that needs to be fixed before this ticket can be. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5548) Debian provider fails on Debian 8 systems without systemd present
Title: Message Title Michael Smith commented on PUP-5548 Re: Debian provider fails on Debian 8 systems without systemd present Testing notes: it'd be good to test at least two service configurations, and make sure we can start/stop/restart/query services. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5601) Puppet settings not setup prior to test runs due to PUP-1118 implementation
Title: Message Title Alex Schultz created an issue Puppet / PUP-5601 Puppet settings not setup prior to test runs due to PUP-1118 implementation Issue Type: Bug Affects Versions: PUP 3.8.4, PUP 3.8.3, PUP 3.7.5, PUP 3.8.2, PUP 3.8.1, PUP 3.8.0, PUP 3.7.4, PUP 3.7.3, PUP 3.7.2, PUP 3.7.1, PUP 3.7.0, PUP 3.6.2, PUP 3.6.1, PUP 3.6.0, PUP 3.5.1, PUP 3.5.0 Assignee: Unassigned Created: 2015/12/11 4:19 PM Priority: Normal Reporter: Alex Schultz I believe I have found a regression for https://projects.puppetlabs.com/issues/15529. With the removal of as part of initialize_settings_before_each from the Puppet::Test::TestHelper.initalize as part of https://github.com/puppetlabs/puppet/commit/8781d0da2fe6ad2fef954c8c2da54d573181d561#diff-0f072f04864a42b92c59db020665c212L36, if you attempt to access any internals via PuppetlabsSpec::PuppetInternals.scope before a test is run then rspec will error. The resulting error seems to be a regression for https://projects.puppetlabs.com/issues/15529 where this was added in to the TestHelper in the first place. The resulting error and stack trace is: /Users/aschultz/.rvm/gems/ruby-2.1.5@fuel/gems/puppet-3.8.4/lib/puppet/settings.rb:1348:in `block in convert': Error converting value for param 'modulepath': Error converting value for param 'basemodulepath': Could not find value for $confdir (Puppet::Settings::InterpolationError) from /Users/aschultz/.rvm/gems/ruby-2.1.5@fuel/gems/puppet-3.8.4/lib/puppet/settings.rb:1337:in `gsub' from /Users/aschultz/.rvm/gems/ruby-2.1.5@fuel/gems/puppet-3.8.4/lib/puppet/settings.rb:1337:in `convert' from /Users/aschu
