Jira (FACT-3190) List processor vendor under cpu
Title: Message Title Pat Riehecky created an issue Facter / FACT-3190 List processor vendor under cpu Issue Type: Improvement Assignee: Unassigned Created: 2023/03/03 8:37 AM Priority: Normal Reporter: Pat Riehecky When doing system management some settings are specific to Intel CPUs, some for AMD CPUs. For example, intel_iommu and amd_iommu or Intel PCM. Having a default system fact with the CPU vendor would simplify the detection greatly. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Pat Riehecky commented on PUP-11759 Re: trusted fqdn fact I'd prefer a "fully" trusted version. My certname for the hosts is often a UUID for "reasons" so I'm assembling it by hand with a trivial join. I'm controlling access to SSL certificates and kerberos keytabs, so I don't really want to trust that the client has the right fqdn. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481383.1676405519000.10325.1676409360042%40Atlassian.JIRA.
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11759 trusted fqdn fact Issue Type: New Feature Assignee: Unassigned Created: 2023/02/14 12:11 PM Priority: Normal Reporter: Pat Riehecky With the legacy top level facts going away, it would be handy if there as a $::trusted['fqdn'] fact I could pull in. In practice I know I can concat $::trusted['hostname'] with $::trusted['domain'], but making sure my mass find/replace is syntax valid for all the quoting and whatnot is going to be ugly. A trusted replacement fact would be great so I don't have to constantly repeat that pattern everywhere. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11588) dnfmodule issues with Nvidia CUDA repository
Title: Message Title Pat Riehecky commented on PUP-11588 Re: dnfmodule issues with Nvidia CUDA repository Is there a way to help get a resolution for this prioritized? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.454330.1657121517000.8879.1675887000528%40Atlassian.JIRA.
Jira (PUP-11627) Bump augeas to 1.14.0
Title: Message Title Pat Riehecky commented on PUP-11627 Re: Bump augeas to 1.14.0 The 7.22.0 AIO package would be a great target for this. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.468405.166370805.4009.1674672360026%40Atlassian.JIRA.
Jira (PUP-11724) Unable to target dnfmodule stream named `latest`
Title: Message Title Pat Riehecky commented on PUP-11724 Re: Unable to target dnfmodule stream named `latest` From a workflow perspective, omitting the version ensures the default stream is installed rather than the highest versioned one. That is, to my mind, not fulfilling the spirit of the "latest". Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479508.1674582615000.3595.1674583260026%40Atlassian.JIRA.
Jira (PUP-11724) Unable to target dnfmodule stream named `latest`
Title: Message Title
Pat Riehecky created an issue
Puppet / PUP-11724
Unable to target dnfmodule stream named `latest`
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/01/24 9:50 AM
Priority:
Normal
Reporter:
Pat Riehecky
Puppet Version: 7.21.0 Puppet Server Version: 7.12 OS Name/Version: AlmaLinux 9 NVidia has a module stream named `latest` which I'd like to use. The documentation the `dnfmodule` provide indicates I should set the target stream under the `ensure` property. Which as you'd expect makes things a bit weird. Their repo contains a stream called `latest-dkms` which ends up getting targeted instead as the `ensure` is omitted. Describe steps to reproduce… Add yum repo : https://developer.download.nvidia.com/compute/cuda/repos/rhel$releasever/$basearch/ ``` puppet apply -e " package {'nvidia-driver': ensure => 'latest', flavor => 'fm', provider => 'dnfmodule', } " dnf module list ``` Desired Behavior: Some sort of way to target the stream named "latest" 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 ``` Info: Using environment 'production' Info: Applying configuration version '1674582424' Debug: Prefetching dnfmodule resources for package Debug: Executing: '/usr/bin/dnf --version' Debug: Executing: '/usr/bin/dnf module list -d 0 -e 1' Debug: Executing: '/usr/bin/dnf module list -d 0 -e 1' Debug: Executing: '/usr/bin/dnf module install -d 0 -e 1 -y nvidia-driver/fm' Notice: /Stage[main]/Main/Package[nvidia-driver]/ensure: created Debug: /Package[nvidia-driver]: The container Class[Main] will propagate my refresh event Debug: Class[Main]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 11940 Debug: Storing state Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml Debug: Pruned old state cache entries in 0.00 seconds Debug: Stored state in 0.00 seconds Notice: Applied catalog in 97.96 seconds ```
Jira (PDB-5580) puppetlabs/puppetdb uses whitelist/blacklist rather than allow/deny
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5580 puppetlabs/puppetdb uses whitelist/blacklist rather than allow/deny Issue Type: Bug Assignee: Unassigned Created: 2023/01/18 9:44 AM Priority: Normal Reporter: Pat Riehecky The official puppetlabs puppetdb module https://forge.puppet.com/modules/puppetlabs/puppetdb/ uses whitelist/blacklist rather than the new terminology. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5579) puppet module to install and configure puppetdb_cli
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5579 puppet module to install and configure puppetdb_cli Issue Type: New Feature Assignee: Unassigned Created: 2023/01/18 9:25 AM Priority: Normal Reporter: Pat Riehecky The puppetdb_cli tools are handy for spot checking and quick queries. Having the official puppetdb module add this tool to the puppetdb server would be a great way for folks to test connectivity issues. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11714) puppet generate types --all-environments would be nice
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11714 puppet generate types --all-environments would be nice Issue Type: Improvement Assignee: Unassigned Components: Types and Providers Created: 2023/01/13 1:20 PM Priority: Normal Reporter: Pat Riehecky When deploying multiple environments from `r10k` it is unclear which ones are updated and need the types regenerated. Because each environment must be specified one at a time, there is some trivial repetition in in rebuilding the types. If `puppet generate types --all-environments` was available it would simplify the workflow greatly and result in an overall better user experience. Add Comment
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title Pat Riehecky commented on PUP-11700 Re: puppet generate types --environment doesn't accept full path Can you add those flags to `–help` as they are both missing Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.478334.1673381987000.71489.1673385480211%40Atlassian.JIRA.
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title
Pat Riehecky created an issue
Puppet / PUP-11700
puppet generate types --environment doesn't accept full path
Issue Type:
Improvement
Affects Versions:
PUP 7.20.0
Assignee:
Unassigned
Components:
Type System
Created:
2023/01/10 12:19 PM
Priority:
Normal
Reporter:
Pat Riehecky
When running `puppet generate types --environment /etc/puppetlabs/code/environments/test` I get an error: Could not find a directory environment named '/etc/puppetlabs/code/environments/test' {{}} It would be helpful if I could use full paths.{}
Add Comment
Jira (PDB-5569) RHEL9 packages for puppetdb
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5569 RHEL9 packages for puppetdb Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2023/01/05 11:14 AM Priority: Normal Reporter: Pat Riehecky Is there an expected timetable for puppetdb to be packaged for RHEL9? The RHEL9 platform has been out for a while Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11694) file resource timeout fetching over https
Title: Message Title
Pat Riehecky created an issue
Puppet / PUP-11694
file resource timeout fetching over https
Issue Type:
Bug
Affects Versions:
PUP 7.20.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2022/12/22 8:46 AM
Priority:
Normal
Reporter:
Pat Riehecky
Puppet Version: 7.20 Puppet Server Version: 7.20 OS Name/Version: AlmaLinux 9 When fetching a resource over https, it is possible to reach a 60 second timeout canceling the fetch. This can be an intermittent problem if an overloaded webserver is hit by multiple clients at time or the link is temporarily congested. Desired Behavior: A way increase the timeout Actual Behavior: file { "${esp_dir}/${efi_rescue_dir}/images/${stage2_name}": ensure => 'file', source => 'https://linux-mirrors.fnal.gov/linux/almalinux/9/BaseOS/x86_64/kickstart/images/install.img', } Examples: Run puppet agent with --test --trace --debug
Error: Request to https://linux-mirrors.fnal.gov/linux/almalinux/9/BaseOS/x86_64/kickstart/images/install.img interrupted after 61.723 seconds
Error: /Stage[main]/Efi_rescue/File[/boot/efi/rescue/images/install.img]/ensure: change from 'absent' to 'file' failed: Request to https://linux-mirrors.fnal.gov/linux/almalinux/9/BaseOS/x86_64/kickstart/im
Jira (PUP-11627) augeas lenses out of date in AIO agent
Title: Message Title Pat Riehecky commented on PUP-11627 Re: augeas lenses out of date in AIO agent Auges 1.14.0 has the updated lense as a part of its release. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.468405.166370805.65491.1670795580058%40Atlassian.JIRA.
Jira (FACT-3169) Report systemd SUPPORT_END if present
Title: Message Title Pat Riehecky created an issue Facter / FACT-3169 Report systemd SUPPORT_END if present Issue Type: New Feature Assignee: Unassigned Created: 2022/12/05 6:43 AM Priority: Normal Reporter: Pat Riehecky Systemd introduced a metadata field in /etc/os-release for a vendor to indicate the end of support https://www.freedesktop.org/software/systemd/man/os-release.html#SUPPORT_END= It would be helpful if facter added this value if present to the OS information Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11627) augeas lenses out of date in AIO agent
Title: Message Title Pat Riehecky commented on PUP-11627 Re: augeas lenses out of date in AIO agent Alas, that does not. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.468405.166370805.37220.1664310900090%40Atlassian.JIRA.
Jira (PUP-11627) augeas lenses out of date in AIO agent
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11627 augeas lenses out of date in AIO agent Issue Type: Bug Affects Versions: PUP 7.18.0 Assignee: Unassigned Created: 2022/09/20 2:07 PM Priority: Normal Reporter: Pat Riehecky Puppet Version: 7.18.0 Puppet Server Version: 7 OS Name/Version: RHEL 9 Install the current AIO agent and review the provided augeas lenses (/opt/puppetlabs/puppet/share/augeas/lenses/dist) vs the latest released augeas lenses. Desired Behavior: Augeas lenses (in particular kdump.aug) match latest upstream release. Actual Behavior: With RHEL9 new options were added to kdump.conf that are not recognized by the lense in the AIO agent. Odds are there are other lenses that are out of date as well. Examples: Run puppet agent with --test --trace --debug ``` Augeas[kdump_conf_extra_modules_setup](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output ``` Additional Information: https://github.com/hercules-team/augeas/commit/288a028da531a5f58d9ee89bc29fd73e7483bf24 Add Comment
Jira (HI-633) Content from eyaml should be Sensitive by default
Title: Message Title Pat Riehecky created an issue Hiera / HI-633 Content from eyaml should be Sensitive by default Issue Type: Improvement Assignee: Unassigned Created: 2022/09/19 8:00 AM Priority: Normal Reporter: Pat Riehecky When content is decoded from an `eyaml` backend, hiera should automatically mark it as a Sensitive data type. Currently it is just converted to the backing data type. This can lead to unintended disclosure of the encrypted values within modules. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11605) config option to use splay after the initial run
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11605 config option to use splay after the initial run Issue Type: Improvement Assignee: Unassigned Created: 2022/08/12 11:06 AM Priority: Normal Reporter: Pat Riehecky For my site it would be helpful if I could run the puppet service immediately and, only after the first run of the client, have the splay values used for follow up by the daemon runs. Something like `splay_initial_run` have it default to `true` so the existing behavior is preserved, but can be shifted a bit. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5522) Docker custom entrypoint scripts
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5522 Docker custom entrypoint scripts Issue Type: Improvement Assignee: Unassigned Created: 2022/08/05 10:10 AM Priority: Normal Reporter: Pat Riehecky It would be helpful if, like the puppet-server, container the puppetdb container had a place for me to deploy my site local customizations for the container. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3140) Include partition type uuid for GPT based systems
Title: Message Title Pat Riehecky created an issue Facter / FACT-3140 Include partition type uuid for GPT based systems Issue Type: Improvement Assignee: Unassigned Created: 2022/08/05 9:05 AM Priority: Normal Reporter: Pat Riehecky When looking for partitions, it would be helpful if the partition type uuid was also included in the facter output. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3132) routing table
Title: Message Title Pat Riehecky commented on FACT-3132 Re: routing table I've got a few hosts with complex routing tables due to their various networks. Having facter report the table information will let me easily record the information, view differences between hosts, and track any changes. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.453864.1656527559000.58680.1657124160205%40Atlassian.JIRA.
Jira (PUP-11585) yumrepo_core doesn't create file resources
Title: Message Title Pat Riehecky commented on PUP-11585 Re: yumrepo_core doesn't create file resources I'm not aware of a way to use the yumrepo type in that manner. It gets more complex when consuming content via subscription-manager. The repo file is written out directly there. It can be tracked with a `File` resource, but without having the other files under the `File` scope, it is a bit of a mess. https://github.com/voxpupuli/puppet-yum/pull/258#issuecomment-1173727992 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.454108.1657029979000.58614.1657120860057%40Atlassian.JIRA.
Jira (PUP-11585) yumrepo_core doesn't create file resources
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11585 yumrepo_core doesn't create file resources Issue Type: Improvement Assignee: Unassigned Created: 2022/07/05 7:06 AM Priority: Normal Reporter: Pat Riehecky The yumrepo_core type creates elements in /etc/yum.repos.d/ but does not create a File resource for those items. As a result, if /etc/yum.repos.d/ is set to purge unmanaged files, the newly created resources are immediately removed making things non-idempotent and also confusing. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3132) routing table
Title: Message Title Pat Riehecky created an issue Facter / FACT-3132 routing table Issue Type: Improvement Assignee: Unassigned Created: 2022/06/29 11:32 AM Priority: Normal Reporter: Pat Riehecky It would be helpful if some sort of routing table was also contained within the facter results to help isolate networking differences between hosts. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3131) Facter include DNS servers
Title: Message Title Pat Riehecky created an issue Facter / FACT-3131 Facter include DNS servers Issue Type: Improvement Assignee: Unassigned Created: 2022/06/29 11:21 AM Priority: Normal Reporter: Pat Riehecky It would be helpful if facter was also able to report DNS servers in use. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11583) yumrepo_core repo_gpgcheck
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11583 yumrepo_core repo_gpgcheck Issue Type: Improvement Assignee: Unassigned Created: 2022/06/29 8:33 AM Priority: Normal Reporter: Pat Riehecky Can `yumrepo_core` be extended to support the `repo_gpgcheck` flag? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11561) summary report show fact creation time cost
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11561 summary report show fact creation time cost Issue Type: Improvement Assignee: Unassigned Components: Catalog Application Created: 2022/06/22 11:47 AM Priority: Normal Reporter: Pat Riehecky When `summarize = true` it would also be helpful to list out how long it takes to generate facts on this system. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11560) yumrepo type support for `countme`
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11560 yumrepo type support for `countme` Issue Type: New Feature Assignee: Unassigned Components: Modules Created: 2022/06/22 8:27 AM Priority: Normal Reporter: Pat Riehecky DNF has added a new flag `countme` that would be nice to support within the yumrepo type. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5501) Docker TLS for postgresql
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5501 Docker TLS for postgresql Issue Type: Improvement Assignee: Unassigned Created: 2022/06/09 8:22 AM Priority: Normal Reporter: Pat Riehecky It would be helpful if the puppetdb container had a clear way to enable TLS support for postgresql (TLS encryption and/or Certificate Authentication). Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11517) Tell puppet it needs a second run
Title: Message Title Pat Riehecky commented on PUP-11517 Re: Tell puppet it needs a second run I found https://forge.puppet.com/modules/morpheu/refacter which is somewhat close to my needs, but having this sort of thing built in would be very helpful. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444665.1650652859000.42960.1654270680069%40Atlassian.JIRA.
Jira (PDB-5499) puppetdb Docker health check hostname
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5499 puppetdb Docker health check hostname Issue Type: Improvement Assignee: Unassigned Created: 2022/06/01 10:09 AM Priority: Normal Reporter: Pat Riehecky It would be nice if the hostname used for the Docker health check could be set to a specific value (and port) to allow for more flexible deployments. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5497) puppetdb container out of date
Title: Message Title Pat Riehecky created an issue PuppetDB / PDB-5497 puppetdb container out of date Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2022/05/20 8:33 AM Priority: Normal Reporter: Pat Riehecky The container at https://hub.docker.com/r/puppet/puppetdb does not have the 7.10.1 tag Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3122) partition `mounted_as` attribue
Title: Message Title Pat Riehecky created an issue Facter / FACT-3122 partition `mounted_as` attribue Issue Type: New Feature Assignee: Unassigned Created: 2022/05/16 10:04 AM Priority: Normal Reporter: Pat Riehecky For doing manipulations/audits/etc it would be helpful if the `partitions` hash had a `monted_as` (or similar) key for each partition. In this way I can easily find `/boot` or `D:` without more advanced tricks. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (HI-631) merge unique with a knockout prefix
Title: Message Title Pat Riehecky created an issue Hiera / HI-631 merge unique with a knockout prefix Issue Type: New Feature Assignee: Unassigned Created: 2022/05/04 10:54 AM Priority: Normal Reporter: Pat Riehecky For most cases, a deep merge is sufficient. However, there are a few minor workflows where having a knockout prefix for unique lists would be very advantageous. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3119) RFC2863 operational state for network interfaces
Title: Message Title Pat Riehecky created an issue Facter / FACT-3119 RFC2863 operational state for network interfaces Issue Type: New Feature Assignee: Unassigned Components: Facter 4 Created: 2022/05/03 7:26 AM Priority: Normal Reporter: Pat Riehecky For working with and tracking the network interface state, it would be helpful to track the RFC2863 operational state of these interfaces. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3118) is network interface physical
Title: Message Title Pat Riehecky created an issue Facter / FACT-3118 is network interface physical Issue Type: New Feature Affects Versions: FACT 4.2.8 Assignee: Unassigned Created: 2022/05/02 8:32 AM Priority: Normal Reporter: Pat Riehecky When looking at network interfaces, it is helpful to have a way to distinguish between software defined interfaces and physical ones. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11514) Extract elements from resource collector
Title: Message Title Pat Riehecky commented on PUP-11514 Re: Extract elements from resource collector The more general "query" is probably what I'd need. The resource titles are coming out of hiera, so I don't know them in advance... Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.71.1650481423000.18530.1651066621102%40Atlassian.JIRA.
Jira (PUP-11517) Tell puppet it needs a second run
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11517 Tell puppet it needs a second run Issue Type: New Feature Assignee: Unassigned Created: 2022/04/22 11:40 AM Priority: Normal Reporter: Pat Riehecky Some of my puppet modules require more than one run to finish configuring a specific element. For example, my RAID card management module uses facts generated by the management tools. If these tools are not installed, the module installs them, but because the facts could not be populated the array isn't configured until a second run occurs. With runs happening every 2 hours at my site, this ends up being a very long time to wait. It would be helpful if there was a way I could tell the agent "after this run, immediately schedule another run". Add Comment
Jira (PUP-11514) Extract elements from resource collector
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11514 Extract elements from resource collector Issue Type: New Feature Affects Versions: PUP 7.15.0 Assignee: Unassigned Created: 2022/04/20 12:03 PM Priority: Normal Reporter: Pat Riehecky For some applications getting data back out of collected resources would be very helpful. For example, the `sssd` service requires you to define a list of active domains and have configuration section detailing how that domain should operate. Today if I generate a custom type (for example `sssd::domain`) and collect that type (`Sssd::Domain<| |>`), I don't have a great way of extracting the domain name so I don't need to repeat it. Propose sort of thingy `$titles = Sssd::Domain<| |>.title` would return some sort of Array containing the title attributes from the collected Sssd::Domain types. Add Comment
Jira (PUP-10732) Puppet service report next prjected runtime
Title: Message Title Pat Riehecky created an issue Puppet / PUP-10732 Puppet service report next prjected runtime Issue Type: Improvement Assignee: Unassigned Created: 2020/10/30 7:36 AM Priority: Trivial Reporter: Pat Riehecky It would be helpful if the puppet service logged the next projected runtime. For example, I've got a run interval of 1 hour and a splay of 20 minutes. It would be nice if I could view the logs to get an estimate of when puppet is likely to run again on this host. I'd love to have this information logged when the service starts and after each run (so that I can see when the next one is likely). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f93
Jira (HI-620) Hiera mapped_paths should permit glob expansion
Title: Message Title
Pat Riehecky created an issue
Hiera / HI-620
Hiera mapped_paths should permit glob expansion
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2020/09/15 8:57 AM
Priority:
Normal
Reporter:
Pat Riehecky
It would be helpful for breaking out files into more manageable chunks, if hiera's mapped_paths option would permit use of globs for expansion. For example: {{- name: Example mapped_paths: [services, tmp, "service/%{tmp}/*.yaml"}}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Pat Riehecky created an issue Puppet / PUP-10666 puppet-agent config option require message for disable Issue Type: New Feature Assignee: Unassigned Created: 2020/09/14 7:14 AM Priority: Normal Reporter: Pat Riehecky Hello, Could a config option be added for the puppet agent to require a message when running `puppet agent --disable`? For larger sites with multiple admins, it would be helpful to have a way to force this best practice. I don't expect it to stop `puppet agent --disable ' '` but in that instance the admin knows they are leaving a useless message against the policy. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10608) Option to "prettyprint" /opt/puppetlabs/puppet/cache/client_data/catalog
Title: Message Title Pat Riehecky commented on PUP-10608 Re: Option to "prettyprint" /opt/puppetlabs/puppet/cache/client_data/catalog That makes sense to me, I'd say this can be canceled. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.367667.1596031358000.34794.1599856140026%40Atlassian.JIRA.
Jira (HI-619) Hiera return all keys (or keys matching pattern)
Title: Message Title Pat Riehecky created an issue Hiera / HI-619 Hiera return all keys (or keys matching pattern) Issue Type: New Feature Affects Versions: HI 3.5.0 Assignee: Unassigned Components: CLI Created: 2020/09/11 12:33 PM Priority: Normal Reporter: Pat Riehecky I'd like to have an option for hiera lookups to fetch all keys (or keys matching a pattern). Example use case: I'm looking to change my existing hierarchy by adding/removing a new element. I'd like to validate that some nodes change and that others did not. Dumping the return result and doing diffs from old/new would give me clear insight into the consequences of the change before going live. I'm coming from an ENC (such as foreman) where I'm used to looking at the entire ENC config. As I develop my hiera setup, I'd like to fetch the output for a node in a manner I'm familiar with. A set of nodes is moving from my group to another group. I've given them a list of puppet modules I'm using for these nodes, but I'd also like to provide the values each node is using so they can develop their configuration management.
Jira (FACT-1815) Add numa facts
Title: Message Title Pat Riehecky created an issue Facter / FACT-1815 Add numa facts Issue Type: New Feature Assignee: Unassigned Created: 2018/02/02 7:18 AM Priority: Trivial Reporter: Pat Riehecky Desired Behavior: Facter should provide some facts to help identify NUMA aware systems and which NUMA zones are viable for a given system. At the minimum two facts are useful: Are there NUMA zones What NUMA zones exist Actual Behavior: No facts provided Linux systems can identify this via: /sys/devices/system/node/possible Examples: numa_aware = true numa_zones = 0-1 numa_aware = false numa_zones = 0 Add Comment
Jira (FACT-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Pat Riehecky commented on FACT-1592 Re: Networking key/value pair for Interface Speed and Duplex State If possible, I'd prefer the speed be an Integer of Mb per sec rather than 'human units' so I can easily to > or < for other matching. 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-8018) ENC option to run catalog in noop mode
Title: Message Title Pat Riehecky updated an issue Puppet / PUP-8018 ENC option to run catalog in noop mode Change By: Pat Riehecky Currently the ENC can provide the environment to the client. However, when testing a new environment on a client the workflow can result in running the catalog before I'm ready.Example workflow:1. disable puppet on the client2. build testing environment on the puppet master3. configure the ENC to send the new environment4. enable puppet in noop mode on the clientIf step 1 is not complete, the client may apply the catalog.This may also be useful in another workflow: if puppet needs to be temporarily disabled on a host. Puppet can set noop=true via a catalog run, but once this is done, there isn't a way to undo that without manual intervention. See also: https://www.example42.com/2017/03/06/server-side-noop-mode/ 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-8018) ENC option to run catalog in noop mode
Title: Message Title Pat Riehecky created an issue Puppet / PUP-8018 ENC option to run catalog in noop mode Issue Type: New Feature Assignee: Unassigned Components: Settings Created: 2017/10/03 8:16 AM Priority: Minor Reporter: Pat Riehecky Currently the ENC can provide the environment to the client. However, when testing a new environment on a client the workflow can result in running the catalog before I'm ready. Example workflow: 1. disable puppet on the client 2. build testing environment on the puppet master 3. configure the ENC to send the new environment 4. enable puppet in noop mode on the client If step 1 is not complete, the client may apply the catalog. This may also be useful in another workflow: if puppet needs to be temporarily disabled on a host. Puppet can set noop=true via a catalog run, but once this is done, there isn't a way to undo that without manual intervention. Add Comment
Jira (PUP-7685) puppet resource user may show double groups
Title: Message Title Pat Riehecky commented on PUP-7685 Re: puppet resource user may show double groups I have a host where my users are listed in /etc/passwd and in the db files created by nss_db (from glibc). My users end up listed in both locations. As a result the groups are double listed. I've also been able to replicate this with a user listed in both LDAP and local passwd file where both locations provide the same ID with similar groups (some identical, some unique to the source) 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-7685) puppet resource user may show double groups
Title: Message Title
Pat Riehecky created an issue
Puppet / PUP-7685
puppet resource user may show double groups
Issue Type:
Bug
Affects Versions:
PUP 4.10.3
Assignee:
Unassigned
Components:
Types and Providers
Created:
2017/06/21 9:22 AM
Priority:
Minor
Reporter:
Pat Riehecky
Systems with complex, and overlapping, user lookups may double list a user's groups.
For example:
$ puppet resource user riehecky
user { 'riehecky': ensure => 'present', comment => 'Patrick Riehecky', gid => '100', groups => ['wheel', 'mock', 'staff', 'wheel', 'mock', 'staff'], home => '/home/r/riehecky', shell => '/bin/bash', uid => '1', }
Jira (PUP-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky updated an issue Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Change By: Pat Riehecky Affects Version/s: PUP 4.9.4 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-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky assigned an issue to Pat Riehecky Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Change By: Pat Riehecky Assignee: Pat Riehecky 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-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky created an issue Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Issue Type: Improvement Affects Versions: PUP 4.9.4 Assignee: Unassigned Components: CLI Created: 2017/04/27 6:50 AM Environment: Command line testing of changes (with a typo) Priority: Normal Reporter: Pat Riehecky When testing puppet changes via the command line, a silly typo results in an agent run being executed. puppet agent -t -noop The correct command is puppet agent -t --noop. Can puppet agent error out if unrecognized arguments are presented on the command line? Unexpected runs of the agent can cause serious outages. Additionally puppet agent -disable does not produce an error which may leave folks believing puppet has been disabled when it has not.
Jira (FACT-1605) Network Link speed fact
Title: Message Title Pat Riehecky created an issue Facter / FACT-1605 Network Link speed fact Issue Type: New Feature Assignee: Unassigned Created: 2017/04/17 6:50 AM Priority: Trivial Reporter: Pat Riehecky With the increasing deployment of 40G and greater links speeds in server environments, it would be nice if Facter could report the link speed of any detected interfaces. For high speed networks often some additional system tunings are required. For datacenter auditing, having links speed automatically captured by puppetdb et.all would help track which systems have the enhanced links. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6326) mount native type use systemd mount units rather than fstab entry
Title: Message Title Pat Riehecky created an issue Puppet / PUP-6326 mount native type use systemd mount units rather than fstab entry Issue Type: New Feature Affects Versions: PUP 4.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/19 9:19 AM Environment: Linux with systemd Priority: Normal Reporter: Pat Riehecky Can the mount native type be extended to allow for the creation of systemd.mount units rather than /etc/fstab entries? https://www.freedesktop.org/software/systemd/man/systemd.mount.html
Jira (PUP-6325) mount native type support /etc/fstab.d/
Title: Message Title Pat Riehecky created an issue Puppet / PUP-6325 mount native type support /etc/fstab.d/ Issue Type: Improvement Affects Versions: PUP 4.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/19 9:16 AM Environment: Linux with linux-utils >= 2.19 Priority: Normal Reporter: Pat Riehecky To help separate out various managed mounts, it would be helpful if I could elect to place a specific mount into /etc/fstab.d/ Ideally I'd like to be able to group some mounts together - ie all mounts for mywebapp - into a single file under /etc/fstab.d/ to help encapsulate the specific reason for the mounts rather than mixing them in with system mounts or mounts for another purpose.
Jira (FACT-1404) Facter Fact for Fibre WWNs
Title: Message Title Pat Riehecky created an issue Facter / FACT-1404 Facter Fact for Fibre WWNs Issue Type: New Feature Affects Versions: FACT 2.4.6 Assignee: Unassigned Created: 2016/04/28 10:49 AM Priority: Normal Reporter: Pat Riehecky It would be handy if Facter also captured the WWN of my fibre devices so that I can export that information to my SAN folks. Add Comment This message was sent by At
Jira (FACT-1350) include dmi/id/product_version
Title: Message Title Pat Riehecky created an issue Facter / FACT-1350 include dmi/id/product_version Issue Type: Improvement Affects Versions: FACT 3.1.4 Assignee: Unassigned Created: 2016/02/24 12:52 PM Environment: Linux Priority: Trivial Reporter: Pat Riehecky Original Estimate: 1 hour Remaining Estimate: 1 hour Can the output of /sys/class/dmi/id/product_version be added as a fact under a linux kernel? On my system that contains useful information for locating support from the manufacture. cat /sys
Jira (PUP-4403) k5login should support setting selinux context and owner attributes
Title: Message Title Pat Riehecky created an issue Puppet / PUP-4403 k5login should support setting selinux context and owner attributes Issue Type: New Feature Affects Versions: PUP 3.7.5 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/04/13 1:57 PM Labels: trivial Priority: Normal Reporter: Pat Riehecky Original Estimate: 3 hours Remaining Estimate: 3 hours When creating the .k5login fi
