Jira (PUP-7203) puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name
Title: Message Title Josh Samuelson commented on PUP-7203 Re: puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name Rob Nelson this fixed the issue for me: https://github.com/puppetlabs/puppetlabs_spec_helper/pull/191 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-7203) puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name
Title: Message Title Josh Samuelson commented on PUP-7203 Re: puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name I just ran into this, reverting to puppetlabs_spec_helper 1.2.2 is also a functional workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6463) Second parameter is evaluated first
Title: Message Title
Josh Samuelson created an issue
Puppet / PUP-6463
Second parameter is evaluated first
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/06/30 12:56 PM
Priority:
Normal
Reporter:
Josh Samuelson
I ran into this error trying to include a PE profile class that happened to inherit a class that was already defined in the PE console. This is the minimal repro of the root issue.
Given the following site.pp:
class breaking (
String $first,
String $second = $first,
){}
Jira (PUP-6463) Second parameter is evaluated first
Title: Message Title Josh Samuelson updated an issue Puppet / PUP-6463 Second parameter is evaluated first Change By: Josh Samuelson Affects Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5627) Inconsistent ERB parsing of comments
Title: Message Title Josh Samuelson commented on PUP-5627 Re: Inconsistent ERB parsing of comments It may be different versions of ruby. The reason I bothered filing a bug for this is that only some comments are ignored. As you say '#' means 'rest of line is a comment', but ' %>' is treated as template markup when '%>' isn't. That might just be a side effect of ' %>' eating the newline. If puppet just relays the string to ERB, I'm less concerned and maybe we can even just close this as "Won't Fix", or just make it a documentation ticket. I'm guessing enough people run into this that it would be worth noting in the docs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Josh Samuelson commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Was this tested with CentOS 6.6 and 3.8.1? I just ran into the issue and had to use the symlink workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-4084) Puppet apply very slow with invalid DNS server
Title: Message Title Josh Samuelson created an issue Puppet / PUP-4084 Puppet apply very slow with invalid DNS server Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/03/04 2:42 PM Priority: Normal Reporter: Josh Samuelson I'm attempting to run through some offline testing for our classroom VMs. I set the DNS and the default gateway to an IP in the same subnet that doesn't have anything running on it. This would simulate a VM being set up via DHCP and then being physically disconnected from that network. This might happen if a student was taking a class and wanted to continue exploring puppet using puppet apply on their VM on the airplane ride home. Puppet apply seems to silently wait for a DNS timeout before continuing on with its run. If I remove the nameserver line from /etc/resolv.conf or set it to a valid DNS server IP, puppet apply goes quickly. The behavior is the same if the gateway is set to a valid IP or not, so this issue seems limited to the DNS setting.
