Jira (PUP-10650) Remove TypeSetType from RichData
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10650
Remove TypeSetType from RichData
Change By:
Josh Cooper
The {{PTypeSetType}} class defines a namespace for a set of PCore types. Internally puppet uses {{PTypeSetType}} when registering all of the AST model classes. See{{Puppet::Pops::Mode.register_pcore_types}}. At one point we considered serializing type information, for example the catalog could contain all of the rich data and the type information needed by the receiver to deserialize. However, the type information was too verbose. So when serializing, we just send the type names, e.g. {{Sensitive}}, and assume the receiver knows how to deserialize.Commit [0a195ef6d6|https://github.com/puppetlabs/puppet/commit/0a195ef6d6] defined {{RichData}} as:{code:ruby}Variant[Scalar,SemVerRange,Binary,Sensitive,Type,TypeSet,Undef,Hash[RichDataKey,RichData],Array[RichData]]{code}The {{TypeSet}} above refers to the {{PTypeSetType}} class. The commit also changed the lookup {{DataProvider}} to accept all {{RichData}}. However, lookup also validates that the data it receives from the data provider contains only {{RichData}}. As a result, puppet could perform full type interference on the entire hash. That was optimized in PUP-10628, but it's based on a heuristic, detecting if the {{pcore_version}} key exists. There's no reason currently to include {{TypeSet}} in {{RichData}}, so we should remove that to avoid performance issues.
Add Comment
This message was sent by Atlassian Jira
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting when using server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting when using server_list Change By: Josh Cooper Team: Coremunity 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.370505.1598545662000.25771.1598572020041%40Atlassian.JIRA.
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting when using server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting when using server_list Change By: Josh Cooper Summary: puppet 6 agent doesn't honor usecacheonfailure setting when using server_list 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.370505.1598545662000.25770.1598571960168%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Rank: 2 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.214573.1507141532000.25765.1598571900040%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Priority: Major 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.214573.1507141532000.25766.1598571900225%40Atlassian.JIRA.
Jira (PUP-10650) Remove TypeSetType from RichData
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10650
Remove TypeSetType from RichData
Change By:
Josh Cooper
The {{PTypeSetType}} class defines a namespace for a set of PCore types. Internally puppet uses {{PTypeSetType}} when registering all of the AST model classes. See{{Puppet::Pops::Mode.register_pcore_types}}. At one point we considered serializing type information, for example the catalog could contain all of the rich data and the type information needed by the receiver to deserialize. However, the type information was too verbose. So when serializing, we just send the type names, e.g. {{Sensitive}}, and assume the receiver knows how to deserialize.Commit [ 0a195ef6d6 |https://github.com/puppetlabs/puppet/commit/0a195ef6d6] defined {{RichData}} as:{code:ruby}Variant[Scalar,SemVerRange,Binary,Sensitive,Type,TypeSet,Undef,Hash[RichDataKey,RichData],Array[RichData]]{code}The {{TypeSet}} above refers to the {{PTypeSetType}} class. The commit also changed the lookup {{DataProvider}} to accept all {{RichData}}. However, lookup also validates that the data it receives from the data provider contains only {{RichData}}. As a result, puppet could perform full type interference on the entire hash. That was optimized in PUP-10628, but it's based on a heuristic, detecting if the {{pcore_version}} key exists. There's no reason currently to include {{TypeSet}} in {{RichData}}, so we should remove that to avoid performance issues.
Add Comment
This message was sent by Atlassian Jira
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10628 Performance regression with large hashes using lookup Change By: Josh Cooper Sprint: Platform Core KANBAN 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.369684.1597848926000.25679.1598569800038%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10628 Performance regression with large hashes using lookup Change By: Josh Cooper Assignee: Josh Cooper 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.369684.1597848926000.25677.1598569740027%40Atlassian.JIRA.
Jira (PUP-10650) Remove TypeSetType from RichData
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10650 Remove TypeSetType from RichData Change By: Josh Cooper Labels: platform_7 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.370572.1598569423000.25676.1598569440183%40Atlassian.JIRA.
Jira (PUP-9577) Large numbers of facts cause slow performance
Title: Message Title Justin Stoller commented on PUP-9577 Re: Large numbers of facts cause slow performance FWIW, I think users can avoid this situation by writing EPP templates vs ERB ones. Ruby, afaict, does not provide a hook for instance variable look up like it does for method_missing so there's nothing to do if users reference @variable names besides preloading all possible instance variables. It would be possible to gate preloading facts as instance variables on a new setting, but users would need to validate that their ERB templates only use the other ways of accessing facts eg scope['variable']. At that point, though, I'm not sure if it wouldn't be better to encourage them to move to EPP? 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.301092.1553181872000.25673.1598569440087%40Atlassian.JIRA.
Jira (PUP-10650) Remove TypeSetType from RichData
Title: Message Title Josh Cooper created an issue Puppet / PUP-10650 Remove TypeSetType from RichData Issue Type: Task Assignee: Unassigned Created: 2020/08/27 4:03 PM Priority: Normal Reporter: Josh Cooper The PTypeSetType class defines a namespace for a set of PCore types. Internally puppet uses PTypeSetType when registering all of the AST model classes. See Puppet::Pops::Mode.register_pcore_types. At one point we considered serializing type information, for example the catalog could contain all of the rich data and the type information needed by the receiver to deserialize. However, the type information was too verbose. So when serializing, we just send the type names, e.g. Sensitive, and assume the receiver knows how to deserialize. Commit 0a195ef6d6 defined RichData as: Variant[Scalar,SemVerRange,Binary,Sensitive,Type,TypeSet,Undef,Hash[RichDataKey,RichData],Array[RichData]] The TypeSet above refers to the PTypeSetType class. The commit also changed the lookup DataProvider to accept all RichData. However, lookup also validates that the data it receives from the data provider contains only RichData. As a result, puppet could perform full type interference on the entire hash. That was optimized in PUP-10628, but it's based on a heuristic, detecting if the pcore_version key exists. There's no reason currently to include TypeSet in RichData, so we should remove that to avoid performance issues.
Jira (PUP-10650) Remove TypeSetType from RichData
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10650 Remove TypeSetType from RichData Change By: Josh Cooper Fix Version/s: PUP 7.0.0 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.370572.1598569423000.25675.1598569440135%40Atlassian.JIRA.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Henrik Lindberg commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates Josh Cooper EPP results in AST elements specific to EPP for rendering a value as a string. That evaluation could evaluate the _expression_, check if the result is a Sensitive, and then instead of getting a REDACTED result it would unwrap the sensitive value and turn that into a string. It would then need to communicate the the top level that the entire result should be wrapped in a Sensitive. The passing back of that value is the most difficult as it needs to handle nesting (one EPP could call another for example). Well - you managed to nerd snipe me The relevant parts is in the `evaluator_impl.rb` def eval_EppExpression(o, scope) scope["@epp"] = [] evaluate(o.body, scope) result = scope["@epp"].join result end def eval_RenderStringExpression(o, scope) scope["@epp"] << o.value.dup nil end
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper commented on PUP-10628 Re: Performance regression with large hashes using lookup I modified TypeSetType#instance? so inference is skipped if the object isn't a hash or if the pcore_version key is missing. The was merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/d00f2a6a23f6a98daf2b954aea2e1bf01c020c17. I'm going to file a separate ticket to remove TypeSetType from RichData to be fixed in Puppet 7. 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.369684.1597848926000.25634.1598568780053%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10628 Performance regression with large hashes using lookup Change By: Josh Cooper Team: Coremunity 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.369684.1597848926000.25635.1598568780096%40Atlassian.JIRA.
Jira (PUP-10628) Performance regression with large hashes using lookup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10628 Performance regression with large hashes using lookup Change By: Josh Cooper Fix Version/s: PUP 6.19.0 Fix Version/s: PUP 5.5.22 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.369684.1597848926000.25636.1598568780139%40Atlassian.JIRA.
Jira (PDB-4730) Update PDB terminus to use puppet's http client
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4730 Update PDB terminus to use puppet's http client Change By: Josh Cooper Labels: platform_7 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.358737.1589402469000.25535.1598564280031%40Atlassian.JIRA.
Jira (PUP-10535) Move to Addressable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10535 Move to Addressable Change By: Josh Cooper Team: Coremunity 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.360343.1590685774000.25429.1598557440043%40Atlassian.JIRA.
Jira (PUP-10601) Only create pcore resource type loaders for compilation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10601 Only create pcore resource type loaders for compilation Change By: Josh Cooper Team: Coremunity 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.367414.1595884476000.25430.1598557440087%40Atlassian.JIRA.
Jira (PUP-9696) Cannot use URIs that require escaping after interpolation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9696 Cannot use URIs that require escaping after interpolation Change By: Josh Cooper Epic Link: PUP- 9120 10649 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.301445.155353411.25425.1598557380060%40Atlassian.JIRA.
Jira (PUP-10535) Move to Addressable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10535 Move to Addressable Change By: Josh Cooper Epic Link: PUP-10649 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.360343.1590685774000.25428.1598557380191%40Atlassian.JIRA.
Jira (PUP-10492) Handle special characters in http(s) source URLs
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10492 Handle special characters in http(s) source URLs Change By: Josh Cooper Epic Link: PUP- 9120 10649 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.357751.1588723848000.25426.1598557380104%40Atlassian.JIRA.
Jira (PUP-10613) Puppet::Util.uri_encode discards '='
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10613 Puppet::Util.uri_encode discards '=' Change By: Josh Cooper Epic Link: PUP-10649 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.368658.1596844155000.25427.1598557380147%40Atlassian.JIRA.
Jira (PUP-10649) URL Encoding
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10649 URL Encoding Change By: Josh Cooper Labels: platform_7 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.370523.1598557297000.25424.1598557320168%40Atlassian.JIRA.
Jira (PUP-10649) URL Encoding
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10649 URL Encoding Change By: Josh Cooper Fix Version/s: PUP 7.0.0 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.370523.1598557297000.25423.1598557320123%40Atlassian.JIRA.
Jira (PUP-10649) URL Encoding
Title: Message Title Josh Cooper created an issue Puppet / PUP-10649 URL Encoding Issue Type: Epic Assignee: Unassigned Created: 2020/08/27 12:41 PM Priority: Normal Reporter: Josh Cooper 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
Jira (PUP-8529) Remove environment_data_provider setting
Title: Message Title
Josh Cooper commented on PUP-8529
Re: Remove environment_data_provider setting
Here are my notes about this: data_binding_terminus Calls to the hiera_xxx functions use the :hiera terminus Calls to the lookup function use the Puppet[:data_binding_terminus}. It can be set to hiera, none or the name of a custom terminus for Puppet::DataBinding models. The none terminus can be used to disable automatic parameter lookup. Setting it to a custom value will generate a deprecation warning (under control of strict). There are some examples of 3rd party data_binding_terminus, see https://tickets.puppetlabs.com/browse/PUP-6576?focusedCommentId=332145=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332145. Based on https://tickets.puppetlabs.com/browse/PUP-6576?focusedCommentId=355340=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-355340 there is/was a desire to remove the data_binding_terminus setting so that there's just a single way of configuring lookups (using hiera.conf and different hiera5 backends). I think it would be ok to disallow setting data_binding_terminus to something other than none or hiera in Puppet 7, but will follow up on the mailing list. I don't think we want to remove the setting entirely due to wanting to disable APL (see PUP-7802). environment_data_provider The environment_data_provider setting is from hiera4 and provides a way of calling a per-environment data provider. Its value can be set to none, function or hiera in environment.conf. If it's set to function, then the environment needs to define a function in environments//lib/puppet/functions/environment/data.rb as: with a specific name and implement the data method:
Puppet::Functions.create_function(:'environment::data') do
def data
{ "key" => "value" }
end
end
See https://puppet-on-the-edge.blogspot.com/2015/01/puppet-40-data-in-modules-and.html for more context. If the environment_data_provider is set to function, puppet creates an EnvironmentDataProvider as it does for hiera, but its configuration is adapted to V4 so it knows to execute the environment::data function. It only makes sense to me to remove this setting at the same time we drop Hiera4
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting
Title: Message Title Nate McCurdy updated an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting Change By: Nate McCurdy Affects Version/s: PUP 6.18.0 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.370505.1598545662000.25316.1598546580029%40Atlassian.JIRA.
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting
Title: Message Title Nate McCurdy commented on PUP-10648 Re: puppet 6 agent doesn't honor usecacheonfailure setting This looks to be an issue with server_list as it works for me when just using server [root@blank ~]# sudo puppet agent --onetime --no-daemonize --verbose --usecacheonfailure Error: Request to https://master.vagrant:8140/puppet/v3 failed after 0.004 seconds: Failed to open TCP connection to master.vagrant:8140 (getaddrinfo: Name or service not known) Wrapped exception: Failed to open TCP connection to master.vagrant:8140 (getaddrinfo: Name or service not known) Warning: Unable to fetch my node definition, but the agent run will continue: Warning: No more routes to puppet Info: Retrieving pluginfacts Error: Request to https://master.vagrant:8140/puppet/v3 failed after 0.001 seconds: Failed to open TCP connection to master.vagrant:8140 (getaddrinfo: Name or service not known) Wrapped exception: Failed to open TCP connection to master.vagrant:8140 (getaddrinfo: Name or service not known) Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': No more routes to fileserver
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting
Title: Message Title Vadym Chepkov commented on PUP-10648 Re: puppet 6 agent doesn't honor usecacheonfailure setting FYI, if I remove server_list configuration from puppet.conf and replace it with random server config, file gets restored 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.370505.1598545662000.25311.1598546280024%40Atlassian.JIRA.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Josh Cooper commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates I expected Sensitive to behave like a flag rather than a distinct data type Henrik Lindberg described the performance impact of doing that in PUP-10092, so the current behavior is unlikely to change. I expected that any evaluation via template, string interpolation, etc. would inherit the Sensitive flag of any Sensitive components. It is possible to do this for EPP templates as Henrik Lindberg described above. Henrik Lindberg Thoughts on how to implement that? It looks like we could add a sensitive attribute to the EppExpression. Could the EppEvaluator set the sensitive attribute on the _expression_ if it encounters a Sensitive token? Is there a better way for the evaluator to know that a sensitive value has been unwrapped, and automatically wrap the result in Sensitive? 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
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting
Title: Message Title
Vadym Chepkov commented on PUP-10648
Re: puppet 6 agent doesn't honor usecacheonfailure setting
resolv.conf is managed by the tempate
# This file is managed by Puppet
<%- if $dns::domain { -%>
domain <%= $dns::domain %>
<% } -%>
<% if $dns::search { -%>
search <%= $dns::search.join(" ") %>
<% } -%>
<% $dns::nameservers.each |$ns| { -%>
nameserver <%= $ns %>
<% } -%>
<% if $dns::options { -%>
options <%= $dns::options.join(" ") %>
<% } -%>
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting
Title: Message Title Vadym Chepkov created an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting Issue Type: Bug Affects Versions: PUP 6.17.0 Assignee: Unassigned Created: 2020/08/27 9:27 AM Priority: Normal Reporter: Vadym Chepkov Puppet Version: 6.17.0 (PE2019.8.1) Puppet Server Version: 2019.8.0.37 OS Name/Version: RHEL8 Had a case where /etc/resolv.conf was accidentally removed and puppet agent hasn't recovered it for unknown reason. usecacheonfailure is set to true Easy to reproduce, manage /etc/resolv.conf by puppet, remove the file, puppet agent will start failing and not recovering the file. The log entry : Could not run Puppet configuration client: Could not select a functional puppet master from server_list:
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title Austin Blatt commented on PDB-4874 Re: regression on resource query performance on upgrade to 6.11.3 from 5.1 Julian Taylor are you able to provide an explain analyze of the query from the 5.1.5 postgres, or is that gone at this point? 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.370482.1598537549000.25269.1598544600025%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Fix Version/s: PUP 8.0.0 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.148538.1471963467000.25260.1598543700103%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Josh Cooper Epic Link: PUP-10591 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.148538.1471963467000.25262.1598543700192%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Josh Cooper Labels: platform_7 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.148538.1471963467000.25261.1598543700147%40Atlassian.JIRA.
Jira (PUP-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper commented on PUP-6645 Re: Remove the hiera_xxx functions Given the potential user impact and available resources we have to work on this, I'm going to bump it out of puppet 7. 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.148538.1471963467000.25259.1598543700059%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9648 Drop PSON support Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Fix Version/s: PUP 8.0.0 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.305621.1555690549000.25257.1598543640043%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9648 Drop PSON support Change By: Josh Cooper Labels: platform_7 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.305621.1555690549000.25258.1598543640087%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Josh Cooper commented on PUP-9648 Re: Drop PSON support My thinking is we need to support upgrading agents from Puppet 5, but not Puppet 4 (since we're dropping legacy routes support). Rich data was not enabled end to end by default until Puppet 6. We had some rich data support in Puppet 5, but it only really worked on the agent when compiling the catalog, and there were problems with the Puppet 5 loaders. So we probably need to hold off on this change until Puppet 8, when we're sure all agents can upgrade to 8 using rich data. 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.305621.1555690549000.25255.1598543580035%40Atlassian.JIRA.
Jira (PUP-9648) Drop PSON support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9648 Drop PSON support Change By: Josh Cooper Epic Link: PUP-10593 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.305621.1555690549000.25256.1598543580080%40Atlassian.JIRA.
Jira (PUP-9426) Remove future_features logic
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9426 Remove future_features logic Change By: Josh Cooper Release Notes Summary: Removes the unused future_features setting 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.291460.1547160478000.25240.1598543160091%40Atlassian.JIRA.
Jira (PUP-9426) Remove future_features logic
Title: Message Title Josh Cooper commented on PUP-9426 Re: Remove future_features logic Merged to main in https://github.com/puppetlabs/puppet/commit/003fee55cc71ee058fbb7cdf3652de37c8baf237 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.291460.1547160478000.25239.1598543160047%40Atlassian.JIRA.
Jira (PUP-9405) Remove Future Feature flag for @prefetch_failed_providers in transaction.rb
Title: Message Title Josh Cooper commented on PUP-9405 Re: Remove Future Feature flag for @prefetch_failed_providers in transaction.rb Merged to main in https://github.com/puppetlabs/puppet/commit/1e9f4d9150dc8d2ca034b42957fced6bec863965 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.290960.1546996315000.25237.1598543100051%40Atlassian.JIRA.
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title
Julian Taylor updated an issue
PuppetDB / PDB-4874
regression on resource query performance on upgrade to 6.11.3 from 5.1
Change By:
Julian Taylor
Hi,We have tried updating an environment with a few thousand hosts and 4441439 entries in the catalog_resources postgres table from puppetdb 5.1.5 to 6.11.3 and have seen a large regression in the resource query performanceA query like{code}/pdb/query/v4/resources?query=["and",["=","type","Prometheus::Scrape_job"],["=","exported",true],["not",["=","certname","mprom003.server.lan"]],["=",["parameter","job_name"],"jobname"]] {code}which used to take 70ms now takes 4 seconds.The query is generated by prometheus scrape config:https://github.com/voxpupuli/puppet-prometheus/blob/3ae9b926c8697938398ff2ff66c2dcda539a6603/manifests/config.pp#L234and is executed many times and now times out due to the slow query.Slow query log:{code}SELECT: ... duration: 4027.270 ms execute /C_3: WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL AND deactivated > '2020-08-13T13:23:03.928Z') OR (expired IS NOT NULL and expired > '2020-08-13T13:23:03.928Z')), not_active_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT encode(resources.resource::bytea, 'hex') AS resource, c.certname AS certname, tags AS tags, exported AS exported, line AS line, title AS title, type AS type, e.environment AS environment, file AS file, rpc.parameters AS parameters FROM catalog_resources resources INNER JOIN certnames ON resources.certname_id = certnames.id INNER JOIN catalogs c ON c.certname = certnames.certname LEFT JOIN environments e ON c.environment_id = e.id LEFT JOIN resource_params_cache rpc ON rpc.resource = resources.resource WHERE (((type = $1) AND (exported = $2) AND NOT (c.certname = $3) AND ((encode(resources.resource::bytea, 'hex')) in (SELECT res_param_resource FROM ( (SELECT encode(resource::bytea, 'hex') AS res_param_resource FROM resource_params WHERE ((name = $4) AND (value = $5))) ) sub))) AND NOT ((c.certname) in (SELECT certname FROM ( (SELECT not_active_nodes.certname AS certname FROM not_active_nodes) ) sub)))parameters: $1 = 'Prometheus::Scrape_job', $2 = 't', $3 = 'mprom003.server.lan', $4 = 'job_name', $5 = '"jobname"'{code}Here the explain of the slow query:{code} Nested Loop Left Join (cost=591.68..1122.65 rows=1 width=1357) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Left Join (cost=591.26..1114.20 rows=1 width=636) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Semi Join (cost=591.10..1113.99 rows=1 width=612) (actual time=4098.975..4098.975 rows=0 loops=1) -> Hash Join (cost=453.88..690.22 rows=3 width=612) (actual time=62.459..70.658 rows=3810 loops=1) Hash Cond: (c.certname = certnames.certname) -> Seq Scan on catalogs c (cost=62.27..293.66 rows=1312 width=34) (actual time=0.933..4.710 rows=2625 loops=1) Filter:
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title
Julian Taylor updated an issue
PuppetDB / PDB-4874
regression on resource query performance on upgrade to 6.11.3 from 5.1
Change By:
Julian Taylor
Hi,We have tried updating an environment with a few thousand hosts and 4441439 entries in the catalog_resources postgres table from puppetdb 5.1.5 to 6.11.3 and have seen a large regression in the resource query performanceA query like{code}/pdb/query/v4/resources?query=["and",["=","type","Prometheus::Scrape_job"],["=","exported",true],["not",["=","certname","mprom003.server.lan"]],["=",["parameter","job_name"],"jobname"]] {code}which used to take 70ms now takes 4 seconds.The query is generated by prometheus scrape config:https://github.com/voxpupuli/puppet-prometheus/blob/3ae9b926c8697938398ff2ff66c2dcda539a6603/manifests/config.pp#L234and is executed many times and now times out due to the slow query. Slow query log:{code}SELECT: ... duration: 4027.270 ms execute /C_3: WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL AND deactivated > '2020-08-13T13:23:03.928Z') OR (expired IS NOT NULL and expired > '2020-08-13T13:23:03.928Z')), not_active_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT encode(resources.resource::bytea, 'hex') AS resource, c.certname AS certname, tags AS tags, exported AS exported, line AS line, title AS title, type AS type, e.environment AS environment, file AS file, rpc.parameters AS parameters FROM catalog_resources resources INNER JOIN certnames ON resources.certname_id = certnames.id INNER JOIN catalogs c ON c.certname = certnames.certname LEFT JOIN environments e ON c.environment_id = e.id LEFT JOIN resource_params_cache rpc ON rpc.resource = resources.resource WHERE (((type = $1) AND (exported = $2) AND NOT (c.certname = $3) AND ((encode(resources.resource::bytea, 'hex')) in (SELECT res_param_resource FROM ( (SELECT encode(resource::bytea, 'hex') AS res_param_resource FROM resource_params WHERE ((name = $4) AND (value = $5))) ) sub))) AND NOT ((c.certname) in (SELECT certname FROM ( (SELECT not_active_nodes.certname AS certname FROM not_active_nodes) ) sub)))parameters: $1 = 'Prometheus::Scrape_job', $2 = 't', $3 = 'mprom003.server.lan', $4 = 'job_name', $5 = '"jobname"'{code} Here the explain of the slow query:{code} Nested Loop Left Join (cost=591.68..1122.65 rows=1 width=1357) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Left Join (cost=591.26..1114.20 rows=1 width=636) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Semi Join (cost=591.10..1113.99 rows=1 width=612) (actual time=4098.975..4098.975 rows=0 loops=1) -> Hash Join (cost=453.88..690.22 rows=3 width=612) (actual time=62.459..70.658 rows=3810 loops=1) Hash Cond: (c.certname = certnames.certname) -> Seq Scan on catalogs c (cost=62.27..293.66 rows=1312 width=34) (actual time=0.933..4.710 rows=2625 loops=1) Filter:
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title Julian Taylor created an issue PuppetDB / PDB-4874 regression on resource query performance on upgrade to 6.11.3 from 5.1 Issue Type: Bug Affects Versions: PDB 6.11.3 Assignee: Unassigned Components: PuppetDB Created: 2020/08/27 7:12 AM Priority: Normal Reporter: Julian Taylor Hi, We have tried updating an environment with a few thousand hosts and 4441439 entries in the catalog_resources postgres table from puppetdb 5.1.5 to 6.11.3 and have seen a large regression in the resource query performance A query like /pdb/query/v4/resources?query=["and",["=","type","Prometheus::Scrape_job"],["=","exported",true],["not",["=","certname","mprom003.server.lan"]],["=",["parameter","job_name"],"jobname"]] which used to take 70ms now takes 4 seconds. The query is generated by prometheus scrape config: https://github.com/voxpupuli/puppet-prometheus/blob/3ae9b926c8697938398ff2ff66c2dcda539a6603/manifests/config.pp#L234 and is executed many times and now times out due to
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title
Julian Taylor updated an issue
PuppetDB / PDB-4874
regression on resource query performance on upgrade to 6.11.3 from 5.1
Change By:
Julian Taylor
Hi,We have tried updating an environment with a few thousand hosts and 4441439 entries in the catalog_resources postgres table from puppetdb 5.1.5 to 6.11.3 and have seen a large regression in the resource query performanceA query like{code}/pdb/query/v4/resources?query=["and",["=","type","Prometheus::Scrape_job"],["=","exported",true],["not",["=","certname","mprom003.server.lan"]],["=",["parameter","job_name"],"jobname"]] {code}which used to take 70ms now takes 4 seconds.The query is generated by prometheus scrape config:https://github.com/voxpupuli/puppet-prometheus/blob/3ae9b926c8697938398ff2ff66c2dcda539a6603/manifests/config.pp#L234and is executed many times and now times out due to the slow query.Here the explain of the slow query:{code} Nested Loop Left Join (cost=591.68..1122.65 rows=1 width=1357) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Left Join (cost=591.26..1114.20 rows=1 width=636) (actual time=4098.976..4098.976 rows=0 loops=1) -> Nested Loop Semi Join (cost=591.10..1113.99 rows=1 width=612) (actual time=4098.975..4098.975 rows=0 loops=1) -> Hash Join (cost=453.88..690.22 rows=3 width=612) (actual time=62.459..70.658 rows=3810 loops=1) Hash Cond: (c.certname = certnames.certname) -> Seq Scan on catalogs c (cost=62.27..293.66 rows=1312 width=34) (actual time=0.933..4.710 rows=2625 loops=1) Filter: ((certname <> 'mprom003.server.lan'::text) AND (NOT (hashed SubPlan 1))) Rows Removed by Filter: 1 SubPlan 1 -> Seq Scan on certnames certnames_1 (cost=0.00..62.27 rows=1 width=26) (actual time=0.896..0.896 rows=0 loops=1) Filter: ((deactivated IS NOT NULL) OR (expired IS NOT NULL)) Rows Removed by Filter: 2627 -> Hash (cost=391.53..391.53 rows=6 width=604) (actual time=61.494..61.494 rows=3811 loops=1) Buckets: 4096 (originally 1024) Batches: 1 (originally 1) Memory Usage: 2182kB -> Nested Loop (cost=318.02..391.53 rows=6 width=604) (actual time=4.377..56.959 rows=3811 loops=1) -> Bitmap Heap Scan on catalog_resources resources (cost=317.74..341.74 rows=6 width=586) (actual time=4.367..46.896 rows=3811 loops=1) Recheck Cond: (exported AND (type = 'Prometheus::Scrape_job'::text)) Heap Blocks: exact=3801 -> BitmapAnd (cost=317.74..317.74 rows=6 width=0) (actual time=3.755..3.755 rows=0 loops=1) -> Bitmap Index Scan on catalog_resources_exported_idx (cost=0.00..80.54 rows=3263 width=0) (actual time=1.306..1.306 rows=3840 loops=1) -> Bitmap Index Scan on catalog_resources_type_idx (cost=0.00..236.95 rows=8602 width=0)
Jira (FACT-2753) Resolve facts sequentially
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2753 Resolve facts sequentially Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.369995.1598251196000.25161.1598532180026%40Atlassian.JIRA.
Jira (FACT-2785) partitions..mount has wrong value on sles15-64
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2785
partitions..mount has wrong value on sles15-64
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 5:13 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"partitions./dev/sda2.mount"=>{:new_value=>"\"/usr/local\"", :old_value=>"\"/\""}}
Add Comment
Jira (PUP-10609) Puppet_Agent : Constant Corrective Change for sles 12
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10609 Puppet_Agent : Constant Corrective Change for sles 12 Change By: Austin Boyd Zendesk Ticket Count: 1 2 Zendesk Ticket IDs: 40216 ,40672 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.367445.1595944717000.25157.1598530320026%40Atlassian.JIRA.
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processors.count" => \{: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \{: new_value => "2",: old_value => "\"2\""} - "selinux" => \{: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \{: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \{: new_value => "0",: old_value =>
Jira (FACT-2784) os.release has wrong value on redhat7-AARCH64
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2784
os.release has wrong value on redhat7-AARCH64
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 4:55 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"operatingsystemrelease" => {
: new_value => "\"7.0\"",: old_value => "\"7.4.1708\""
}, "os.release.full" => {
: new_value => "\"7.0\"",: old_value => "\"7.4.1708\""
}, "os.release.minor" => {
: new_value => "\"0\"",: old_value => "\"4\""
Jira (FACT-2783) mountpoints..used report wrong value on osx1014-64
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2783
mountpoints..used report wrong value on osx1014-64
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 4:47 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"mountpoints./private/var/vm.used" => {:new_value => "\"20.00 KiB\"",: old_value => "\"39.80 GiB\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processors.count" => \{: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \{: new_value => "2",: old_value => "\"2\""} - "selinux" => \{: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \{: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \{: new_value => "0",: old_value =>
Jira (FACT-2782) mountpoints values are to large on centos6-32
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2782
mountpoints values are to large on centos6-32
Change By:
Bogdan Irimie
{code } , "mountpoints./dev/shm.available" => { : new_value => "\"2.86 EiB\"",: old_value => "\"946.52 MiB\"" }, "mountpoints./dev/shm.available_bytes" => { : new_value => "3292852608002330624",: old_value => "\"992501760\"" }, "mountpoints./dev/shm.capacity" => { : new_value => "\"22.75%\"",: old_value => "\"0%\"" }, "mountpoints./dev/shm.size" => { : new_value => "\"3.70 EiB\"",: old_value => "\"946.52 MiB\"" }, "mountpoints./dev/shm.size_bytes" => { : new_value => "4262762601414942720",: old_value => "\"992501760\"" }, "mountpoints./dev/shm.used" => { : new_value => "\"861.44 PiB\"",: old_value => "\"0 bytes\"" }, "mountpoints./dev/shm.used_bytes" => { : new_value => "969892401000742912",: old_value => "\"0\"" {code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message
Jira (FACT-2782) mountpoints values are to large on centos6-32
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2782
mountpoints values are to large on centos6-32
Change By:
Bogdan Irimie
}, "mountpoints./dev/shm.available" => { : new_value => "\"2.86 EiB\"",: old_value => "\"946.52 MiB\"" }, "mountpoints./dev/shm.available_bytes" => { : new_value => "3292852608002330624",: old_value => "\"992501760\"" }, "mountpoints./dev/shm.capacity" => { : new_value => "\"22.75%\"",: old_value => "\"0%\"" }, "mountpoints./dev/shm.size" => { : new_value => "\"3.70 EiB\"",: old_value => "\"946.52 MiB\"" }, "mountpoints./dev/shm.size_bytes" => { : new_value => "4262762601414942720",: old_value => "\"992501760\"" }, "mountpoints./dev/shm.used" => { : new_value => "\"861.44 PiB\"",: old_value => "\"0 bytes\"" }, "mountpoints./dev/shm.used_bytes" => { : new_value => "969892401000742912",: old_value => "\"0\""
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are
Jira (FACT-2782) mountpoints values are to large on centos6-32
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2782 mountpoints values are to large on centos6-32 Change By: Bogdan Irimie Summary: mountpoints ..used_bytes is values are to large on centos6-32 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.370474.1598527981000.25143.1598528100057%40Atlassian.JIRA.
Jira (FACT-2782) mountpoints values are to large on centos6-32
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2782
mountpoints values are to large on centos6-32
Change By:
Bogdan Irimie
{code}"mountpoints./dev/shm.used_bytes" => {: new_value => "969892401000742912",: old_value => "\"0\""}{code}
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.370474.1598527981000.25144.1598528100099%40Atlassian.JIRA.
Jira (FACT-2782) mountpoints..used_bytes is to large on centos6-32
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2782
mountpoints..used_bytes is to large on centos6-32
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 4:33 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"mountpoints./dev/shm.used_bytes" => {: new_value => "969892401000742912",: old_value => "\"0\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processors.count" => \{: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \{: new_value => "2",: old_value => "\"2\""} - "selinux" => \{: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \{: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \{: new_value => "0",: old_value =>
Jira (FACT-2781) filesystems has wrong values on osx1015
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2781
filesystems has wrong values on osx1015
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 4:18 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"filesystems" => {: new_value => "\"apfs,autofs,devfs,hfs,vmhgf\"",: old_value => "\"apfs,autofs,devfs,hfs,vmhgfs\""}
Add Comment
Jira (FACT-2780) os.distro.description has wrong value on debian8-64
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2780
os.distro.description has wrong value on debian8-64
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 4:10 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"os.distro.description" => {: new_value => "\"Debian GNU/Linux 8 (jessie)\"",: old_value => "\"Debian GNU/Linux 8.11 (jessie)\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processors.count" => \{: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \{: new_value => "2",: old_value => "\"2\""} - "selinux" => \{: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \{: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \{: new_value => "0",: old_value =>
Jira (FACT-2773) Add boardassettag fact on Linux
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2773 Add boardassettag fact on Linux Change By: Bogdan Irimie Update DMI resolver to find this fact as well.Add core fact and legacy fact. Factes:- boardassettag - dmi.board.asset_tag 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.370060.1598294959000.25131.1598526300028%40Atlassian.JIRA.
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processorcount" => \{: new_value => "2",: old_value => "\"2\""} - "processors.count" => \{: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \{: new_value => "2",: old_value => "\"2\""} - "selinux" => \{: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \{: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \{: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \{: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \{: new_value => "0",: old_value =>
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7- "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => \ {: new_value => "2",: old_value => "\"2\""} - "processorcount" => \ {: new_value => "2",: old_value => "\"2\""} - "processors.count" => \ {: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => \ {: new_value => "2",: old_value => "\"2\""} - "selinux" => \ {: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => \ {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => \ {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => \ {: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => \ {: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => \ {: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => \ {:
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7- "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - "physicalprocessorcount" => {: new_value => "2",: old_value => "\"2\""} - "processorcount" => {: new_value => "2",: old_value => "\"2\""} - "processors.count" => {: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => {: new_value => "2",: old_value => "\"2\""} - "selinux" => {: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => {: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => {: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds" => {: new_value => "1873",: old_value => "\"1871\""} - "uptime_days" => {: new_value => "0",: old_value => "\"0\""} -
Jira (FACT-2779) serialnumber is not resolved on aix61power
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2779
serialnumber is not resolved on aix61power
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 3:42 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"serialnumber" => {: new_value => "nil",: old_value => "\"21684EW\""}
Add Comment
Jira (FACT-2778) big different in mountpoint capacity on aix6.1power
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2778
big different in mountpoint capacity on aix6.1power
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 3:37 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
"mountpoints./.capacity" => {: new_value => "\"11.43%\"",: old_value => "\"53.03%\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
redhat 7 - "fips_enabled" => \{: new_value => "false",: old_value => "\"false\""} - "identity.gid" => \{: new_value => "0",: old_value => "\"0\""} - "identity.privileged" => \{: new_value => "true",: old_value => "\"true\""} - "identity.uid" => \{: new_value => "0",: old_value => "\"0\""} - "is_virtual" => \{: new_value => "true",: old_value => "\"true\""} - "load_averages.15m" => \{: new_value => "0.08",: old_value => "\"0.08\""} - "load_averages.1m" => \{: new_value => "0.47",: old_value => "\"0.47\""} - "load_averages.5m" => \{: new_value => "0.14",: old_value => "\"0.14\""} - "memory.swap.available_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => \{: new_value => "\"0.00%\"",: old_value => "\"0%\""} - "memory.swap.total_bytes" => \{: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.used_bytes" => \{: new_value => "0",: old_value => "\"0\""} - "memory.system.available_bytes" => \{: new_value => "6901067776",: old_value => "\"7896244224\""} - "memory.system.total_bytes" => \{: new_value => "8201728000",: old_value => "\"8201728000\""} - "memory.system.used_bytes" => \{: new_value => "1300660224",: old_value => "\"305483776\""} - "memoryfree_mb" => \{: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => \{: new_value => "7821.78",: old_value => "\"7821.77734375\""} - "mountpoints./.available_bytes" => \{: new_value => "17441038336",: old_value => "\"17441017856\""} - "mountpoints./.size_bytes" => \{: new_value => "19815989248",: old_value => "\"19815989248\""} - "mountpoints./.used_bytes" => \{: new_value => "2374950912",: old_value => "\"2374971392\""} - "mtu_ens160" => \{: new_value => "1500",: old_value => "\"1500\""} (mtu_.*) - "networking.interfaces.ens160.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "networking.mtu" => \{: new_value => "1500",: old_value => "\"1500\""} - "os.selinux.enabled" => \{: new_value => "false",: old_value => "\"false\""} - "partitions./dev/mapper/rhel-root.size_bytes" => \{: new_value => "19826475008",: old_value => "\"19826475008\""} - " partitions./dev/mapper/rhel-swap.size_bytes" => \{: new_value => "1073741824",: old_value => "\"1073741824\""} - " physicalprocessorcount" => {: new_value => "2",: old_value => "\"2\""} - "processorcount" => {: new_value => "2",: old_value => "\"2\""} - "processors.count" => {: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => {: new_value => "2",: old_value => "\"2\""} - "selinux" => {: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => {: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => {: new_value => "0",: old_value => "\"0\""} - "system_uptime.seconds"
Jira (FACT-2777) lsbmajdistrelease has wrong value on ubuntu16.04
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2777
lsbmajdistrelease has wrong value on ubuntu16.04
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 3:24 AM
Priority:
Normal
Reporter:
Bogdan Irimie
"lsbmajdistrelease" => {: new_value => "\"16\"",: old_value => "\"16.04\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
- "fips_enabled" => \ {: new_value => "false",: old_value => "\"false\""}- "identity.gid" => \ {: new_value => "0",: old_value => "\"0\""}- "identity.privileged" => \ {: new_value => "true",: old_value => "\"true\""}- "identity.uid" => \ {: new_value => "0",: old_value => "\"0\""}- "is_virtual" => \ {: new_value => "true",: old_value => "\"true\""}- "load_averages.15m" => \ {: new_value => "0.08",: old_value => "\"0.08\""}- "load_averages.1m" => \ {: new_value => "0.47",: old_value => "\"0.47\""}- "load_averages.5m" => \ {: new_value => "0.14",: old_value => "\"0.14\""}- "memory.swap.available_bytes" => \ {: new_value => "1073737728",: old_value => "\"1073737728\""}- "memory.swap.capacity" => \ {: new_value => "\"0.00%\"",: old_value => "\"0%\""}- "memory.swap.total_bytes" => \ {: new_value => "1073737728",: old_value => "\"1073737728\""}- "memory.swap.used_bytes" => \ {: new_value => "0",: old_value => "\"0\""}- "memory.system.available_bytes" => \ {: new_value => "6901067776",: old_value => "\"7896244224\""}- "memory.system.total_bytes" => \ {: new_value => "8201728000",: old_value => "\"8201728000\""}- "memory.system.used_bytes" => \ {: new_value => "1300660224",: old_value => "\"305483776\""}- "memoryfree_mb" => \ {: new_value => "6581.37",: old_value => "\"7530.4453125\""}- "memorysize_mb" => \ {: new_value => "7821.78",: old_value => "\"7821.77734375\""}- "mountpoints./.available_bytes" => \ {: new_value => "17441038336",: old_value => "\"17441017856\""}- "mountpoints./.size_bytes" => \ {: new_value => "19815989248",: old_value => "\"19815989248\""}- "mountpoints./.used_bytes" => \ {: new_value => "2374950912",: old_value => "\"2374971392\""}- "mtu_ens160" => \ {: new_value => "1500",: old_value => "\"1500\""} (mtu_.*)- "networking.interfaces.ens160.mtu" => \ {: new_value => "1500",: old_value => "\"1500\""}- "networking.mtu" => \ {: new_value => "1500",: old_value => "\"1500\""}- "os.selinux.enabled" => \ {: new_value => "false",: old_value => "\"false\""}- "partitions./dev/mapper/rhel-root.size_bytes" => \ {: new_value => "19826475008",: old_value => "\"19826475008\""}- "partitions./dev/mapper/rhel-swap.size_bytes" => \ {: new_value => "1073741824",: old_value => "\"1073741824\""} - "physicalprocessorcount" => {: new_value => "2",: old_value => "\"2\""} - "processorcount" => {: new_value => "2",: old_value => "\"2\""} - "processors.count" => {: new_value => "2",: old_value => "\"2\""} - "processors.physicalcount" => {: new_value => "2",: old_value => "\"2\""} - "selinux" => {: new_value => "false",: old_value => "\"false\""} - "swapfree_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "swapsize_mb" => {: new_value => "1024.0",: old_value => "\"1023.99609375\""} - "system_uptime.days" => {: new_value => "0",: old_value => "\"0\""} - "system_uptime.hours" => {: new_value => "0",:
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
- "fips_enabled" => {: new_value => "false",: old_value => "\"false\""}- "identity.gid" => {: new_value => "0",: old_value => "\"0\""}- "identity.privileged" => {: new_value => "true",: old_value => "\"true\""}- "identity.uid" => {: new_value => "0",: old_value => "\"0\""}- "is_virtual" => {: new_value => "true",: old_value => "\"true\""}- "load_averages.15m" => {: new_value => "0.08",: old_value => "\"0.08\""}- "load_averages.1m" => {: new_value => "0.47",: old_value => "\"0.47\""}- "load_averages.5m" => {: new_value => "0.14",: old_value => "\"0.14\""}- "memory.swap.available_bytes" => {: new_value => "1073737728",: old_value => "\"1073737728\""}- "memory.swap.capacity" => {: new_value => "\"0.00%\"",: old_value => "\"0%\""}- "memory.swap.total_bytes" => {: new_value => "1073737728",: old_value => "\"1073737728\""}- "memory.swap.used_bytes" => {: new_value => "0",: old_value => "\"0\""}- "memory.system.available_bytes" => {: new_value => "6901067776",: old_value => "\"7896244224\""}- "memory.system.total_bytes" => {: new_value => "8201728000",: old_value => "\"8201728000\""}- "memory.system.used_bytes" => {: new_value => "1300660224",: old_value => "\"305483776\""}- "memoryfree_mb" => {: new_value => "6581.37",: old_value => "\"7530.4453125\""} - "memorysize_mb" => {: new_value => "7821.78",: old_value => "\"7821.77734375\""}- "mountpoints./.available_bytes" => {: new_value => "17441038336",: old_value => "\"17441017856\""}- "mountpoints./.size_bytes" => {: new_value => "19815989248",: old_value => "\"19815989248\""}- "mountpoints./.used_bytes" => {: new_value => "2374950912",: old_value => "\"2374971392\""}- "mtu_ens160" => {: new_value => "1500",: old_value => "\"1500\""} (mtu_.*)- "networking.interfaces.ens160.mtu" => {: new_value => "1500",: old_value => "\"1500\""}- "networking.mtu" => {: new_value => "1500",: old_value => "\"1500\""}- "os.selinux.enabled" => {: new_value => "false",: old_value => "\"false\""}- "partitions./dev/mapper/rhel-root.size_bytes" => {: new_value => "19826475008",: old_value => "\"19826475008\""}- "partitions./dev/mapper/rhel-swap.size_bytes" => {: new_value => "1073741824",: old_value => "\"1073741824\""}
Jira (FACT-2776) partitions..uuid not working on redhat7
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2776
partitions..uuid not working on redhat7
Change By:
Bogdan Irimie
{code}"partitions./dev/mapper/rhel-root.uuid" => {: new_value => "nil",: old_value => "\"cb455c09-da6b-44e6-8464-48a5a296d420\""}{code}
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.370467.1598518046000.25102.1598518140028%40Atlassian.JIRA.
Jira (FACT-2775) partitions..filesystem not working on redhat7
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2775 partitions..filesystem not working on redhat7 Change By: Bogdan Irimie Summary: partitions.< partition_name partition >.filesystem not working on redhat7 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.370466.1598517881000.25100.1598518080151%40Atlassian.JIRA.
Jira (FACT-2776) partitions..uuid not working on redhat7
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2776 partitions..uuid not working on redhat7 Change By: Bogdan Irimie Summary: partitions..uuid not working on rhel7 redhat7 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.370467.1598518046000.25101.1598518080199%40Atlassian.JIRA.
Jira (FACT-2776) partitions..uuid not working on rhel7
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2776 partitions..uuid not working on rhel7 Issue Type: Bug Assignee: Unassigned Created: 2020/08/27 1:47 AM Labels: platform_7 Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-2775) partitions..filesystem not working on redhat7
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2775
partitions..filesystem not working on redhat7
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/08/27 1:44 AM
Labels:
platform_7
Priority:
Normal
Reporter:
Bogdan Irimie
Facter 3.x resolves to `xfs` while Facter 4 cannot resolve the fact
"partitions./dev/mapper/rhel-root.filesystem" => {: new_value => "nil",: old_value => "\"xfs\""}
Add Comment
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
- "fips_enabled" => {: new_value => "false",: old_value => "\"false\""}- "identity.gid" => {: new_value => "0",: old_value => "\"0\""}- "identity.privileged" => {: new_value => "true",: old_value => "\"true\""}- "identity.uid" => {: new_value => "0",: old_value => "\"0\""}- "is_virtual" => {: new_value => "true",: old_value => "\"true\""}- "load_averages.15m" => {: new_value => "0.08",: old_value => "\"0.08\""}- "load_averages.1m" => {: new_value => "0.47",: old_value => "\"0.47\""}- "load_averages.5m" => {: new_value => "0.14",: old_value => "\"0.14\""}- "memory.swap.available_bytes" => {: new_value => "1073737728",: old_value => "\"1073737728\""} - "memory.swap.capacity" => {: new_value => "\"0.00%\"",: old_value => "\"0%\""}- "memory.swap.total_bytes" => {: new_value => "1073737728",: old_value => "\"1073737728\""}- "memory.swap.used_bytes" => {: new_value => "0",: old_value => "\"0\""}- "memory.system.available_bytes" => {: new_value => "6901067776",: old_value => "\"7896244224\""}- "memory.system.total_bytes" => {: new_value => "8201728000",: old_value => "\"8201728000\""}- "memory.system.used_bytes" => {: new_value => "1300660224",: old_value => "\"305483776\""}- "memoryfree_mb" => {: new_value => "6581.37",: old_value => "\"7530.4453125\""}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2748) Fix fact types on all platforms
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2748
Fix fact types on all platforms
Change By:
Bogdan Irimie
- "fips_enabled" => {: new_value => "false",: old_value => "\"false\""}- "identity.gid" => {: new_value => "0",: old_value => "\"0\""}- "identity.privileged" => {: new_value => "true",: old_value => "\"true\""}- "identity.uid" => {: new_value => "0",: old_value => "\"0\""}- "is_virtual" => {: new_value => "true",: old_value => "\"true\""}- "load_averages.15m" => {: new_value => "0.08",: old_value => "\"0.08\""}- "load_averages.1m" => {: new_value => "0.47",: old_value => "\"0.47\""}- "load_averages.5m" => {: new_value => "0.14",: old_value => "\"0.14\""}- "memory.swap.available_bytes" => {: new_value => "1073737728",: old_value => "\"1073737728\""}
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
