Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Halim Wijaya Priority: Normal Major 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
CS Priority:
Needs Priority
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png|thumbnail!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png|thumbnail!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png |thumbnail !Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya commented on PUP-7326 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Thanks Josh, created new issue https://tickets.puppetlabs.com/browse/PUP-9604 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Halim Wijaya Attachment: image-2019-04-05-10-41-13-985.png 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java} puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java} puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below! Screen Shot image- 2019-04- 03 at 11 05-10-41-13-985 . 44.28 AM. png!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
* Puppet Version: * This is spin-off ticket of PUP-7326. *Puppet Server Version:* * OS Name/Version Steps to reproduce :* # Setup Active Directory with Domain Functional level 2016 Describe your issue # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in as much detail as possible… Active Directory Describe steps # Add testadmin1 user to reproduce… local administrators group in Win2012R2 # Delete testadmin1 user in AD *Desired Behavior # Run{code : * java} *Actual Behavior puppet apply -e "group {'Administrators' : * members => ['Administrator'], auth_membership => true }"{code} Please take Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a moment Win2016 machine and attach any relevant log output and/or manifests connect to AD # Create a test user (e . This will help us immensely when troubleshooting the issue q . testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 Examples: # Delete testadmin1 user in AD # Run puppet agent with --test --trace --debug {code:java} Relevant sections of puppet apply -e "group { 'Administrators': members => ['Administrator'], auth_membership => true } { /var/log/puppetlabs/puppetserver/puppetserver.log code } } or any applicable logs from the same directory Puppet apply returns error below!Screen Shot 2019-04-03 at 11 . 44.28 AM.png! For more detailed information turn up Note the server logs by upping error occurs only on Windows client machine with condition its OS version is different with the log AD Domain Functional level in the server's logback . xmlRelevant sections of configurations files (puppet E . conf, hiera q . conf, Server's conf Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2 . d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Add Comment
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Halim Wijaya Summary: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression ) 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression
Title: Message Title Halim Wijaya created an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression Issue Type: Bug Assignee: Unassigned Created: 2019/04/04 7:29 PM Priority: Normal Reporter: Halim Wijaya Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Comment: [^debugtraceoutput.txt] 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Attachment: debugtraceoutput.txt 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya commented on PUP-7326 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts debugtraceoutput.txt 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Attachment: Screen Shot 2019-04-03 at 11.45.12 AM.png 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya commented on PUP-7326 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts This issue re-occurs in Windows 2016 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Attachment: Screen Shot 2019-04-03 at 11.44.28 AM.png 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-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Halim Wijaya commented on PUP-9324 Re: Puppet agent run output to differentiate between corrective and intentional change Thanks Melissa Stone for the quick turnaround on this. There is a question from customer if there is a plan to backport this to current LTS? 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-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Halim Wijaya assigned an issue to Halim Wijaya Puppet / PUP-5233 puppet inspect is using wrong path for catalog data Change By: Halim Wijaya Assignee: Halim Wijaya 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 (BOLT-614) I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1
Title: Message Title Halim Wijaya commented on BOLT-614 Re: I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1 The updated documentation https://puppet.com/docs/bolt/1.x/writing_tasks.html#tasks-with-multiple-implementations doesn't work with `puppet task` command. Orchestrator looks for executable file that is the same name with the metadata file and will complain the task doesn't exist if it can't find one. # puppet task run test::listout --nodes pe-201815-master.puppetdebug.vlan Starting job ... Failed to submit job: puppetlabs.orchestrator/unknown-task: The test::listout task does not exist in environment production # ls -ahl total 12K drwxr-xr-x. 2 pe-puppet pe-puppet 74 Jan 16 22:56 . drwxr-xr-x. 3 pe-puppet pe-puppet 18 Jan 16 22:37 .. -rw-r--r--. 1 pe-puppet pe-puppet 251 Jan 16 22:56 listout.json -rw-r--r--. 1 pe-puppet pe-puppet 20 Jan 16 22:37 listout_linux.sh -rw-r--r--. 1 pe-puppet pe-puppet 14 Jan 16 22:38 listout_windows.ps1
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9324 Puppet agent run output to differentiate between corrective and intentional change Change By: Halim Wijaya Comment: A comment with security level 'Developers' was removed. 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 (BOLT-990) Allow Tasks page on Console to display list of tasks from non-production environment
Title: Message Title Halim Wijaya created an issue Puppet Task Runner / BOLT-990 Allow Tasks page on Console to display list of tasks from non-production environment Issue Type: Improvement Assignee: Unassigned Created: 2018/11/21 9:13 PM Priority: Normal Reporter: Halim Wijaya Currently, Console Tasks page display only list of Tasks that are in Production environment. The only workaround to run non-production tasks is via Command Line. There should be an option to run "non-production" environment Tasks on PE Console. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-853) Puppet Task is not parsing Powershell parameter default value
Title: Message Title Halim Wijaya updated an issue Puppet Task Runner / BOLT-853 Puppet Task is not parsing Powershell parameter default value Change By: Halim Wijaya Issue Type: Task Bug 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 (BOLT-853) Puppet Task is not parsing Powershell parameter default value
Title: Message Title
Halim Wijaya updated an issue
Puppet Task Runner / BOLT-853
Puppet Task is not parsing Powershell parameter default value
Change By:
Halim Wijaya
*Powershell script sample* {code:java} param( [Parameter(Mandatory = $False)] [String] $firstArg = 'somevaluehere' )Write-Host $firstArg{code} *Expected behaviour:*Task run should print out _somevaluehere_ *Actual behaviour:*Task run returns empty String*Current workaround* {code:java} param( [Parameter(Mandatory = $False)] [String] $firstArg = 'somevaluehere' ) if (!$firstArg) { $firstArg = "somevaluehere"} Write-Host $firstArg {code} Note that the issue appears to impact only Powershell 2.0, upgrading to Powershell 3.0 seems to fix the issue it .
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
Jira (BOLT-853) Puppet Task is not parsing Powershell parameter default value
Title: Message Title Halim Wijaya created an issue Puppet Task Runner / BOLT-853 Puppet Task is not parsing Powershell parameter default value Issue Type: Task Assignee: Unassigned Created: 2018/09/18 5:39 PM Priority: Normal Reporter: Halim Wijaya Powershell script sample param( [Parameter(Mandatory = $False)] [String] $firstArg = 'somevaluehere' ) Write-Host $firstArg Expected behaviour: Task run should print out somevaluehere Actual behaviour: Task run returns empty String Current workaround
Jira (PUP-9101) PE agent installation fails on newly released Solaris 11.4
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9101
PE agent installation fails on newly released Solaris 11.4
Change By:
Halim Wijaya
*Puppet Version: 5.5.4* *Puppet Server Version: 2018.1.2* *OS Name/Version: Solaris 11.4*Installation of the puppet agent using the curl | bash method fails on Solaris 11.4, which was released last week. {code:java} curl -k [ https:// \ {Master FQDN}:8140/packages/current/install.bash |https://puppetmaster.unix.anz:8140/packages/current/install.bash] | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 25740 100 25740 0 0 447k 0 - - : -- :-- -- : -- :-- -- : -- :- - 523k This method of agent installation is not supported for solaris-11.4-sparc in Puppet Enterprise v2018.1.2 {code} This seems to happen because in Solaris 11.4, is now an *_ /etc/os- release release_* file. An example file follows: {code:java} # cat /etc/os-release NAME="Oracle Solaris" PRETTY_NAME="Oracle Solaris 11.4" CPE_NAME="cpe:/o:oracle:solaris:11:4" ID=solaris VERSION=11.4 VERSION_ID=11.4 BUILD_ID=11.4.0.0.1.3.0 HOME_URL=" [ https://www.oracle.com/solaris/ ] " SUPPORT_URL=" [ https://support.oracle.com/ ] " {code} The presence of this file causes install.bash to resolve the platform tag to solaris-11.4-sparc, where on previous Solaris releases it would be solaris-11-sparc. This in turn causes the t_supported_platform_regex to not match.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9101) PE agent installation fails on newly released Solaris 11.4
Title: Message Title
Halim Wijaya created an issue
Puppet / PUP-9101
PE agent installation fails on newly released Solaris 11.4
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/09/04 6:54 PM
Priority:
Critical
Reporter:
Halim Wijaya
Puppet Version: 5.5.4 Puppet Server Version: 2018.1.2 OS Name/Version: Solaris 11.4 Installation of the puppet agent using the curl | bash method fails on Solaris 11.4, which was released last week. curl -k https://{Master FQDN}:8140/packages/current/install.bash | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 25740 100 25740 0 0 447k 0 -::- -::- -::- 523k This method of agent installation is not supported for solaris-11.4-sparc in Puppet Enterprise v2018.1.2 This seems to happen because in Solaris 11.4, is now an /etc/os-release file. An example file follows:
cat /etc/os-release NAME="Oracle Solaris" PRETTY_NAME="Oracle Solaris 11.4" CPE_NAME="cpe:/o:oracle:solaris:11:4" ID=solaris VERSION=11.4 VERSION_ID=11.4 BUILD_ID=11.4.0.0.1.3.0 HOME_URL="https://www.oracle.com/solaris/" SUPPORT_URL="https://support.oracle.com/"
The presence of this file causes install.bash to resolve the platform tag to solaris-11.4-sparc, where on previous Solaris releases it would be solaris-11-sparc. This in turn causes the t_supported_platform_regex to not match.
Jira (PUP-7466) Error while evaluating a Virtual Query
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7466 Error while evaluating a Virtual Query Change By: Halim Wijaya CS Priority: Needs Priority 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-8903) Allow "puppet agent --disable" via Console > Run Puppet
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-8903 Allow "puppet agent --disable" via Console > Run Puppet Change By: Halim Wijaya Issue Type: Improvement New Feature 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-8903) Allow "puppet agent --disable" via Console > Run Puppet
Title: Message Title Halim Wijaya created an issue Puppet / PUP-8903 Allow "puppet agent --disable" via Console > Run Puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/06/04 1:38 AM Priority: Normal Reporter: Halim Wijaya PE was shipped with MCollective that can disable puppet agent with command mco puppet disable Now with MCollective being deprecated and eventually replaced by Task, there is no "built-in" option to disable puppet agents. Would be great if we can have that option via Console UI. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX
Title: Message Title Halim Wijaya updated an issue Facter / FACT-1597 "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX Change By: Halim Wijaya Priority: Normal Major Running Puppet Enterprise 2017.1.1Previous facter: 3.5.0 (commit 872c5707799c1c30925b632f20eab763ec03b5a4)New facter: 3.6.2 (commit 36e4f036cfab9e283f6b47bd5e3890a4de54c5ff)After upgrading AIX Client with puppet-agent-1.9.3-1.aix7.1.ppc.rpm, new version of facter returns warning below.# facter 2017-03-28 13:10:48.912233 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.912822 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913030 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913236 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913441 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.914954 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.915236 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.915448 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. Add Comment
Jira (PUP-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-1913 Puppet user resource should respect the forcelocal option Change By: Halim Wijaya CS Priority: Needs Priority 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-8295) Group resource cannot resolve virtual account "NT Service\Servicename"
Title: Message Title Halim Wijaya created an issue Puppet / PUP-8295 Group resource cannot resolve virtual account "NT Service\Servicename" Issue Type: Bug Assignee: Unassigned Attachments: image.png Created: 2017/12/26 6:37 PM Environment: Windows Server 2012 R2 that has services with Log On As Virtual accounts (NT Service\servicename). Priority: Critical Reporter: Halim Wijaya Note: the issue does not occur if the service has run at least once within machine up time, regardless whether it is stopped or disabled after that. Steps to reproduce: Disable service that run as NT Service\servicename (e.q. NT Service\SqlIaaSExtension) Reboot machine Create new group with NT Service\SqlIaaSExtension as member
Jira (PUP-8231) Group resource - unable to add new member if there is existing IIS AppPool\user
Title: Message Title
Halim Wijaya created an issue
Puppet / PUP-8231
Group resource - unable to add new member if there is existing IIS AppPool\user
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/12/06 5:38 PM
Environment:
Reproduce in Win 2012 R2, but should affect most windows platform
Priority:
Major
Reporter:
Halim Wijaya
Steps to reproduce
1. Create Group "TestGroup" with "IIS AppPool\DefaultAppPool" as a member
group { 'TestGroup':
name=> 'TestGroup',
ensure => present,
