Jira (BOLT-864) Always upload code from bolt when running a task via Orchestrator
Title: Message Title Paul Schaffer updated an issue Puppet Task Runner / BOLT-864 Always upload code from bolt when running a task via Orchestrator Change By: Paul Schaffer 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Paul Schaffer commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run It's been reported that for the 6.0.4 agent, while removing the file locally resolves the issue, running the agent via a task causes the permissions issue to reoccur. 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title
Paul Schaffer commented on PUP-9337
Re: Puppet sets permissions for Puppet files every run
A user was able to reproduce these conditions during an upgrade from 5.3.3 to 5.5.8. Notably, when performing the upgrade they observe permissions shifting to a higher level, then the agent run attempting to lower them back down: With an agent version 5.3.3, prior to upgrade:
C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled
file { 'C:\ProgramData\PuppetLabs\puppet\cache\state\package_inventory_enabled':
...
mode => '0664',
...
}
C:\WINDOWS\system32>puppet resource file C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf
file { 'C:\ProgramData\PuppetLabs\pxp-agent\etc\pxp-agent.conf':
...
mode => '0660',
...
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Paul Schaffer 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title
Paul Schaffer updated an issue
Puppet / PUP-9337
Puppet sets permissions for Puppet files every run
Change By:
Paul Schaffer
*Puppet Version:* 2018.1.5, 2019.0.1*OS Name/Version:* Windows 2012 R2, 2016, 2019File permissions for Puppet files are being set to the same value every run: ``` {code} Resource Event Changed from Changed toFile[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89 Corrective change 0674 664File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105 Corrective change 0670 660 ``` {code} This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions): > {panel} The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.) {panel} However the next agent run shows the value has reverted and needs to be set again. It appears that removing the file often - but not always - resolves the issue.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Paul Schaffer commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run At least one report shows the group with (F) permissions, which would probably explain the '7' value: Owner : BUILTIN\Administrators Group : NT AUTHORITY\SYSTEM BUILTIN\Administrators:(R,W,D,WDAC,WO) NT AUTHORITY\SYSTEM:(F) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Paul Schaffer *Puppet Version:* 2018.1.5, 2019.0.1*OS Name/Version:* Windows 2012 R2, 2016, 2019File permissions for Puppet files are being set to the same value every run:```Resource Event Changed from Changed toFile[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89 Corrective change 0674 664File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105 Corrective change 0670 660```This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions):> The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.)However the next agent run shows the value has reverted and needs to be set again. It appears that removing the file often - but not always - resolves the issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Paul Schaffer created an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Issue Type: Bug Assignee: Unassigned Created: 2018/11/30 10:48 AM Priority: Normal Reporter: Paul Schaffer Puppet Version: 2018.1.5, 2019.0.1 OS Name/Version: Windows 2012 R2, 2016, 2019 File permissions for Puppet files are being set to the same value every run: ``` Resource Event Changed from Changed to File[C:\ProgramData/PuppetLabs/puppet/cache/state/package_inventory_enabled] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/profile/agent.pp Line: 89 Corrective change 0674 664 File[C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf] File: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/pxp_agent.pp Line: 105 Corrective change 0670 660 ``` This seems to target package_inventory_enabled most frequently. Every run the permission is set from 0674 to 0664, which would seem to correspond with documentation requirements (https://puppet.com/docs/puppet/6.0/resources_file_windows.html#how-nix-modes-map-to-windows-permissions): > The group can’t have higher permissions than the owner. Other users can’t have higher permissions than the owner or group. (That is, 0640 and 0755 are supported, but 0460 is not.) However the next agent run shows the value has reverted and needs to be set again. Add Comment
Jira (PDB-3473) PDB query that can return a list of nodes in a given node group
Title: Message Title Paul Schaffer updated an issue PuppetDB / PDB-3473 PDB query that can return a list of nodes in a given node group Change By: Paul Schaffer Create a new endpoint or extend the functionality of a current one so that a user can issue a query about a specific group (either through group name or group ID) and have it return a list of nodes associated with that group (whether statically or dynamically pinned). An example of how this can currently be accomplished via some API and combinatory logic can be found here: https://github.com/abottchen/pe_curl_requests/blob/master/classifier/nodes_by_node_group.rb 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
Jira (PDB-3473) PDB query that can return a list of nodes in a given group
Title: Message Title Paul Schaffer updated an issue PuppetDB / PDB-3473 PDB query that can return a list of nodes in a given group Change By: Paul Schaffer 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-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Paul Schaffer assigned an issue to Henrik Lindberg Puppet / PUP-9040 puppet lookup command returns warning with poor formatting Change By: Paul Schaffer Assignee: Paul Schaffer Henrik Lindberg 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-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Paul Schaffer commented on PUP-9040 Re: puppet lookup command returns warning with poor formatting Sorry Henrik Lindberg, it doesn't look like that provided any additional information: [root@pe-201812-master ~]# puppet lookup foo --explain --strict_variables --trace Warning: Undefined variable 'bar'; \n (file & line not available) Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Classifier Configuration Data" No such key: "lookup_options" Environment Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/code/environments/production/hiera.yaml" Merge strategy hash Hierarchy entry "Per-node data (yaml version)" Path "/etc/puppetlabs/code/environments/production/data/nodes/pe-201812-master.puppetdebug.vlan.yaml"
Jira (PUP-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Paul Schaffer created an issue Puppet / PUP-9040 puppet lookup command returns warning with poor formatting Issue Type: Task Affects Versions: PUP 5.5.2 Assignee: Unassigned Created: 2018/08/03 12:15 PM Labels: maintenance triage Priority: Normal Reporter: Paul Schaffer When performing a hiera lookup against a hierarchy that includes an undefined variable, the warning message that Puppet returns includes a new line marker: [root@pe-201812-master ~]# puppet lookup "foo" Warning: Undefined variable 'bar'; \n (file & line not available) Otherwise the lookup appears to perform as intended: [root@pe-201812-master ~]# puppet lookup
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-8770
Puppet resource service status should be more than binary
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/05/22 12:32 PM
Priority:
Normal
Reporter:
Paul Schaffer
When the Puppet Agent runs during boot (or at other times, during changes of various sorts), some services may still be starting, which means they show a different state than "active" for the service units. When Puppet runs, it tries to enforce { ensure=>running , enable => true} on the Service resource, which ends up restarting the already-starting service. For example, when restarting a host running a MariaDB Galera cluster, MariaDB is in the process of "catching up" with the cluster (via IST) when Puppet restarts it. That ends up breaking the incremental updates, requiring the node to take even longer to start up again by doing a full SST (which also makes another node in the cluster unavailable at that time). The desired behavior is that Puppet would see that the service is already in the process of starting, and do nothing, or possibly just log a warning. A similar issue likely exists for services which are in the process of stopping. The command `systemctl status is-active mariadb.service` returns this output in these states:
active (exit code 0) – normal "fully started" state
inactive (exit code 3) – fully stopped
deactivating (exit code 3) – in the process of stopping
activating (exit code 3) – in the process of starting
Puppet is simply leveraging an exit code of 0 or nonzero to determine the state, but it should probably be interpreting the actual state, through the contents of STDOUT from `systemctl is-active $SERVICE_NAME` for instance, so that it can properly handle these other states.
Jira (PUP-8675) Attempting to use `puppet config --section -- set` breaks the config command.
Title: Message Title Paul Schaffer moved an issue Puppet / PUP-8675 Attempting to use `puppet config --section -- set` breaks the config command. Change By: Paul Schaffer Affects Version/s: PE 2018.1.1 Affects Version/s: PE 2017.1.1 Affects Version/s: PUP 5.5.1 Key: PE PUP - 20298 8675 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received
Jira (PUP-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-8536 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment Change By: Paul Schaffer Issue Type: Bug Improvement 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-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-8536 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment Change By: Paul Schaffer Issue Type: Improvement 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 (PUP-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-8536
If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2018/03/08 11:38 AM
Priority:
Normal
Reporter:
Paul Schaffer
Puppet Version: 5.3.3 Puppet Server Version: 2017.3.2 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment. To reproduce the issue: Create a module called testmod, and set testmod's init.pp to the following:
class testmod {
notify { 'hello_world':
message => 'I am supposed to be here.'
}
}
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Paul Schaffer Summary: Group resource (with auth_membership) failes fails if local Windows group contains not resolvable Domain accounts Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Paul Schaffer 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Paul Schaffer Affects Version/s: PUP 4.10.4 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-3963) Error message gives wrong advice for allowed module names
Title: Message Title Paul Schaffer commented on PUP-3963 Re: Error message gives wrong advice for allowed module names Oops, doubled up with Marty - PR#6428 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Paul Schaffer A customer has noticed that they are getting It's possible to get a successful agent run reports report that on closer inspection include errors (ticket located here: https://puppetlabs . zendesk.com/agent/tickets/25207). The For instance, an error points to a failure with the Chocolatey provider. Because the provider failed out, it did not return a complete list of resources to manage, and the agent run completes successfully on this smaller catalog without raising an alarm. The issue with the Chocolatey provider was fixed in a later version of that module, however the overall issue There is still a problem: there is no way for an administrator to notice this problem and correct it without drilling down into green agent reports to confirm whether an error has occurred or not. On large scale deployments this solution rapidly becomes unmanageable.Agent runs need to return some condition when providers fail that highlights that this has occurred. There needs to be a scaleable way to monitor and report on this kind of failure. 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
Jira (PUP-7773) Puppet should recognize BOM in a hosts file
Title: Message Title Paul Schaffer created an issue Puppet / PUP-7773 Puppet should recognize BOM in a hosts file Issue Type: Bug Assignee: Unassigned Created: 2017/07/12 4:04 PM Priority: Normal Reporter: Paul Schaffer Windows hosts files are encoded as ANSI, however some devices and software write entries to the hosts file in other encodings such as UTF-16. Puppet consumes the hosts file as Encoding.default_external instead of recognizing the UTF-16LE BOM and then writes the file back out as Encoding.default_external, leading to issues such as inserting whitespace between every character in the previous entries, which breaks Windows networking. Puppet should check for a BOM in the hosts file first, then if one is detected load the file accordingly / preserve the content of the file. Add Comment
Jira (PUP-7651) The Notify Resource for Devices
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-7651
The Notify Resource for Devices
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/06/12 8:58 AM
Priority:
Normal
Reporter:
Paul Schaffer
Devices should be able to handle the notify resource. For instance:
Given this manifest: node 'pe-201652-master' { include f5 }
node 'bigip' { notify {"TJK": }
f5_virtualserver { '/Common/puppet_vs': ensure => 'present', provider => 'standard', description => 'Hello World', destination_address => '10.20.30.40', destination_mask => '255.255.255.255', http_profile => '/Common/http', service_port => '443', protocol => 'tcp', source => '0.0.0.0/0', source_address_translation => 'automap', }
}
We don't see any notify output: [root@pe-201652-master manifests]# puppet device -v --user=root Info: starting applying configuration to bigip at https://54.244.180.9:443/ Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for bigip Info: Applying configuration version '1497281724' Notice: Applied catalog in 3.12 seconds
Can we add notify to the list of supported resources for devices?
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Paul Schaffer commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] It's admittedly an unlikely case, but I discovered this after a customer opened a ticket because they'd set the certname of the system to something other than the FQDN through declaring the certname in both the [agent] and [master] sections of puppet.conf prior to installing the agent. Though the system is reachable via mco at the certname and all of the contents of the ssl directory have the correct certname 'puppet config print certname' returns the FQDN, which is an inaccurate description of the state of the machine. One (or both) of the values in [agent] and [master] were sufficient to generate the desired certnames for the system, but the print command ignores them both unless you specifically designate the section. It would seem more accurate to default to the value set in [main], but to then return the value if set in any other section before defaulting to the FQDN. 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-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Paul Schaffer created an issue Puppet / PUP-7638 `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/06/08 3:55 PM Priority: Normal Reporter: Paul Schaffer `puppet config print certname` appears to read from the [main] section of puppet.conf only, and if certname is not set in that section it defaults to the FQDN of the system. To test: 1. Spin up a blank box. 2. Create puppet.conf and set the certname to something other than the FQDN. 3. Install the agent, confirming that the certname has been set to something other than the FQDN. 4. Run `puppet config print certname` and compare to expected output. Additionally: 1. Open puppet.conf, and if certname is set in [main] comment it out. 2. Add a unique certname value to the [agent] section and save and close the file. 3. Run 'puppet config print certname' and compare to expected output. 4. Run 'puppet config print --section=agent` and compare. 5. Repeat for any other sections, such as [master].
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Paul Schaffer moved an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Paul Schaffer Affects Version/s: PE 2017.1.1 Affects Version/s: PUP 4.7.0 Affects Version/s: PUP 4.9.4 Key: PE PUP - 20411 7630 Project: Puppet Enterprise [Internal] 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
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title Paul Schaffer commented on PUP-2551 Re: Certname must be lowercase error not helpful Simplified the warning to "All certificate names must be fully lowercase." in pull requests https://github.com/puppetlabs/puppet/pull/5902 and https://github.com/puppetlabs/puppet-docs/pull/748 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 (FACT-1619) Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0
Title: Message Title Paul Schaffer created an issue Facter / FACT-1619 Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0 Issue Type: Bug Affects Versions: FACT 3.4.1 Assignee: Unassigned Created: 2017/04/28 1:20 PM Environment: Publisher: solaris Version: 0.5.11 Build Release: 5.11 Branch: 0.175.3.17.0.3.0 Puppet: 4.7.0 Priority: Normal Reporter: Paul Schaffer On Solaris 11.3 SPARC boxes, patch level 17.0.3.0 the memory fact fails with the following error: root@testbox:~# /opt/puppetlabs/puppet/bin/facter memory --debug 2017-04-28 15:05:26.434530 INFO puppetlabs.facter - executed with command line: memory --debug. 2017-04-28 15:05:26.442146 INFO leatherman.ruby:133 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2". 2017-04-28 15:05:26.548339 INFO leatherman.ruby:182 - using ruby version 2.1.9 2017-04-28 15:05:26.548774 INFO puppetlabs.facter - requested queries: memory. 2017-04-28 15:05:26.549301 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.4.1". 2017-04-28 15:05:26.549543 DEBUG
Jira (PDB-3473) PDB query that can return a list of nodes in a given group
Title: Message Title Paul Schaffer created an issue PuppetDB / PDB-3473 PDB query that can return a list of nodes in a given group Issue Type: New Feature Assignee: Unassigned Created: 2017/04/20 8:29 AM Priority: Normal Reporter: Paul Schaffer Create a new endpoint or extend the functionality of a current one so that a user can issue a query about a specific group (either through group name or group ID) and have it return a list of nodes associated with that group (whether statically or dynamically pinned). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
