Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-6295 Include corrective_change field in reports Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6586) User resource always reports password changed when account disabled
Title: Message Title Ethan Brown commented on PUP-6586 Re: User resource always reports password changed when account disabled We can indeed verify disabled status on the ADSI User with the AccountDisabled property. Of course, we're hoping to move away from ADSI in the future to something based more on the Windows API - but that's still a bit out. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2935) Duplicate declaration: Service[firewalld] is already declared
Title: Message Title Tracy Phillips updated an issue PuppetDB / PDB-2935 Duplicate declaration: Service[firewalld] is already declared Change By: Tracy Phillips Comment: If I remove /etc/puppetlabs/code/environments/production/modules/puppetdb/manifests/server/firewall.pp the puppet run completes without error. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2856) OSX and Windows testing related to the PuppetDB CLI in PE
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2856 OSX and Windows testing related to the PuppetDB CLI in PE Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6439) Pass per-instance property sensitivity from resource catalog to resource harness
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-6439 Pass per-instance property sensitivity from resource catalog to resource harness Change By: Branan Riley Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6588) Allow context path in http_proxy
Title: Message Title Jainish Shah commented on PUP-6588 Re: Allow context path in http_proxy Same Behaviour with: puppet module --debug install --module_repository=http://10.60.1.94:8080/artifactory/Puppet puppetlabs/azure Debug: Runtime environment: puppet_version=4.5.2, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8 Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from http://10.60.1.94:8080/artifactory/Puppet ... Debug: HTTP GET http://10.60.1.94:8080/artifactory/Puppet/v3/releases?module=puppetlabs-azure_groups=base+pe_only Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Error: Request to Puppet Forge failed. The server being queried was http://10.60.1.94:8080/v3/releases?module=puppetlabs-azure_groups=base+pe_only The HTTP response we received was '404 Not Found' Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6588) Allow context path in http_proxy
Title: Message Title Jainish Shah created an issue Puppet / PUP-6588 Allow context path in http_proxy Issue Type: Bug Assignee: Unassigned Created: 2016/08/05 2:39 PM Priority: Normal Reporter: Jainish Shah tried `export http_proxy=http://10.60.1.94:8080/artifactory/Puppet` Then `puppet module --debug search apache` Debug: Runtime environment: puppet_version=4.5.2, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8 Notice: Searching https://forgeapi.puppetlabs.com ... Debug: HTTP GET https://forgeapi.puppetlabs.com/v3/modules?query=apache_groups=base+pe_only Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Error: Could not connect to https://forgeapi.puppetlabs.com There was a network communications problem The error we caught said '404 "Not Found"' Check your network connection and try again Error: Try 'puppet help module search' for usage It tries to search module only from http://Host:Port it ignores context path Add Comment
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_resource_user-security-log-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_resource_user-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6579) yum package test failing on master branch
Title: Message Title Kenn Hussey commented on PUP-6579 Re: yum package test failing on master branch Branan Riley should this be in 'Ready for CI' now? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title Kenn Hussey commented on PUP-6578 Re: Failure to apply defined ensure value for service Branan Riley should this be in 'Ready for CI' now? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_apply_2-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_apply_2-security_log-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Glenn Sarti Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title
Rob Reynolds commented on PUP-6483
Re: "puppet resource user", when run in Windows creates a login attempt.
Installed the 64-bit version.
Created a manifest called user_nopassword.pp:
user {'bob':
ensure => present,
}
user {'bill':
ensure => present,
password = '123abcD',
Add Comment
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_apply-security_log-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Attachment: puppet_apply-x64.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" It would do the same bad thing. It would also do that if bar was a 4.x ruby function. The only way around the problem is to set environment_timeout to 0. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kenneth Barber commented on PUP-6295 Re: Include corrective_change field in reports Jorie Tappa heya, Kylo Ginsberg asked me to put together release notes for this ticket. I've attached them to the release notes summary, but I'm terrible at english, so feel free to hack it to pieces. I think I've made the most pertinent points at least. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-6295 Include corrective_change field in reports Change By: Kenneth Barber Release Notes Summary: This release adds a new report event field called ‘corrective_change’ that is designed to detect manual change that has been corrected by a Puppet run.This feature should help users be able to detect when an unexpected change occurred outside of Puppet, allowing better auditing and understanding around changes.This feature achieves this by storing the last best known value for each property that is applied by Puppet, and comparing that against the values in the next Puppet run.As part of the requirement is to store values, this feature also introduces a new local storage mechanism, and introduces a new configuration option ‘transactionstorefile’ which points at the YAML file used. This storage is queried for each run for old values during comparison, and persists the new values for next transaction to do its calculation.While we’ve done our best to ensure this feature works well, this entire process is still in development and is quite new, and has some known points of interest:* For noop events in particular, these a treated especially. We will continue to return a positive ‘corrective_change’ flag if there will be a corrective_change, if Puppet was to be ran in enforcement mode.* Today, idempotency issues are raised as ‘corrective_change’ because we can’t tell the difference. An idempotency issue is when either a provider has a bug applying a change twice consistently, or when Puppet DSL code (or external dependences) is used that has idempotency issues (common in service, and exec resources for example). For those properties that have known idempotency issues, we have introduced an ‘idempotent’ flag for declaring that corrective_change calculation can be skipped . An example can be found in the notify provider , as the message property on notify has been a long-standing and well known non-idempotent property : https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/notify.rb#L9* The API for comparison in Puppet for older arbitrary values is brittle, and some custom Puppet types may show the incorrect thing for corrective_change as a consequence. We ask users to raise bugs when these cases are discovered.* For now, if there is any exception during value comparison we will still continue to run Puppet, but return an error to the user so it can be debugged. Also, we return a ‘corrective_change’ as nil instead, indicating an unknown state. Any cases where this occurs should be raised as bugs to the appropriate project.* Comparison of secret values is currently out of scope. For us to ensure we could compare these values, we would have to store them in doing so leak secret information. We’ve decided we would step back from this problem, and for now secret properties are not supported for being flagged as corrective.Along with flagging each event with the ‘corrective_change’ field, we also flag a resource that has such events, and the entire report. Metrics have been included to allow report consumers to see a count of events that are marked as ‘corrective_change’ also.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6295 Include corrective_change field in reports Change By: Kylo Ginsberg Release Notes Summary: This release adds a new report event field called ‘corrective_change’ that is designed to detect manual change that has been corrected by a Puppet run.This feature should help users be able to detect when an unexpected change occurred outside of Puppet, allowing better auditing and understanding around changes.This feature achieves this by storing the last best known value for each property that is applied by Puppet, and comparing that against the values in the next Puppet run.As part of the requirement is to store values, this feature also introduces a new local storage mechanism, and introduces a new configuration option ‘transactionstorefile’ which points at the YAML file used. This storage is queried for each run for old values during comparison, and persists the new values for next transaction to do its calculation.While we’ve done our best to ensure this feature works well, this entire process is still in development and is quite new, and has some known points of interest:* For noop events in particular, these a treated especially. We will continue to return a positive ‘corrective_change’ flag if there will be a corrective_change, if Puppet was to be ran in enforcement mode.* Today, idempotency issues are raised as ‘corrective_change’ because we can’t tell the difference. An idempotency issue is when either a provider has a bug applying a change twice consistently, or when Puppet DSL code (or external dependences) is used that has idempotency issues (common in service, and exec resources for example). For those properties that have known idempotency issues, we have introduced an ‘idempotent’ flag for declaring. An example can be found in the notify provider: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/notify.rb#L9* The API for comparison in Puppet for older arbitrary values is brittle, and some custom Puppet types may show the incorrect thing for corrective_change as a consequence. We ask users to raise bugs when these cases are discovered.* For now, if there is any exception during value comparison we will still continue to run Puppet, but return an error to the user so it can be debugged. Also, we return a ‘corrective_change’ as nil instead, indicating an unknown state. Any cases where this occurs should be raised as bugs to the appropriate project.* Comparison of secret values is currently out of scope. For us to ensure we could compare these values, we would have to store them in doing so leak secret information. We’ve decided we would step back from this problem, and for now secret properties are not supported for being flagged as corrective.Along with flagging each event with the ‘corrective_change’ field, we also flag a resource that has such events, and the entire report. Metrics have been included to allow report consumers to see a count of events that are marked as ‘corrective_change’ also.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Rob Reynolds Assignee: Erick Banks Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title
Ryan Whitehurst commented on PUP-6582
Re: The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Henrik Lindberg would that cause this issue to still occur if you did something (bad) like below, or does/would creating a named closure with the `function` keyword always initialize without a specific parent scope?
foo/manifests/bar.pp
function bar() {
$facts['system_uptime']['seconds']
}
class foo::bar {
notify { bar(): }
}
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Erick Banks commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) Demoed to me by Moses, James' acceptance test reviewed and is green in CI. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" yes, that was the problem... thus: The problem affects all global variable access in puppet functions. It also affects all lookupvar done in 4.x functions for a global variable. Workaround: set environment_timeout to 0 (which is the current recommendation anyway for other reasons). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Henrik Lindberg Summary: The environment cache erroneously caches the resultant binds topscope and compilation gets values of functions defined purely in the puppet language from "first compilation after restart" Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language DOH! Functions when created are bound to a closure_scope (the scope where they are defined). This becomes the parent scope of the local scope used for the function. It means loaders either must be torn down for each environment and recreated (not much use having a cache then), or Function.closure_scope must return the current global scope if not initialized with a specific scope. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kenneth Barber commented on PUP-6295 Re: Include corrective_change field in reports The current build for this patch failed for puppet-agent upstream, PUP-6578 and PUP-6579 covers those failures. Potential fix PR is here: https://github.com/puppetlabs/puppet/pull/5174 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title Kenneth Barber commented on PUP-6578 Re: Failure to apply defined ensure value for service Potential fix is here: https://github.com/puppetlabs/puppet/pull/5174 its mixed in with PUP-6579 but we can break it up if required. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6579) yum package test failing on master branch
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6579 yum package test failing on master branch Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6545) Ruby 2.3 fails spec tests on Appveyor in Windows
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6545 Ruby 2.3 fails spec tests on Appveyor in Windows Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1454 When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6551) Pin json_pure dependency to < 2
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6551 Pin json_pure dependency to < 2 Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6295 Include corrective_change field in reports Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6582 The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Change By: Henrik Lindberg Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6582 The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Change By: Henrik Lindberg Affects Version/s: PUP 4.6.0 Affects Version/s: PUP 4.5.3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language I managed to recreate this. The function is actually being called over and over again. The problem is that it gets access to the wrong scope. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6582 The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Change By: Henrik Lindberg Sprint: Language 2016-08-10 (3rd 1.6.0 Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1202) ENC should instantiate defines
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-1202
ENC should instantiate defines
Change By:
Henrik Lindberg
It would be great if Puppets ENC could instantiate defines. A simple example: {code} site.pp cleanup_2::cleanup {"/var/log/php/": matches => "*", recurse => false, size => "300m", age => "6w", rmdirs => false, } cleanup_2::cleanup {"/appserver/mapbender/log/": matches => "*", recurse => true, size => "100m", age => "2w", rmdirs => false, }cleanup_2/init.ppclass cleanup_2 { define cleanup ($matches, $age, $size, $recurse, $rmdirs) { tidy {"$name": matches => $matches, age => $age, size => $size, recurse => $recurse, backup => false, rmdirs => $rmdirs, type => mtime; }}} {code} This can not be done with the current ENC, you just can add one define to a node... .
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title
Jeremy Barlow commented on PUP-6582
Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Both Ryan Whitehurst and I were able to reproduce this just with a stock Puppet Server 2.4.0 / Puppet Agent 1.5.3 / Puppet 4.5.3 install without the versioned code service / code-id functionality being enabled on the server.
For reference, here are the files I was using:
/etc/puppetlabs/code/environments/production/environment.conf
environment_timeout = unlimited
/etc/puppetlabs/code/environments/production/manifests/site.pp
include uptime
/etc/puppetlabs/code/environment/production/modules/uptime/manifests/init.pp
class uptime {
Jira (PUP-1202) ENC should instantiate defines
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1202 ENC should instantiate defines Change By: Henrik Lindberg Sprint: Language Triage Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6579) yum package test failing on master branch
Title: Message Title Kenneth Barber commented on PUP-6579 Re: yum package test failing on master branch A potential fix is in the PR here: https://github.com/puppetlabs/puppet/pull/5174. This switches the should setting to use self.should properly, instead of relying on dup. It wraps the entire call in bubble-wrap as well, swallowing exceptions and simply logging them to avoid failing transactions due to insync comparison issues we run into along the way. Kind of sucks, but we're working with 3rd party code and a troublesome api. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Anything that direct puppet could be doing that would cause this? A computed id - made "dirty" by Ruby function calls, but not by puppet function calls? (I am trying to come up with hypotheses to test). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6586) User resource always reports password changed when account disabled
Title: Message Title Moses Mendoza commented on PUP-6586 Re: User resource always reports password changed when account disabled Silently ignore the given password (and perhaps introduce a warning that passwords for disabled accounts are not managed), only setting the password when the account is actually enabled In this option would we (can we) first do a check for if an account is disabled before actually attempting the logon? If so, I think this may also be one to really consider - maybe it depends on how much it matters that we generate failed login attempts in the security log. This option won't generate spurious/recurring logon failures in the security log (which e.g., potentially obscure our user's audit(s), security measures, etc). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte Release Notes Summary: Bug fix in yet unreleased feature Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte QA Highest Test Level: Acceptance Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte QA Risk Assessment Reason: fails puppet run when encountered Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6578) Failure to apply defined ensure value for service
Title: Message Title John Duarte updated an issue Puppet / PUP-6578 Failure to apply defined ensure value for service Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Chris Price commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Chris Price Does puppet server have logic trying to figure out if one request will yield an identical catalog and then avoid compilation ? Definitely not. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on STDOUT
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6587
`puppet module search --render-as json` returns non-JSON first line on STDOUT
Change By:
Jeremy Adams
As a user wanting to parse JSON returned from puppet module tool,I need puppet module tool to return only JSON on {{ stdout }} so I can pipe it to thenext tool in my pipeline such as {{jq}}.Currently two lines are returned on {{stdout}} . The second line contains the JSON output, while, the first line is:{{Notice: Searching https://forgeapi.puppetlabs.com ...}}That line should not appear on the standard output {{stdout}} .To make the JSON parseable, you need to strip off the first line, currently.Since a lot of JSON is returned to the screen, it wasn't clear at first what the problem was. A possible solution would be to return the {{Notice: Searching https://forgeapi.puppetlabs.com ...}} message on {{stderr}} instead of {{stdout}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on stdout
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6587 `puppet module search --render-as json` returns non-JSON first line on stdout Change By: Jeremy Adams Summary: `puppet module search --render-as json` returns non-JSON first line on STDOUT stdout Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6056) Specification of the new function API should include autoload information
Title: Message Title Henrik Lindberg assigned an issue to Jorie Tappa Puppet / PUP-6056 Specification of the new function API should include autoload information Change By: Henrik Lindberg Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6056) Specification of the new function API should include autoload information
Title: Message Title Henrik Lindberg commented on PUP-6056 Re: Specification of the new function API should include autoload information Specification merged to master at: ce9b86a Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Ryan Whitehurst Which version of Puppet was used (not totally clear)? There has been bugs in the loaders (a memory leak + binding to values in the first evaluated environment instance when caching. Those problems were fixed quite some time ago). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6582 The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Change By: Henrik Lindberg Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Chris Price Does puppet server have logic trying to figure out if one request will yield an identical catalog and then avoid compilation ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously caches the resultant values of functions defined purely in the puppet language
Title: Message Title Henrik Lindberg commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language This is truly bizarre behavior - there is no logic in the Ruby code base that tries to memoize function returns based on the input as we cannot know if functions have side effects or depend on external scope. However, it could possible be bugs in the call logic that does something differently first time function is called. Will see if I can replicate this with only Ruby. Ping Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1459) Allow specifying the config file from command line
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1459 Allow specifying the config file from command line Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1458) Allow setting existing facter config flags from the config file
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1458 Allow setting existing facter config flags from the config file Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5623) Callable type should be able to describe return type
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5623 Callable type should be able to describe return type Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6583) `puppet module generate` does not honor `--modulepath` on the command line
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6583 `puppet module generate` does not honor `--modulepath` on the command line Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on STDOUT
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6587 `puppet module search --render-as json` returns non-JSON first line on STDOUT Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on STDOUT
Title: Message Title Jeremy Adams created an issue Puppet / PUP-6587 `puppet module search --render-as json` returns non-JSON first line on STDOUT Issue Type: Bug Assignee: Unassigned Created: 2016/08/04 11:04 PM Priority: Normal Reporter: Jeremy Adams As a user wanting to parse JSON returned from puppet module tool, I need puppet module tool to return only JSON on stdout so I can pipe it to the next tool in my pipeline such as jq. Currently two lines are returned. The second line contains the JSON output, while, the first line is: Notice: Searching https://forgeapi.puppetlabs.com ... That line should not appear on the standard output. To make the JSON parseable, you need to strip off the first line, currently. Since a lot of JSON is returned to the screen, it wasn't clear at first what the problem was. Add Comment
