Jira (PUP-11526) Evaluate deferred functions lazily by default
Title: Message Title Josh Cooper created an issue Puppet / PUP-11526 Evaluate deferred functions lazily by default Issue Type: Bug Assignee: Unassigned Created: 2022/04/27 7:35 PM Fix Versions: PUP 8.0.0 Priority: Normal Reporter: Josh Cooper This is a follow up to PUP-9323 so that deferred functions are evaluated lazily by default. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5483) PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10
Title: Message Title Jon-Paul Lindquist commented on PDB-5483 Re: PuppetDB ERROR: cannot set transaction read-write mode during recovery After Upgrade to 7.10 Did some more testing, and it seems like the session set was the original intention, so I put this together in hopes that it helps https://github.com/puppetlabs/puppetdb/pull/3670 (Hopefully that's formatted properly and everything). I am not terribly familiar with the clojure language again), but I made an attempt -bash-4.2$ psql -d puppetdb psql (14.2) Type "help" for help. puppetdb=# \x Expanded display is on. puppetdb=# select * from pg_settings where name = 'jit'; -[ RECORD 1 ]---+- name | jit setting | on unit | category | Query Tuning / Other Planner Options short_desc | Allow JIT compilation.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-11522 Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store' Change By: Josh Cooper Assignee: Josh Cooper 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.444827.1650996743000.19304.1651102140059%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Josh Cooper updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Josh Cooper Fix Version/s: FACT 4.2.10 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.444890.1651054037000.19264.1651098660264%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Josh Cooper commented on FACT-3117 Re: Azure metadata not fetching tags An earlier version of the 3rd party module used to call the 2018-04-02 version of the API and convert the "tags" as reported by Azure into a Hash: https://github.com/keirans/azuremetadata/blob/02e18bff84783f11f15cc8f94c0f734fca950fe6/lib/facter/azure_metadata.rb#L22-L23 The module was modified to call a newer version of the API and the tag parsing wasn't preserved. See https://github.com/keirans/azuremetadata/commit/1e5668fba79195a2904dd8ee64391cb208d7ba1f#diff-7c55f6f5e9b2f257c6ea24ca9e84d192f9a2689045474d0ec14f45cf2bf7df85L19-L24 The author explicitly states that this in intentional and 0.2.0 is a breaking change. See https://github.com/keirans/azuremetadata#api-version-pinned-to-2020-06-01 You should use the tagsList value instead which is native functionaly. As a result, 0.2.0 is a breaking change for previous users. This native approach also gracefully handles special characters in tag keys and values unlike previous versions of the module. For example, from the Azure docs: "The tags field is a string with the tags delimited by semicolons. This output can be a problem if semicolons are used in the tags themselves." Facter 4 does not claim to maintain compatibility with the old version of the module, so the customer should either use the old version of the module or create a separate custom fact to convert the "az_metadata.compute.tagsList" Array into a Hash. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title Aria Li assigned an issue to Aria Li Puppet / PUP-11472 Legacy function error does not include the source ref Change By: Aria Li Assignee: Aria Li 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.437580.1646090265000.19256.1651098120051%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Josh Cooper commented on FACT-3117 Re: Azure metadata not fetching tags Ah facter 3 and 4 use slightly different API versions https://github.com/keirans/azuremetadata/blob/f641e94340771b1873c0cbca27b035f278399493/lib/facter/azure_metadata.rb#L20 https://github.com/puppetlabs/facter/blob/3e5715ac88fd8cf2a0fe69a57d7f2b62f461bc21/lib/facter/resolvers/az.rb#L8 Also the Azure API docs say "The tags field is a string with the tags delimited by semicolons." so I don't believe tags have ever been collected in the way the customer is wanting. See https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service?tabs=linux#sample-3-get-vm-tags There is a "tagsList" option make JSON parsing easier. 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.444890.1651054037000.18985.1651081800041%40Atlassian.JIRA.
Jira (PUP-11525) 17. Update Public-facing Puppet docs to include macOS 12 (M1)
Title: Message Title Josh Cooper created an issue Puppet / PUP-11525 17. Update Public-facing Puppet docs to include macOS 12 (M1) Issue Type: Task Assignee: Unassigned Created: 2022/04/27 10:44 AM Labels: os Priority: Normal Reporter: Josh Cooper Update Public-facing Puppet docs to include this platform This ticket will be set with the fix version of the first release containing the new platform and checked with doc team during the Platform release process. Add Comment This message was sent by
Jira (PUP-11525) 17. Update Public-facing Puppet docs to include macOS 12 (M1)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11525 17. Update Public-facing Puppet docs to include macOS 12 (M1) Change By: Josh Cooper Epic Link: PA-4457 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.444943.1651081481000.18964.1651081500200%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11522 Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store' Change By: Josh Cooper Acceptance Criteria: create_context and load_context methods should behave like create_system_context wrt the include system_store include_system_store parameter and ssl_trust_store config path settingWhen using the http client in puppet it should be possible to connect to a https server that requires client certs and who's whose server cert issues is issued by a third party CAEg. should be possible to call post(url, include system_store include_system_store: true) and connect to server described above 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.444827.1650996743000.18777.1651078680092%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title Josh Cooper commented on PUP-11522 Re: Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store' Yeah jarret.lavallee that's correct. The use case for "create_system_context" is when the agent is bootstrapping itself and has a CA & CRL, but doesn't yet have a client cert. For example, when submitting its CSR. The HTTP client will be updated as part of this ticket to no longer call "create_system_context". 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.444827.1650996743000.18775.1651078620049%40Atlassian.JIRA.
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11472
Legacy function error does not include the source ref
Change By:
Josh Cooper
*Puppet Version:* main*Desired Behavior:*Legacy function errors should include the source path. For example, if you have a 3x function in module, like "$codedir/environments/production/modules/sample/lib/puppet/parser/functions/sample.rb" containing:{code:ruby}module Puppet::Parser::Functions newfunction(:sample, :type => :rvalue, :doc => <<-EOSA function using the 3x API EOS ) do |arguments|"the returned value" end def method_here_is_illegal() endend{code}Then puppet should return the filename where the legacy function is defined. See PUP-9294 and https://puppet.com/docs/puppet/5.5/functions_legacy.html for information about legacy (3x) function errors.For example , the following should indicate the path and line number of the legacy function :{noformat}$ bundle exec puppet apply -e 'notice(sample(""))' {noformat} *Actual Behavior:*No source path is included, e.g.{noformat}ruby_legacy_function_instantiator.rb:97:in `walk': Illegal method definition of method 'initialize' on line 8 in legacy function. See https://puppet.com/docs/puppet/latest/functions_refactor_legacy.html for more information (SecurityError) {noformat}
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11472 Legacy function error does not include the source ref Change By: Josh Cooper Community Contributors: lollipopman 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.437580.1646090265000.18690.1651077180109%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title
Jarret Lavallee commented on PUP-11522
Re: Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
The problem with {{post(url, options: { include_system_store } )}} is that it uses the system SSL context, which does include the CA certs in Puppet[:ssl_trust_store], but does not include the client certificates. https://github.com/puppetlabs/puppet/blob/main/lib/puppet/http/client.rb#L461-L470 As a part of this, the HTTP::Client will probably need to be updated to use create_context or load_context with the include_system_store and ssl_trust_store options that are added/modified. Is there a use case for using the system context and not the client context within HTTP::Client?
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.444827.1650996743000.18688.1651077120034%40Atlassian.JIRA.
Jira (PUP-11472) Legacy function error does not include the source ref
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11472
Legacy function error does not include the source ref
Change By:
Josh Cooper
*Puppet Version:* main*Desired Behavior:*Legacy function errors would should include the source path . For example, if you have a 3x function in module, like "$codedir/environments/production/modules/sample/lib/puppet/parser/functions/sample.rb" containing: {code:ruby}module Puppet::Parser::Functions newfunction(:sample, :type => :rvalue, :doc => <<-EOSA function using the 3x API EOS ) do |arguments|"the returned value" end def method_here_is_illegal() endend{code}Then puppet should return the filename where the legacy function is defined. See PUP-9294 and https://puppet.com/docs/puppet/5.5/functions_legacy.html for information about legacy (3x) function errors.For example:{noformat}$ bundle exec puppet apply -e 'notice(sample(""))' *Actual Behavior:*No source path is included, e.g. {noformat}ruby_legacy_function_instantiator.rb:97:in `walk': Illegal method definition of method 'initialize' on line 8 in legacy function. See https://puppet.com/docs/puppet/latest/functions_refactor_legacy.html for more information (SecurityError){noformat}
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-1557) Extend "cloud" fact to Google Compute Engine
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-1557 Extend "cloud" fact to Google Compute Engine Change By: Nirupama Mantha Sprint: Phoenix 2022-05- 11 25 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.168608.148349210.18674.1651075620125%40Atlassian.JIRA.
Jira (FACT-3113) Locale bug with Facter 4
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-3113 Locale bug with Facter 4 Change By: Nirupama Mantha Sprint: Phoenix 2022-05- 11 25 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.56.1650473576000.18673.1651075620057%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Michael Hashizume updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Michael Hashizume Sprint: Phoenix 2022-05-11 Team: Phoenix 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.444890.1651054037000.18672.1651075440047%40Atlassian.JIRA.
Jira (PUP-11518) Update the type system to handle deferred functions
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11518 Update the type system to handle deferred functions Change By: Nirupama Mantha Summary: [SPIKE] update Update the type system to handle deferred functions 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.443425.1649776248000.18670.1651075380029%40Atlassian.JIRA.
Jira (PUP-11518) [SPIKE] update the type system to handle deferred functions
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11518 [SPIKE] update the type system to handle deferred functions Change By: Nirupama Mantha Acceptance Criteria: Compilations don't error with deferred functions 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.443425.1649776248000.18669.1651075320080%40Atlassian.JIRA.
Jira (PUP-11518) [SPIKE] update the type system to handle deferred functions
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11518 [SPIKE] update the type system to handle deferred functions Change By: Nirupama Mantha Sprint: Froyo - 4/27/ Phoenix 2022 -05-11 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.443425.1649776248000.18667.1651075260040%40Atlassian.JIRA.
Jira (PUP-11518) [SPIKE] update the type system to handle deferred functions
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11518 [SPIKE] update the type system to handle deferred functions Change By: Nirupama Mantha Team: Froyo Phoenix 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.443425.1649776248000.18666.1651075200144%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Nirupama Mantha Fix Version/s: FACT 4.2.10 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.444890.1651054037000.18662.1651075020037%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Nirupama Mantha Story Points: 3 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.444890.1651054037000.18661.1651074960146%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Nirupama Mantha Acceptance Criteria: Can retrieve tags from azure metadata facts and use that in a Hiera configuration 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.444890.1651054037000.18658.1651074900038%40Atlassian.JIRA.
Jira (PUP-9323) Resolve Deferred values on demand instead of at catalog read time
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-9323 Resolve Deferred values on demand instead of at catalog read time Change By: Nirupama Mantha Acceptance Criteria: Install the dependencies needed for a deferred function and call the deferred function in the same run.The current behavior should be preserved by default, the new behavior can be turned on with a configuration. 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.285576.154262828.18623.165107447%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11522 Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store' Change By: Nirupama Mantha Acceptance Criteria: create_context and load_context methods should behave like create_system_context wrt the include system_store parameter and ssl_trust_store config path settingWhen using the http client in puppet it should be possible to connect to a https server that requires client certs and who's server cert issues by a third party CAEg. should be possible to call post(url, include system_store true) and connect to server described above 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.444827.1650996743000.18613.1651073700112%40Atlassian.JIRA.
Jira (PUP-11498) Send release announcement (Puppet Platform 7.16.0)
Title: Message Title Alex Rodriguez assigned an issue to Alex Rodriguez Puppet / PUP-11498 Send release announcement (Puppet Platform 7.16.0) Change By: Alex Rodriguez Assignee: Alex Rodriguez 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.442359.1648659517000.18604.1651073340141%40Atlassian.JIRA.
Jira (FACT-3109) Failed to get networking information: "\xE5" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE
Title: Message Title Nirupama Mantha updated an issue Facter / FACT-3109 Failed to get networking information: "\xE5" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE Change By: Nirupama Mantha Fix Version/s: FACT 4.2.10 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.438363.1646388745000.18588.1651073100036%40Atlassian.JIRA.
Jira (PUP-11488) Send release announcement (Puppet Platform 6.27.0)
Title: Message Title Alex Rodriguez assigned an issue to Alex Rodriguez Puppet / PUP-11488 Send release announcement (Puppet Platform 6.27.0) Change By: Alex Rodriguez Assignee: Alex Rodriguez 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.442324.1648659194000.18578.1651072920040%40Atlassian.JIRA.
Jira (FACT-3115) virt-what-1.22-1 changes virtual=kvm to virtual=redhat
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Facter / FACT-3115 virt-what-1.22-1 changes virtual=kvm to virtual=redhat Change By: Michael Hashizume Assignee: Michael Hashizume 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.444600.1650614566000.18577.1651072380517%40Atlassian.JIRA.
Jira (FACT-3115) virt-what-1.22-1 changes virtual=kvm to virtual=redhat
Title: Message Title Michael Hashizume updated an issue Facter / FACT-3115 virt-what-1.22-1 changes virtual=kvm to virtual=redhat Change By: Michael Hashizume Sprint: Phoenix 2022-05-11 Team: Phoenix 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.444600.1650614566000.18576.1651072380470%40Atlassian.JIRA.
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-11524) Manifest to install Grafana Agent
Title: Message Title Nagendra K updated an issue Puppet / PUP-11524 Manifest to install Grafana Agent Change By: Nagendra K I am new to puppet. I am trying to create a manifest to install grafana-agent in ubuntu VM. I downloaded grafana-agent deb file and included in manifest file as a source. But getting the following error.!image-2022-04-27-18-27-34-499.png! Please help me creating the manifest . that installs grafana-agent in ubuntu vm 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.444894.1651064294000.18500.1651064460051%40Atlassian.JIRA.
Jira (PUP-11524) Manifest to install Grafana Agent
Title: Message Title Nagendra K created an issue Puppet / PUP-11524 Manifest to install Grafana Agent Issue Type: Story Assignee: Unassigned Attachments: image-2022-04-27-18-27-34-499.png Created: 2022/04/27 5:58 AM Priority: Critical Reporter: Nagendra K I am new to puppet. I am trying to create a manifest to install grafana-agent in ubuntu VM. I downloaded grafana-agent deb file and included in manifest file as a source. But getting the following error. Please help me creating the manifest. Add Comment
Jira (PUP-11524) Manifest to install Grafana Agent
Title: Message Title Nagendra K updated an issue Puppet / PUP-11524 Manifest to install Grafana Agent Change By: Nagendra K Issue Type: Story Task 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.444894.1651064294000.18497.1651064340158%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title
Jordi Garcia updated an issue
Facter / FACT-3117
Azure metadata not fetching tags
Change By:
Jordi Garcia
After migration from 2019.8.9 to 2021.5.0 the customer removed `keirans/azuremetadata` module and started to use default puppet for fetching az_metadata.After the upgrade the agent runs are coming across the following error: {code:java} Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Data Provider type mismatch: Got String when a hash-like object was expected to access value using 'environment' from key 'facts.az_metadata.compute.tags.environment' on node{code} The customer has implemented the following code in `hiera.yaml`: --- — version: 5 defaults: datadir: data data_hash: yaml_data hierarchy: - name: "Per-node data (eyaml version)" globs: - "per_role/%\{facts.az_metadata.compute.tags.environment}/%\{trusted.extensions.pp_role}.yaml" - "per_region/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.application}/*.yaml" - "per_region/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/*.yaml" - "secrets/%\{facts.az_metadata.compute.tags.environment}/*.yaml" - "secrets/*.yaml" - "per_environment/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.application}/*.yaml" - "per_environment/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_os/%\{facts.os.name}.yaml"
Add Comment
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title
Jordi Garcia updated an issue
Facter / FACT-3117
Azure metadata not fetching tags
Change By:
Jordi Garcia
After migration from 2019.8.9 to 2021.5.0 the customer removed `keirans/azuremetadata` module and started to use default puppet for fetching az_metadata.After the upgrade the agent runs are coming across the following error: {code:java} ~ Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Data Provider type mismatch: Got String when a hash-like object was expected to access value using 'environment' from key 'facts.az_metadata.compute.tags.environment' on node{code} The customer has implemented the following code in `hiera.yaml`: ---version: 5 defaults: datadir: data data_hash: yaml_data hierarchy: - name: "Per-node data (eyaml version)" globs: - "per_role/%\{facts.az_metadata.compute.tags.environment}/%\{trusted.extensions.pp_role}.yaml" - "per_region/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.application}/ * Please see Zendesk Support tab for further comments and attachments . ~ yaml" - "per_region/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/*.yaml" - "secrets/%\{facts.az_metadata.compute.tags.environment}/*.yaml" - "secrets/*.yaml" - "per_environment/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.application}/*.yaml" - "per_environment/%\{facts.az_metadata.compute.tags.environment}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/%\{facts.az_metadata.compute.location}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.application}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_service/%\{facts.az_metadata.compute.tags.service}/%\{facts.az_metadata.compute.tags.environment}.yaml" - "per_os/%\{facts.os.name}.yaml"
Add Comment
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Alvin Rodis updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Alvin Rodis Zendesk Ticket Count: 1 Zendesk Ticket IDs: 48158 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.444890.1651054037000.18468.1651054080158%40Atlassian.JIRA.
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Jordi Garcia created an issue Facter / FACT-3117 Azure metadata not fetching tags Issue Type: Bug Assignee: Unassigned Created: 2022/04/27 3:07 AM Priority: Normal Reporter: Jordi Garcia After migration from 2019.8.9 to 2021.5.0 the customer removed `keirans/azuremetadata` module and started to use default puppet for fetching az_metadata. After the upgrade the agent runs are coming across the following error: * Please see Zendesk Support tab for further comments and attachments. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (FACT-3117) Azure metadata not fetching tags
Title: Message Title Alvin Rodis updated an issue Facter / FACT-3117 Azure metadata not fetching tags Change By: Alvin Rodis Labels: jira_escalated 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.444890.1651054037000.18469.1651054080205%40Atlassian.JIRA.
