Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Nick Howes commented on PUP-1916 Re: puppet cert clean cannot remove signing requests `puppet ca` has recently been deprecated, so that option is going away and soon there'll be no way to do this without manually managing the files. 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-6529) User project on Solaris is never set
Title: Message Title Nick Howes commented on PUP-6529 Re: User project on Solaris is never set For info I set up this test case with a bare bones Vagrantfile and the box at http://www.benden.us/vagrant/solaris-11.2.box 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-6529) User project on Solaris is never set
Title: Message Title Nick Howes created an issue Puppet / PUP-6529 User project on Solaris is never set Issue Type: Bug Affects Versions: PUP 4.5.2, PUP 3.8.7 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/07/21 7:16 AM Priority: Normal Reporter: Nick Howes When setting the project attribute on a user type in Solaris 11.2 or 11.3, the incorrect option (-p X) is used in useradd and usermod commands. It should be using -K project=X to set it as a user attribute. Once this is done manually, reading the project value back out works fine. It's just writing that is wrong. We use Puppet 3.6.2 but have also tested in 3.8.7 and 4.5.3. root@solaris:/tmp# puppet resource user vagrant project=group.staff
Jira (HI-487) Strict %{hiera()} interpolation
Title: Message Title
Nick Howes commented on HI-487
Re: Strict %{hiera()} interpolation
If that's feasible, that would be a great alternative to what I suggested.
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 (HI-487) Strict %{hiera()} interpolation
Title: Message Title
Nick Howes created an issue
Hiera / HI-487
Strict %{hiera()} interpolation
Issue Type:
New Feature
Affects Versions:
HI 2.0.0
Assignee:
Unassigned
Created:
2015/12/17 3:33 AM
Priority:
Normal
Reporter:
Nick Howes
The default behaviour of the hiera() function in Puppet is to fail when a key is missing unless a default value is provided, so it is jarring to find that the equivalent interpolation function returns an empty string instead.
I know it would break people's setups to change how this works by default but would it be possible to add an option to make interpolation stricter, so that we can catch typos? In situations where we want a specific lookup to fall back to an empty string, we can simply set it to that at the top of our hierarchy.
Add Comment
Jira (FACT-1010) Uptime inaccurate on Solaris zones
Title: Message Title Nick Howes commented on FACT-1010 Re: Uptime inaccurate on Solaris zones I think you need to be on Solaris 11 to see the effect I describe, which calculates the uptime as many years (since it receives the uptime in seconds from the OS and treats that as a UNIX timestamp of seconds since 1970). The solution of using the uptime command is the same either way, so you shouldn't need to do anything extra for 11, but it would be good to include Solaris 11 in the acceptance test. 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-4754) Solaris crontabs apparently do not support environment lines
Title: Message Title Nick Howes commented on PUP-4754 Re: Solaris crontabs apparently do not support environment lines OP here root@solaris:~# /usr/ruby/1.9/bin/puppet --version 4.1.0 root@solaris:~# /usr/ruby/1.9/bin/puppet resource cron example command=echo hello environment=PATH=/bin Warning: Facter: ldapname is deprecated and will be removed in a future version Notice: /Cron[example]/command: command changed '/bin/echo hello' to 'echo hello' Notice: /Cron[example]/environment: defined 'environment' as 'PATH=/bin' Error: /Cron[example]: Could not evaluate: Could not write crontab for root: Execution of 'crontab /tmp/puppet_suntab20150615-1500-1nj9qub' returned 1: PATH=/bin crontab: error on previous line; unexpected character found in line. crontab: errors detected in input, no crontab file generated.
Jira (PUP-4754) Solaris crontabs apparently do not support environment lines
Title: Message Title Nick Howes commented on PUP-4754 Re: Solaris crontabs apparently do not support environment lines Would be better to prepend the environment variables to the command Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4754) Solaris crontabs apparently do not support environment lines
Title: Message Title Nick Howes updated an issue Puppet / PUP-4754 Solaris crontabs apparently do not support environment lines Change By: Nick Howes Affects Version/s: PUP4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4406) Corrupt /etc/shadow entry when password hash contains newline
Title: Message Title Nick Howes created an issue Puppet / PUP-4406 Corrupt /etc/shadow entry when password hash contains newline Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Unassigned Created: 2015/04/14 1:18 AM Environment: Solaris 11.2 Priority: Normal Reporter: Nick Howes I accidentally used a password hash with a newline at the end (which I didn't notice because it was encased in an eyaml encrypted value). The user_role_add user provider for Solaris carries on and edits /etc/shadow (code) in a way that keeps adding an extra days since 1970 value on every run. specialops:bqaTovDgSOMEHASHVALUE/:16538:16538:16538:16538:16538:16538:16538::
Jira (PUP-1457) fail should be usable in a selector
Title: Message Title
Nick Howes updated an issue
Puppet / PUP-1457
fail should be usable in a selector
Change By:
Nick Howes
Itwouldbeniceifthisworkedbetter: pre {code} notify{test:message=$environment?{production=http://blah/blah/prod,development=http://blah/blah/dev,default=fail(environment'${environment}'isnotyetsupported),}} /pre {code} Desiredresultwhenthedefaultbranchoftheselectoristaken:Failuretocompilethecatalog,withtheerrormessageenvironment'foo'isnotsupported.Actualresultwhenthedefaultbranchoftheselectoristaken:Failuretocompilethecatalog,withtheerrormessageFunction'fail'doesnotreturnavalue.Usecase:Downloadinganenvironment-dependentURLontheclient.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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-14) Allow access to structured data
Title: Message Title Nick Howes commented on HI-14 Re: Allow access to structured data Seems too much of an edge case to implement in Hiera. If you want to keep the same data structure, I'd recommend replacing dots with underscores using regsubst, so your key name becomes: services::elasticsearch-0_90_11::maintainer Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4086) File and line numbers often missing from errors
Title: Message Title Nick Howes commented on PUP-4086 Re: File and line numbers often missing from errors Thanks for looking into this - your explanation makes sense. I agree that ArgumentError seems more appropriate than ParseError, and does give line numbers. Also agree that the best place for a fix is in the module functions themselves, rather than adding cruft to the evaluator. I might raise a PR on stdlib to consider the idea of using ArgumentError instead. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-14) Allow access to structured data
Title: Message Title Nick Howes commented on HI-14 Re: Allow access to structured data Jon Shanks, what you're describing is HI-294 so you should track that issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3619) Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Title: Message Title
Nick Howes commented on PUP-3619
Re: Hiera: future+strict_variables fails with uncaught throw :undefined_variable
I get this on 3.7.3. For me it works if the value is found in the first item in the hierarchy, otherwise it throws this exception before it gets any further. So for me it's more than just a cryptic message. Without strict_variables, hiera can traverse its hierarchy.
/etc/puppet/hiera.yaml
---
:hierarchy:
- nodes/%{::hostname}
- common
A call to hiera('puppet::version') fails with the above exception if puppet::version is set in common.yaml, but works if it's set in nodes/thehostname.yaml
Add Comment
Jira (PUP-3619) Hiera: future+strict_variables fails with uncaught throw :undefined_variable
Title: Message Title Nick Howes commented on PUP-3619 Re: Hiera: future+strict_variables fails with uncaught throw :undefined_variable Ah, found out what it is - it's not that it doesn't go past the first item in the hierarchy, it's that the second item in my hierarchy used interpolated facts that aren't being set. So it is genuinely complaining about missing variables, which is fair enough. So my case is nothing new from what Chris has already mentioned. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
