Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?

2020-08-25 Thread Michael Krause (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Krause updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10642  
 
 
  Uppercase Default value in conditional documentation a typo?   
 

  
 
 
 
 

 
Change By: 
 Michael Krause  
 

  
 
 
 
 

 
 *Puppet Version: 6.17*  {{Starting with 6.x it seems the [documentation for case conditionals|https://puppet.com/docs/puppet/6.17/lang_conditional.html]}} shows an uppercase `Default` as catch-call value. Since this doesn't work and would also be inconsistent to the selector statement I'm carefully assuming it's a (grave) typo?{{This test seems to confirm:}}  {code:java}  class test {  case $facts['os']['name'] {Default:  { notify {'uppercase default':} }  }  case $facts['os']['name'] {default:  { notify {'lowercase default':} }  }}include test{code}   {{And the log:}}  { { noformat} root@host :~# puppet apply test.pp }}{{ {{   Notice: Compiled catalog for host in environment production in 0.02 seconds   {{ {{ Notice: lowercase default   {{ {{ Notice: /Stage[main]/Test/Notify[lowercase default]/message: defined 'message' as 'lowercase default'   {{ {{ Notice: Applied catalog in 0.06 seconds {noformat } }}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

 

Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?

2020-08-25 Thread Michael Krause (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Krause updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10642  
 
 
  Uppercase Default value in conditional documentation a typo?   
 

  
 
 
 
 

 
Change By: 
 Michael Krause  
 

  
 
 
 
 

 
 *Puppet Version: 6.17* **  ** {{Starting with 6.x it seems the [documentation for case conditionals }}{{ |https://puppet.com/docs/puppet/6.17/lang_conditional.html]}} {{  shows an uppercase `Default` as catch-call value. Since this doesn't work and would also be inconsistent to the selector statement I'm carefully assuming it's a (grave) typo? }} {{This test seems to confirm:}} {{class test {}}{{    case $facts['os']['name'] {}}  {{    Default: \{ notify {'uppercase default':} }}}  {{    }}}  {{    case $facts['os']['name'] {}}  {{    default: \{ notify {'lowercase default':} }}} {{   }}}{{}}}{{include test}} {{ And the log:}}   {{root@host :~# puppet apply test.pp }}{{  {{ Notice: Compiled catalog for host in environment production in 0.02 seconds}} }} {{  {{ Notice: lowercase default}} }} {{  {{ Notice: /Stage[main]/Test/Notify[lowercase default]/message: defined 'message' as 'lowercase default'}} }} {{  {{ Notice: Applied catalog in 0.06 seconds}} }}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

 

Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?

2020-08-25 Thread Michael Krause (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Krause created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10642  
 
 
  Uppercase Default value in conditional documentation a typo?   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.y  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Docs  
 
 
Created: 
 2020/08/25 12:50 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Krause  
 

  
 
 
 
 

 
 Puppet Version: 6.17 ** ** Starting with 6.x it seems the documentation for case conditionals}} shows an uppercase `Default` as catch-call value. Since this doesn't work and would also be inconsistent to the selector statement I'm carefully assuming it's a (grave) typo?}} This test seems to confirm: class test {   case $facts['os']['name'] { {{    Default: { notify  {'uppercase default':}  }}} {{  }}}   case $facts['os']['name'] { {{    default: { notify  {'lowercase default':}  }}} {{  }}} } include test   And the log:   {{root@host :~# puppet apply test.pp }} Notice: Compiled catalog for host in environment production in 0.02 seconds Notice: lowercase default Notice: /Stage[main]/Test/Notify[lowercase default]/message: defined 'message' as 'lowercase default' Notice: Applied catalog in 0.06 seconds  
 

  
 
 
 
 

 
 
 

 
 
  

Jira (PUP-9502) codesigning puppet executables on macOS 10.14

2019-03-20 Thread Michael Krause (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Krause commented on  PUP-9502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: codesigning puppet executables on macOS 10.14   
 

  
 
 
 
 

 
 Seems to me that a core resource provider is broken with all puppet versions on macOS 10.14. Why is this not being escalated higher? Am I missing something here. Isn't that a pretty big deal?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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-9502) codesigning puppet executables on macOS 10.14

2019-03-19 Thread Michael Krause (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Krause updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9502  
 
 
  codesigning puppet executables on macOS 10.14   
 

  
 
 
 
 

 
Change By: 
 Michael Krause  
 
 
Affects Version/s: 
 PUP 6.3.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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-8330) macOS agents fails to retrieve password hash

2018-01-08 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause commented on  PUP-8330 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: macOS agents fails to retrieve password hash  
 
 
 
 
 
 
 
 
 
 
This may be related to https://www.exploit-db.com/exploits/43248/ as the affected user resource is root. 
I can workaround this problem by manually setting a new password with passwd. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-8330) macOS agents fails to retrieve password hash

2018-01-08 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8330 
 
 
 
  macOS agents fails to retrieve password hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Krause 
 
 
 
 
 
 
 
 
 
 *Puppet Version: 5.3.3**Puppet Server Version: 5.1.4**OS Name/Version: macOS 10.13.2*puppet user provider fails with every puppet run or with puppet resource*Desired Behavior:*No error or error handling.*Actual Behavior:*Crash.*Example:*{ { code} # puppet resource user admin --trace --debug[..]Debug: Executing: '/usr/bin/dscl -plist . readall /Groups'Debug: Converting binary plist to hashDebug: Converting binary plist to hashDebug: Converting binary plist to hashDebug: Converting binary plist to hashDebug: Converting binary plist to hashError: Could not run: undefined method `unpack' for nil:NilClass/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/directoryservice.rb:210:in `get_salted_sha512_pbkdf2'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/directoryservice.rb:149:in `generate_attribute_hash'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/directoryservice.rb:87:in `block in instances'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/directoryservice.rb:86:in `collect'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/user/directoryservice.rb:86:in `instances'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1164:in `block in instances'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1163:in `collect'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type.rb:1163:in `instances'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/resource/ral.rb:14:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:195:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/resource.rb:216:in `find_or_save_resources'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/resource.rb:142:in `block in main'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:263:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/resource.rb:137:in `main'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:366:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:666:in `exit_on_fail'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'/opt/puppetlabs/puppet/bin/puppet:5:in `' {code } }  
 
 
 
 
 
 
 
 
 
 
 
 

 
 

Jira (PUP-8330) macOS agents fails to retrieve password hash

2018-01-08 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8330 
 
 
 
  macOS agents fails to retrieve password hash  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 5.3.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2018/01/08 7:36 AM 
 
 
 

Environment:
 
 
macOS 10.13.2 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Krause 
 
 
 
 
 
 
 
 
 
 
Puppet Version: 5.3.3 Puppet Server Version: 5.1.4 OS Name/Version: macOS 10.13.2 
puppet user provider fails with every puppet run or with puppet resource 
Desired Behavior: 
No error or error handling. 
Actual Behavior: 
Crash. 
Example: 
{{ 
 

puppet resource user admin --trace --debug [..] Debug: Executing: '/usr/bin/dscl -plist . readall /Groups' Debug: Converting binary plist to hash Debug: Converting binary plist to hash Debug: Converting binary plist to hash Debug: Converting binary plist to hash Debug: Converting binary plist to hash Error: Could not run: undefined method `unpack' for nil:NilClass 

Jira (PUP-1744) User creation fails on OS X 10.9 if user is added to more than one group

2016-09-28 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause commented on  PUP-1744 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User creation fails on OS X 10.9 if user is added to more than one group  
 
 
 
 
 
 
 
 
 
 
The default launchd file recommended with puppet 3.8.x is missing LC_ALL/LANG environments: https://docs.puppet.com/puppet/3.8/reference/install_osx.html#create-a-launchd-service-for-puppet-agent . Maybe that's on purpose, maybe not. 
If I run the puppet agent 3.8 with LC_ALL/LANG set to C this issue still persits. We worked around that by setting the EnvironmentVariables key in the launchd plist directly to en_US.UTF-8. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6161) puppet failes during OSX RTC wakups

2016-04-12 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6161 
 
 
 
  puppet failes during OSX RTC wakups  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.6 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2016/04/12 8:40 AM 
 
 
 

Environment:
 
 
OS: MacOS 10.9 to 10.11 
 
 
 

Labels:
 

 osx client bug 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Krause 
 
 
 
 
 
 
 
 
 
 
There are several issues with the puppet service generating error reports when it is being run during the very short uptime cycle when some of our Macs wake up from sleep to re-register their services with ARP Proxy devices on the network [ Wake reason: RTC (Alarm) ]. 
Example Log: https://gist.github.com/octomike/be9b76d0dc164c41c84bd7fffa97e916 

Jira (PUP-1744) User creation fails on OS X 10.9 if user is added to more than one group

2015-08-18 Thread Michael Krause (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause commented on  PUP-1744 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: User creation fails on OS X 10.9 if user is added to more than one group  
 
 
 
 
 
 
 
 
 
 
We are seeing a similar issue with puppet 3.8.2 on OSX 10.10 : 
Here is the trace: 
 
 
 
 
 
 
Debug: Executing '/usr/bin/dscl -plist . readall /Users' 
 
 
 
 
Error: Could not prefetch user provider 'directoryservice': invalid byte sequence in US-ASCII 
 
 
 
 
/Library/Ruby/Site/facter/util/plist/parser.rb:90:in `scan' 
 
 
 
 
/Library/Ruby/Site/facter/util/plist/parser.rb:90:in `parse' 
 
 
 
 
/Library/Ruby/Site/facter/util/plist/parser.rb:28:in `parse_xml' 
 
 
 
 
/Library/Ruby/Site/puppet/provider/user/directoryservice.rb:94:in `get_all_users' 
 
 
 
 
/Library/Ruby/Site/puppet/provider/user/directoryservice.rb:86:in `instances' 
 
 
 
 
/Library/Ruby/Site/puppet/provider/user/directoryservice.rb:73:in `prefetch' 
 
 
 
 
/Library/Ruby/Site/puppet/transaction.rb:307:in `prefetch'