Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Patrick Grant commented on FACT-3188 Re: Error on on Solaris non-global zone after upgrading to PE2021.7.2 Another instance of this in https://puppetlabs.zendesk.com/agent/tickets/52278 from ANZ bank. Beforehand the facts would just come back empty but now the errors are flagging the customers monitoring so this will need to be addressed Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481890.1677480699000.367.1686839460021%40Atlassian.JIRA.
Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Patrick Grant updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Patrick Grant Zendesk Ticket Count: 1 2 Zendesk Ticket IDs: 51151 ,52278 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481890.1677480699000.366.1686839340091%40Atlassian.JIRA.
Jira (PUP-11847) User resources on AIX call lsgroup command multiple times, adding a lot of time to puppet runs
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11847 User resources on AIX call lsgroup command multiple times, adding a lot of time to puppet runs Change By: Patrick Grant When the users are managed on AIX, this calls the lsgroup command. When connected to both Ldap and local directories, this can call can take a significant amount of time. (In the case of the customer I'm raising this on behalf of, 23 seconds per call) When multiple users are managed this can add a considerable amount of time to your puppet run (customer case had 10 users managed , puppet runs were totaling 5 minutes +), running the same command. Is there any way this lsgroup can be run once for all user resources on this OS?~* Please see Zendesk Support tab for further comments and attachments.~ 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
Jira (PUP-11847) User resources on AIX call lsgroup command multiple times, adding a lot of time to puppet runs
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11847 User resources on AIX call lsgroup command multiple times, adding a lot of time to puppet runs Change By: Patrick Grant Summary: User resources on AIX call lsgroup command multiple times , adding a lot of time to puppet runs 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.485200.1683213405000.10954.1683213600038%40Atlassian.JIRA.
Jira (PUP-11847) User resources on AIX call lsgroup command multiple times
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11847 User resources on AIX call lsgroup command multiple times Change By: Patrick Grant When the users are managed on AIX, this calls the lsgroup command. When connected to both Ldap and local directories, this can call can take a significant amount of time. (In the case of the customer I'm raising this on behalf of, 23 seconds per call) When multiple users are managed this can add a considerable amount of time to your puppet run, running the same command. Is there any way this lsgroup can be run once for all user resources on this OS?~* Please see Zendesk Support tab for further comments and attachments.~ 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
Jira (FACT-3199) facts with regular expression matching characters in the name of the fact cause facter 4 to crash
Title: Message Title
Patrick Grant updated an issue
Facter / FACT-3199
facts with regular _expression_ matching characters in the name of the fact cause facter 4 to crash
Change By:
Patrick Grant
Customer A customer noticed this after the move from facter 3 to facter 4, using the following code, i I have reproduced this locally: {code:java}Facter.add("hello(there") do setcode do"greetings" endend{code}Results in:{code:java}$ facter -pTraceback (most recent call last):31: from /opt/puppetlabs/puppet/bin/facter:10:in `'30: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli_launcher.rb:23:in `start'29: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'28: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'27: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'26: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'25: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli.rb:124:in `query'24: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:454:in `to_user_output'23: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:521:in `resolve_facts_for_user_query'22: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:24:in `resolve_facts'21: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/external/external_fact_manager.rb:7:in `resolve_facts'20: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/external/external_fact_manager.rb:19:in `external_facts'19: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/external/external_fact_manager.rb:19:in `each'18: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/external/external_fact_manager.rb:21:in `block in external_facts'17: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/custom_facts/util/fact.rb:127:in `value'16: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/custom_facts/util/fact.rb:177:in `searching'15: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/custom_facts/util/fact.rb:137:in `block in value'14: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/custom_facts/util/fact.rb:161:in `resolve_value'13: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:134:in `core_value'12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:67:in `resolve_core'11: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:83:in `core_fact'10: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/parsers/query_parser.rb:31:in `parse' 9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/parsers/query_parser.rb:31:in `each' 8: from
Jira (FACT-3199) facts with regular expression matching characters in the name of the fact cause facter 4 to crash
Title: Message Title Patrick Grant updated an issue Facter / FACT-3199 facts with regular _expression_ matching characters in the name of the fact cause facter 4 to crash Change By: Patrick Grant Zendesk Ticket Count: 1 Zendesk Ticket IDs: 51837 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.485170.1683128012000.10640.1683128100030%40Atlassian.JIRA.
Jira (FACT-3185) facter os.windows.product_name incorrect value for Windows 11
Title: Message Title Patrick Grant commented on FACT-3185 Re: facter os.windows.product_name incorrect value for Windows 11 Still an issue In PE 2023 after testing 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.481300.1676300202000.9902.1676313780019%40Atlassian.JIRA.
Jira (FACT-3185) facter os.windows.product_name incorrect value for Windows 11
Title: Message Title Patrick Grant commented on FACT-3185 Re: facter os.windows.product_name incorrect value for Windows 11 Potentially fixed by https://tickets.puppetlabs.com/browse/FACT-3090 Will need a test on latest version of PE to confirm 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.481300.1676300202000.9845.1676311860021%40Atlassian.JIRA.
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title Patrick Grant commented on FACT-3178 Re: Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC Question from todays Phoenix/support call, did this work in Facter 3? Facter debug output from both working and failure would be useful as well 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.479125.1673888594000.9844.1676311440018%40Atlassian.JIRA.
Jira (FACT-3185) facter os.windows.product_name incorrect value for Windows 11
Title: Message Title Patrick Grant created an issue Facter / FACT-3185 facter os.windows.product_name incorrect value for Windows 11 Issue Type: Bug Assignee: Unassigned Created: 2023/02/13 6:56 AM Priority: Normal Reporter: Patrick Grant Windows 11 currently displays the following from a facter 4 output: C:\ProgramData\PuppetLabs>facter -p os.windows.product_name Windows 10 Enterprise Evaluation C:\ProgramData\PuppetLabs>facter -v 4.2.8
Jira (FACT-3167) Networking facts on AIX incomplete if network device is in down state
Title: Message Title Patrick Grant created an issue Facter / FACT-3167 Networking facts on AIX incomplete if network device is in down state Issue Type: Bug Assignee: Unassigned Created: 2022/11/23 7:57 AM Priority: Normal Reporter: Patrick Grant Noticed in PE 2021.7 puppet agent --version 7.18.0 facter --version 4.2.11 If any network interface is in down state (chdev -l enX -a state=down), facter does not report networking::interfaces::enX::ip|mac|mtu for any interfaces. facter --debug shows the following error: ... DEBUG Facter::Resolvers::Aix::Networking - Could not resolve ip6, got undefined method `[]=' for nil:NilClass at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/aix/networking.rb:51:in `block in populate_with_mtu_and_mac!' ... DEBUG Facter::Resolvers::Aix::Networking - Could not resolve mac, got undefined method `[]=' for nil:NilClass at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/aix/networking.rb:51:in `block in populate_with_mtu_and_mac!'
Jira (PUP-11508) Package collection triggers install
Title: Message Title Patrick Grant commented on PUP-11508 Re: Package collection triggers install We spoke about this in todays Support/Phoenix sync meeting, with no clear path forward from the dev side of things, would it be possible to get this documented as a known issue Parker Leach ? 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.443888.164996258.44352.1665420480252%40Atlassian.JIRA.
Jira (FACT-3144) Hypervisors experimental fact improvements
Title: Message Title Patrick Grant commented on FACT-3144 Re: Hypervisors experimental fact improvements The customers use case is indeed to use the facts to provide a hiera source for openstack machines, and at the minute the format of the data isn't useful for that 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.466448.1662372316000.31821.1663161660089%40Atlassian.JIRA.
Jira (FACT-3144) Hypervisors experimental fact improvements
Title: Message Title
Patrick Grant updated an issue
Facter / FACT-3144
Hypervisors experimental fact improvements
Change By:
Patrick Grant
Info raised from a support customer:The info it (hypervisor experimental fact) provides at the moment isn't very useful.I wanted to provide some feedback in hopes of improving it in future versions.I use 2 hypervisors. openstack and vmware. At the moment.on openstack it returns "hypervisors::kvm::openstack: true" I would like to use it to provide a hiera source for openstack machines. Which is incovenient with that data format.I would find it more useful if it returned something like{code:java}hypervisors::virtualisation: kvmhypervisors::cluster: openstack.{code} Similarly for vmware, it returns "hypervisors::vmware: {}" which is difficult to make use of.I would find it more useful if it returned something like{code:java}hypervisors::virtual: vmwarehypervisors::cluster: vmware{code} The hypervisors fact is also being generated using the whereami library.However, the related virtual and is_virtual facts are being generated using virt-what.Which can lead to inconsistent results between the facts. I would be nicer if these related facts used whereami consistently.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3144) Hypervisors experimental fact improvements
Title: Message Title Patrick Grant created an issue Facter / FACT-3144 Hypervisors experimental fact improvements Issue Type: Improvement Assignee: Unassigned Created: 2022/09/05 3:05 AM Priority: Normal Reporter: Patrick Grant Info raised from a support customer: The info it (hypervisor experimental fact) provides at the moment isn't very useful. I wanted to provide some feedback in hopes of improving it in future versions. I use 2 hypervisors. openstack and vmware. At the moment. on openstack it returns "hypervisors::kvm::openstack: true" I would like to use it to provide a hiera source for openstack machines. Which is incovenient with that data format. I would find it more useful if it returned something like hypervisors::virtualisation: kvm hypervisors::cluster: openstack.
Jira (PUP-11508) Package collection triggers install
Title: Message Title Patrick Grant commented on PUP-11508 Re: Package collection triggers install nirupama This came up in our phoenix/support sync today as it's marked as needs information, what exactly is required here to progress this at the moment? 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.443888.164996258.35381.1653327840049%40Atlassian.JIRA.
Jira (PUP-11521) puppet-ca/v1/clean endpoint, only works when hitting the primary directly an not thorugh compilers
Title: Message Title Patrick Grant created an issue Puppet / PUP-11521 puppet-ca/v1/clean endpoint, only works when hitting the primary directly an not thorugh compilers Issue Type: Bug Assignee: Unassigned Created: 2022/04/25 10:39 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 7.12.1 Puppet Server Version: 7.4.2 A customer has stated that the puppet-ca/v1/clean endpoint only “works for them when talking directly to the primary, it doesn’t work when connecting via a PE Compiler, using the built-in proxy the compilers provide. Every other type of CA request proxies just fine, it’s just the newer clean endpoint.” Desired Behavior: can hit puppet-ca/v1/clean via a compiler Actual Behavior: Only works directly via primary Add Comment
Jira (PUP-11378) User resource difference in functionality between rhel 7 and 8
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11378 User resource difference in functionality between rhel 7 and 8 Change By: Patrick Grant Team: Night's Watch 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.427060.1639420066000.4391.1639420380092%40Atlassian.JIRA.
Jira (PUP-11378) User resource difference in functionality between rhel 7 and 8
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11378 User resource difference in functionality between rhel 7 and 8 Change By: Patrick Grant Zendesk Ticket Count: 1 Zendesk Ticket IDs: 46670 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.427060.1639420066000.4389.1639420320090%40Atlassian.JIRA.
Jira (PUP-11378) User resource difference in functionality between rhel 7 and 8
Title: Message Title
Patrick Grant updated an issue
Puppet / PUP-11378
User resource difference in functionality between rhel 7 and 8
Change By:
Patrick Grant
*Puppet version: 6.22.1 (PE Agent from PE 2019.8.6) * * Puppet Server Version: 6.15.3 * * OS Name/Version: rhel 7 and rhel 8*In this case, both systems have a local and domain user called administrator, in rhel 8 this results in corrective changes on each run as it tries to manage the domain user whereas this seems to be ignored on the rhel 7 box, and only the local user is managed.*Desired Behaviour:* Behaviour is consistent across OS versions. What that should be, I'm not exactly sure, should the local user take precedence in this case?*Actual Behaviour:* rhel 7, puppet only acts on the local user, rhel 8 has a corrective change on every run as it manages the domain administrator:{code:java}Dec 7 13:01:43 puppet-agent[18320]: (/Stage[main]/Profile::Base/User[administrator]/uid) change from 1553200500 to 1000 failed: Could not set uid on user[administrator]: Execution of '/usr/sbin/usermod -u 1000 administrator' returned 4: usermod: UID '1000' already exists (corrective){code}
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11378) User resource difference in functionality between rhel 7 and 8
Title: Message Title Patrick Grant created an issue Puppet / PUP-11378 User resource difference in functionality between rhel 7 and 8 Issue Type: Bug Assignee: Unassigned Created: 2021/12/13 10:27 AM Priority: Normal Reporter: Patrick Grant *Puppet version: 6.22.1 (PE Agent from PE 2019.8.6) Puppet Server Version: 6.15.3 OS Name/Version: rhel 7 and rhel 8* In this case, both systems have a local and domain user called administrator, in rhel 8 this results in corrective changes on each run as it tries to manage the domain user whereas this seems to be ignored on the rhel 7 box, and only the local user is managed. Desired Behaviour: Behaviour is consistent across OS versions. What that should be, I'm not exactly sure, should the local user take precedence in this case? Actual Behaviour: rhel 7, puppet only acts on the local user, rhel 8 has a corrective change on every run as it manages the domain administrator: Dec 7 13:01:43 puppet-agent[18320]: (/Stage[main]/Profile::Base/User[administrator]/uid) change from 1553200500 to 1000 failed: Could not set uid on user[administrator]: Execution of '/usr/sbin/usermod -u 1000 administrator' returned 4: usermod: UID '1000' already exists (corrective)
Jira (PUP-11190) User resource not removing password on AIX agents
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11190 User resource not removing password on AIX agents Change By: Patrick Grant CS Priority: Needs Priority Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408666.1627390115000.91160.1627390860033%40Atlassian.JIRA.
Jira (PUP-11190) User resource not removing password on AIX agents
Title: Message Title Patrick Grant updated an issue Puppet / PUP-11190 User resource not removing password on AIX agents Change By: Patrick Grant Summary: User resource not removing password on AIX agents Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.408666.1627390115000.91155.1627390560031%40Atlassian.JIRA.
Jira (PUP-11190) User resource not removing password on AIX
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-11190
User resource not removing password on AIX
Issue Type:
Bug
Affects Versions:
PUP 7.8.0
Assignee:
Unassigned
Created:
2021/07/27 5:48 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 7.8.0 Puppet Server Version: PE 2021.2 ( 7.2.0) OS Name/Version: AIX 7.2 when deleting a user with Puppet (User resource type), the password entry in /etc/security/passwd is not being cleaned up. Resource definition example:
user { 'saaddm':
ensure => 'absent',
managehome => true
}
Jira (FACT-3049) Reading the `/etc/resolv.conf` file for the domain value
Title: Message Title Patrick Grant commented on FACT-3049 Re: Reading the `/etc/resolv.conf` file for the domain value Going to close this ticket out at this point, it has been explained that facter will use /etc/resolv.conf only when DNS resolving fails. If we are missing any detail here, this can be reopened but for now there appears to be no issue. Thanks! Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401272.1622450814000.79416.1626173580043%40Atlassian.JIRA.
Jira (PUP-10820) Binary, Sensitive, etc deferred results can corrupt the transaction store
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10820 Binary, Sensitive, etc deferred results can corrupt the transaction store Change By: Patrick Grant CS Priority: Needs Priority Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380578.1607562201000.76966.1625746260037%40Atlassian.JIRA.
Jira (FACT-3049) Reading the `/etc/resolv.conf` file for the domain value
Title: Message Title Patrick Grant commented on FACT-3049 Re: Reading the `/etc/resolv.conf` file for the domain value Hi Paul Liong could you provide an update on our query above? Without this information it will be difficult to progress this ticket. Thank you. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401272.1622450814000.61966.1624358400112%40Atlassian.JIRA.
Jira (FACT-3049) Reading the `/etc/resolv.conf` file for the domain value
Title: Message Title Patrick Grant commented on FACT-3049 Re: Reading the `/etc/resolv.conf` file for the domain value Hi Paul Liong would it be possible to provide more detail here on how you would like this mechanism to work? At the moment it uses gethostname(), if this doesn't return anything it then searches the /etc/resolv.conf. How would you like this to operate to best suit your use case? If you can provide as much detail as possible, it will help us to see if a change is feasible. Thank you! Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401272.1622450814000.51043.1623149760033%40Atlassian.JIRA.
Jira (PUP-10781) If file resource content changes during puppet run, it uses original file checksum although content is retrieved several times
Title: Message Title Patrick Grant commented on PUP-10781 Re: If file resource content changes during puppet run, it uses original file checksum although content is retrieved several times Closing this in favor of PUP-3916, will add the support case there for traction 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.378054.1605178578000.80958.1605614580027%40Atlassian.JIRA.
Jira (PUP-10781) If file resource content changes during puppet run, it uses original file checksum although content is retrieved several times
Title: Message Title Patrick Grant created an issue Puppet / PUP-10781 If file resource content changes during puppet run, it uses original file checksum although content is retrieved several times Issue Type: Bug Assignee: Unassigned Created: 2020/11/12 2:56 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 6.17.0 Puppet Server Version: 6.12.1 OS Name/Version: Rhel7 If file resource content changes during a puppet run, although content of the file is retrieved several times, its continues to use the first retrievals checksum Steps from customer testing: Starting with empty file (checksum d41d8) 2020-11-05 12:57:34 +0100 Puppet (debug): HTTP GET https://testmaster:8140/puppet/v3/file_metadata/skv_files/bigfile?links=manage_type=md5_permissions=ignore=che_mini returned 200 OK 2020-11-05 12:57:34 +0100 Puppet (debug): Caching connection for https://testmaster:8140 2020-11-05 12:57:34 +0100 Puppet (debug): Using cached connection for https://testmaster:8140 2020-11-05 12:57:34 +0100 Puppet (debug): HTTP GET
Jira (PUP-10581) Puppet lookup --compile issues in PE2019.8
Title: Message Title Patrick Grant commented on PUP-10581 Re: Puppet lookup --compile issues in PE2019.8 Rob Braden Still no word back, I have just replied again but if I don't hear any word in a few days, the support ticket will have to be closed 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.365394.1594311475000.2787.1595924040088%40Atlassian.JIRA.
Jira (FACT-1575) Add the ability to cache and block the output of custom facts
Title: Message Title Patrick Grant commented on FACT-1575 Re: Add the ability to cache and block the output of custom facts Any update on my above query Dorin Pleava or even Maggie Dreyer? 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.176225.1487804791000.104001.1594315980142%40Atlassian.JIRA.
Jira (PUP-10581) Puppet lookup --compile issues in PE2019.8
Title: Message Title Patrick Grant created an issue Puppet / PUP-10581 Puppet lookup --compile issues in PE2019.8 Issue Type: Bug Affects Versions: PUP 6.16.0 Assignee: Unassigned Created: 2020/07/09 9:17 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 6.16 (PE 2019.8) Puppet Server Version: 6.12.0 *OS Name/Version:*RHEL 7 Customer is using the --compile flag with the `puppet lookup` command and they are receiving the following error: Error: Could not run: Could not retrieve resources from the PuppetDB at **hostname**:8140: [400 Bad Request] Malformed JSON for query: %5B%22and%22%2C%5B%22%3D%22%2C%22type%22%2C%22Host6%22%5D%2C%5B%22%3D%22%2C%22exported%22%2Ctrue%5D%2C%5B%22not%22%2C%5B%22%3D%22%2C%22certname%22%2C%22**hostname**%22%5D%5D%2C%5B%22%3D%22%2C%22tag%22%2C%22**hostname**%22%5D%5D This is a bit strange as the exported resources can be queried and returned from the db just fine. This was also working before upgrading to 2019.8 Desired Behavior: no errors relating to exported resources when using the --compile flag Actual Behavior: receiving the above 400 Bad Request] Malformed JSON
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant commented on PUP-10550 Re: rich_data enabled by default, error message is not informative and puppet should be able to process json report The customer was using a cached catalog on the agents. I have attached a catalog and stack trace, each with rich data enabled and disabled 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.364234.1593423699000.98209.1593526920022%40Atlassian.JIRA.
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10550 rich_data enabled by default, error message is not informative and puppet should be able to process json report Change By: Patrick Grant Attachment: int-lcanary-01.integrafin.net-RICHENABLED.json Attachment: agentdebug-RICHENABLED.txt Attachment: agentdebug-RICHDISABLED.txt Attachment: int-lcanary-01.integrafin.net-RICHDISABLED.json 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
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10550 rich_data enabled by default, error message is not informative and puppet should be able to process json report Change By: Patrick Grant CS Priority: Needs Priority 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.364234.1593423699000.97156.1593424080053%40Atlassian.JIRA.
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant commented on PUP-10550 Re: rich_data enabled by default, error message is not informative and puppet should be able to process json report Support ticket: https://puppetlabs.zendesk.com/agent/tickets/39780 from Integrated Financial Arrangements - UK, PE Standard 250 nodes. 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.364234.1593423699000.97155.1593423900027%40Atlassian.JIRA.
Jira (PUP-10550) rich_data enabled by default, error message is not informative and puppet should be able to process json report
Title: Message Title Patrick Grant created an issue Puppet / PUP-10550 rich_data enabled by default, error message is not informative and puppet should be able to process json report Issue Type: Bug Assignee: Unassigned Created: 2020/06/29 2:41 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 6.10.1 Puppet Server Version: 6.7.1 OS Name/Version: centos 7 rich_data is enabled by default (customer is on PE 2019.2.1), and it is causing the following error on a customers agents: Could not intern from rich_data_json: Internal Error: Puppet Context ':loaders' missing Desired Behavior: This is not a very informative error message and puppet should be able to process the json report Actual Behavior: All agent nodes are falling over with the above error, however we have been able to work around this by disabling rich_data Add Comment
Jira (PUP-10261) X-Hub-Signature check
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10261 X-Hub-Signature check Change By: Patrick Grant Zendesk Ticket IDs: 37914 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344469.1580475995000.7950.1580476320255%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10097 Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Change By: Patrick Grant 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.307.1571740260373%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant commented on PUP-9996 Re: Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Thanks Jarret, finally got another chance at a replication today and restarting the puppetserver solves this particular issue. As soon as I did, the correct error was presented, I will close the ticket. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.103925.1568825700434%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant updated an issue Puppet / PUP-9996 Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Change By: Patrick Grant Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.88497.1567772340106%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Patrick Grant Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323802.1567763238000.88495.1567771080276%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Patrick Grant updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Patrick Grant 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323802.1567763238000.88487.1567770360136%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant commented on PUP-9996 Re: Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Tested on PE 2019.1.0, (Puppet 6.4.2) Following my documented replication steps I was able to recreate. Following similar steps to TP's puppet apply replication, I could not. Both attempts are attached in 201910agenttest.txt 201910applytest.txt Seems to be more of an issue with puppet apply vs puppet agent from these replications and having spoken to Thomas Honey i've cloned this to the puppet project 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.84803.1567608360078%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9996
Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
201910agenttest.txt, 201910applytest.txt, ensure_resources.txt
Created:
2019/09/04 7:39 AM
Priority:
Normal
Reporter:
Patrick Grant
Basic Info Module Version: puppetlabs-stdlib (v6.0.0) Puppet Version: PE 2018, (5.5.14) OS Name/Version: RHEL 7 agent Replication... Install the inifile module (puppetlabs-inifile (v3.1.0)) on a Master and use the following test code to apply a file to my test agent:
class ensurerestest{
ensure_resources ('ini_setting', {'sample' => {'ensure' => 'present', 'path' => '/tmp/foo.ini', 'section' => 'bar', 'setting' => 'baz', 'value' => 'quux'}})
}
Jira (PUP-9962) stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers
Title: Message Title Patrick Grant moved an issue Puppet / PUP-9962 stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers Change By: Patrick Grant Component/s: stdlib Key: MODULES PUP - 9655 9962 Project: Modules Puppet 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319159.1564655694000.53093.1565692740213%40Atlassian.JIRA.
Jira (PUP-9939) Update the PQL Queries with clients own examples.
Title: Message Title Patrick Grant updated an issue Puppet / PUP-9939 Update the PQL Queries with clients own examples. Change By: Patrick Grant 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319938.1565184419000.46445.1565185020145%40Atlassian.JIRA.
Jira (PUP-9938) Puppet Agent is not a protected service.
Title: Message Title Patrick Grant updated an issue Puppet / PUP-9938 Puppet Agent is not a protected service. Change By: Patrick Grant 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319937.1565183931000.46442.1565184600171%40Atlassian.JIRA.
Jira (PUP-9912) Puppet Task formatting
Title: Message Title Patrick Grant updated an issue Puppet / PUP-9912 Puppet Task formatting Change By: Patrick Grant 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317444.1563815632000.26791.1563888660183%40Atlassian.JIRA.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Patrick Grant commented on PUP-1298 Re: manage_membership for unix groups provider Adding on behalf of behalf of customer: "Fundamentally, the request is to implement 'manages_members' in the 'groupadd' group provider. Based on the description from the 'groups' resource, this should be available, but this is not the case. While 'groupadd' group membership is defined in the group record, it is managed via the user resource. 1) May not be managed by puppet, such as a. Root, sys, or other OS-created users b. RPM-created users, such as the apache user c. Users federated by such features as ldap, sssd, or other centralized authentication 2) May not exist (yet) This is a level of configuration flexibility that is allowed by the underlying OS configuration, but cannot be expressed in Puppet." 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.4185.1557845400464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Patrick Grant updated an issue Puppet / PUP-1298 manage_membership for unix groups provider Change By: Patrick Grant 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.700.1557506580646%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9688
User resource sets password on every puppet agent run (Windows)
Issue Type:
Bug
Affects Versions:
PUP 5.5.10
Assignee:
Unassigned
Created:
2019/04/29 3:25 AM
Priority:
Normal
Reporter:
Patrick Grant
*Puppet Version: 5.5.10 *Puppet Server Version: 5.3.7 OS Name/Version: WIndows Server 2016 When using the following simple code to set the Administrator password on Windows:
$adminpassword = 'slkdhfl@#$slkW223'
if $adminpassword {
user { 'Administrator':
ensure => present,
password => $adminpassword,
Jira (PUP-9576) Puppet Catalog Command
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9576
Puppet Catalog Command
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/03/21 6:13 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: RHEL 7.5 Issue raised on behalf of a customer: In the documentation, it says "Retrieve the catalog for a node" for the command 'puppet catalog find' When the customer runs this from their master, then they only get the catalog of the master with some changes so it looks like it would be a catalog from the node specified by . The commands used were
puppet catalog find --terminus rest --environment production node.domain.org
{{}}
puppet catalog find --terminus rest --server > agent-catalog.json
{{}} I think here we either need to be more clear in our docs on how to use this command properly or if there is an issue here with the functionality then this needs to be resolved.
Jira (PUP-9464) Investigate different behavior of puppet resource vs puppet apply in resource titles
Title: Message Title Patrick Grant moved an issue Puppet / PUP-9464 Investigate different behavior of puppet resource vs puppet apply in resource titles Change By: Patrick Grant Key: MODULES PUP - 8522 9464 Project: Modules Puppet 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-9435) Windows - Group resource member parameter outputs an array of SID's instead of Names
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9435
Windows - Group resource member parameter outputs an array of SID's instead of Names
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/01/11 11:52 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 5.5.8 (PE 2018.1.5) Puppet Server Version: 5.3.6 OS Name/Version: Windows 2019 This ticket has arisen from a support case where the customer had noticed that a custom fact of theirs that used the group resource parameter member no longer worked after upgrading from PE 2018.1.3 to 2018.1.5. After a quick repro and speaking with some of the devs, this looks like a regression issue. In 2018.1.3, member outputs names and in 2018.1.5 SID's were outputted: 2018.1.3 (Puppet 5.5.3) Group resource:
group { 'Users':
ensure => 'present',
gid => 'S-1-5-32-545',
members => ['NT AUTHORITY\INTERACTIVE', 'NT AUTHORITY\Authenticated Users', 'PL2U24SBREN5JPS\sshd', 'PL2U24SBREN5JPS\cyg_server'],
Jira (PUP-9293) read_wide_string hides errors if the string is nil
Title: Message Title
Patrick Grant updated an issue
Puppet / PUP-9293
read_wide_string hides errors if the string is nil
Change By:
Patrick Grant
*Puppet Version:* Unknown 5.5.2 (PE 2018.1.2 Master & Agent) *Puppet Server Version:* N/A*OS Name/Version:* Windows Server 2012r2 As part of [ https://puppetlabs.zendesk.com/agent/tickets/32364 ] it was found that there was a bug in the error handler in the read_wide_string method ( [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/api_types.rb#L56-L63 ] )Where if {{str}} is nil then an error is raised during the debug statement and raises the wrong error. Instead the Puppet.debug statement should never error and raise the real error
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
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Patrick Grant assigned an issue to Paul Showalter Puppet / PUP-7638 `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Change By: Patrick Grant Assignee: Patrick Grant Paul Showalter 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-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title Patrick Grant assigned an issue to Patrick Grant Puppet / PUP-7638 `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Change By: Patrick Grant Assignee: Paul Showalter Patrick Grant 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-8658) Feature Request : Reports not sent due to error get sent at a later time
Title: Message Title Patrick Grant created an issue Puppet / PUP-8658 Feature Request : Reports not sent due to error get sent at a later time Issue Type: New Feature Assignee: Unassigned Created: 2018/04/11 9:52 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 5.3.5 Puppet Server Version: 5.1.6 ** This feature request arose from a support ticket where the customer has experienced the following error from the puppet agent: "Error: Could not send report: Connection reset by peer" The customer would like if Puppet tried to send these reports at a later time, for example, before the next run, at the beginning of the next run or save them until they do get sent. Add Comment This message was
Jira (PUP-8651) Augeas unknown error - Matching path expression
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-8651
Augeas unknown error - Matching path _expression_
Issue Type:
Bug
Affects Versions:
PUP 4.10.9
Assignee:
Unassigned
Created:
2018/04/10 7:52 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 4.10.9 Puppet Server Version: 2.6.0 OS Name/Version: AIX 7.1 This issue arose from a support ticket where a customer experiences the following error during a puppet run on one of their AIX servers.
Debug: Augeas[sshd_config](provider=augeas): Opening augeas with root /, lens path , flags 32
Debug: Augeas[sshd_config](provider=augeas): Augeas version 1.4.0 is installed
Debug: Augeas[sshd_config](provider=augeas): Closed the augeas connection
Error: /Stage[main]/Profiles::Pci_dss::Sshd_config/Augeas[sshd_config]: Could not evaluate: unknown error - Matching path _expression_ '/augeas/load/*['/etc/ssh/sshd_config/' !~ glob(incl) + regexp('/.*')]' failed
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title
Patrick Grant updated an issue
Puppet / PUP-8611
Crontab gets erased after error during agent run
Change By:
Patrick Grant
*OS Name/Version: PE Master/Agent Version 2016.4.2 / Master RHEL 6.9 / Agent AIX 7.1*Customer experienced high utilization of paging space on his agent which caused the following error during a puppet run: {code:java} Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty{code}After the error occurred the customer's crontab was wiped and it left only the following: {code:java} # HEADER: This file was autogenerated at 2017-11-09 13:20:05 -0500 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. {code}Another agent run after the paging problems were fixed did not resolve the crontab and it had to be restored from a backup. After the file was present, subsequent puppet runs now correct the crontab entries. *Desired Behavior:* When the error below occurs, crontab should not be wiped and should be left as is{code:java} Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty{code}*Actual Behavior:* Crontab gets completely wiped when the error occurs during a puppet run.
Add Comment
This message was sent by Atlassian
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Patrick Grant created an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Issue Type: Bug Assignee: Unassigned Created: 2018/03/28 3:20 AM Priority: Normal Reporter: Patrick Grant OS Name/Version: PE Master/Agent Version 2016.4.2 / Master RHEL 6.9 / Agent AIX 7.1 Customer experienced high utilization of paging space on his agent which caused the following error during a puppet run: Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty After the error occurred the customer's crontab was wiped and it left only the following: # HEADER: This file was autogenerated at 2017-11-09 13:20:05 -0500 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that
Jira (PUP-8551) Error 500 response received for request for classes in production.
Title: Message Title Patrick Grant created an issue Puppet / PUP-8551 Error 500 response received for request for classes in production. Issue Type: Bug Assignee: Unassigned Attachments: console-services .log, puppetserver.log.gz Created: 2018/03/15 4:42 AM Priority: Normal Reporter: Patrick Grant Puppet Version: 2016.4.0 Puppet Server Version: 2016.4.0.1005 OS Name/Version: Oracle Linux 7.0 A customer's puppet agents were not getting updated with classes during puppet runs. This occurred after code changes which have not yet been specified. We believe this to be associated with a bug where a class parameter has no type info and this may have been fixed in a later version of 2016.4.x but with no specifics, we haven't been able to replicate yet. Attached are the console services log and the puppet server log with debug level logging. Console services log outputs the following error: 2018-03-14 14:40:29,343 [qtp909839951-3205] INFO [p.c.class-updater] Requesting classes in production from https://iumg106.in.audi.vwg:8140/puppet/v3/environment_classes?environment=production 2018-03-14 14:40:32,585 [qtp909839951-3205] ERROR [p.c.class-updater] 500 response received for request for classes in production.
Jira (PUP-7969) debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes'
Title: Message Title Patrick Grant assigned an issue to Unassigned Puppet / PUP-7969 debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes' Change By: Patrick Grant Assignee: Patrick Grant 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-7969) debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes'
Title: Message Title
Patrick Grant commented on PUP-7969
Re: debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes'
Had a quick look at this one during puppethack. So, lib/puppet/type.rb lines 1540 & 1545 is where this is written to debug:
self.debug{"subscribes to #{related_resource.ref}"}
"subscribes to" has just been hardcoded and I'd bet that this issue occurs for the other meta parameters (before, require) as well and not just notify.
I'm going to unassign this ticket from myself as it's a little out of my comfort zone not knowing too much Ruby but to fix I would do a check on which metaparameter is used and based on that, interpolate either "before", "requires ", "notifies" or "subscribes to" into the start of the debug string.
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-7969) debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes'
Title: Message Title Patrick Grant assigned an issue to Patrick Grant Puppet / PUP-7969 debug message for notify relationship is inaccurate - should be 'notifies' not 'subscribes' Change By: Patrick Grant Assignee: Patrick Grant 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-8145) Spaces in file resource paths break filebucket
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-8145
Spaces in file resource paths break filebucket
Issue Type:
Bug
Affects Versions:
PUP 5.3.2
Assignee:
Unassigned
Created:
2017/11/10 8:44 AM
Priority:
Normal
Reporter:
Patrick Grant
When backing up a file resource to filebucket where the file path contains spaces, see manifest snippit:
class space {
file { 'C:\Test space\space.txt':
ensure => 'file',
