Jira (BOLT-614) I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1
Title: Message Title Halim Wijaya commented on BOLT-614 Re: I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1 The updated documentation https://puppet.com/docs/bolt/1.x/writing_tasks.html#tasks-with-multiple-implementations doesn't work with `puppet task` command. Orchestrator looks for executable file that is the same name with the metadata file and will complain the task doesn't exist if it can't find one. # puppet task run test::listout --nodes pe-201815-master.puppetdebug.vlan Starting job ... Failed to submit job: puppetlabs.orchestrator/unknown-task: The test::listout task does not exist in environment production # ls -ahl total 12K drwxr-xr-x. 2 pe-puppet pe-puppet 74 Jan 16 22:56 . drwxr-xr-x. 3 pe-puppet pe-puppet 18 Jan 16 22:37 .. -rw-r--r--. 1 pe-puppet pe-puppet 251 Jan 16 22:56 listout.json -rw-r--r--. 1 pe-puppet pe-puppet 20 Jan 16 22:37 listout_linux.sh -rw-r--r--. 1 pe-puppet pe-puppet 14 Jan 16 22:38 listout_windows.ps1
Jira (PUP-1168) Add values to default resources with the plusignment
Title: Message Title
Daniel Parks commented on PUP-1168
Re: Add values to default resources with the plusignment
For future people who stumble upon this, here is a puppet apply command line that demonstrates the problem:
❯ puppet apply <<'EOF'
define echo ( $lines = ['one'] ) {
exec { "echo ${title}":
command => "/bin/echo ${$lines.join(', ')}",
logoutput => true,
}
}
echo { 'a': }
echo { 'b': lines => ['two'] }
Echo <| |> { lines +> ['three'] }
EOF
Notice: Compiled catalog for marla.corp.puppetlabs.net in environment production in 0.13
Jira (FACT-1905) Facter networking fact tests fail on redhat 8
Title: Message Title Casey Williams updated an issue Facter / FACT-1905 Facter networking fact tests fail on redhat 8 Change By: Casey Williams Team: Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3263) Architecture Parameter for Package Resource
Title: Message Title Adam Bottchen assigned an issue to Branan Riley Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Adam Bottchen Assignee: Adam Bottchen Branan Riley Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Nick Walker commented on PDB-3526 Re: Add online index rebuild capability to PuppetDB While not native to PuppetDB, we will have pg_repack in Puppet Enterprise with 2018.1.7 and 2019.02 which provides the ability to rebuild indexes online. Closing this as won't fix since we can use a 3rd party tool to solve the issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3526 Add online index rebuild capability to PuppetDB Change By: Nick Walker Labels: cstop10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4233) Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4233 Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4233) Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4233 Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Fix Version/s: PDB 6.2.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4234) Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4234 Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Fix Version/s: PDB 6.2.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4234) Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4234 Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Mikker Gimenez-Peterson commented on BOLT-1094 Re: Bolt Puppetfile install deletes modules in modules directory. That solution seems reasonable to me Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Nick Lewis commented on BOLT-1094 Re: Bolt Puppetfile install deletes modules in modules directory. We should check whether any modules are present that aren't declared in the Puppetfile and refuse to do any work unless something like --force is specified. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4234) Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4234 Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4233) Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4233 Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1900) The system32 fact can be confused by an empty directory
Title: Message Title Branan Riley updated an issue Facter / FACT-1900 The system32 fact can be confused by an empty directory Change By: Branan Riley Release Notes Summary: Facter now correctly returns the path to system32 on 64-bit systems when a user has manually created the "sysnative" folder. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1900) The system32 fact can be confused by an empty directory
Title: Message Title Branan Riley updated an issue Facter / FACT-1900 The system32 fact can be confused by an empty directory Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Mikker Gimenez-Peterson commented on BOLT-1094 Re: Bolt Puppetfile install deletes modules in modules directory. I see now in the docs of the windows section that if you add the module to the Puppetfile it won't delete it. This seems like harsh punishment for not noticing this. Can we have a warning saying that modules will be deleted unless this is added to puppetfile? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Mikker Gimenez-Peterson updated an issue Puppet Task Runner / BOLT-1094 Bolt Puppetfile install deletes modules in modules directory. Change By: Mikker Gimenez-Peterson Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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 (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Mikker Gimenez-Peterson updated an issue Puppet Task Runner / BOLT-1094 Bolt Puppetfile install deletes modules in modules directory. Change By: Mikker Gimenez-Peterson Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Mikker Gimenez-Peterson created an issue Puppet Task Runner / BOLT-1094 Bolt Puppetfile install deletes modules in modules directory. Issue Type: Improvement Assignee: Unassigned Created: 2019/01/16 2:49 PM Priority: Normal Reporter: Mikker Gimenez-Peterson Hello! This tutorial: https://puppet.com/docs/bolt/1.x/applying_manifest_blocks.html#task-6111 Says to create your new "profiles" module in ~/.puppetlabs/bolt/modules But bolt seems to delete any files created in ~/.puppetlabs/bolt/modules when you do a bolt puppetfile install. ❰mikker❙~/.puppetlabs/bolt/modules❱✔≻ mkdir test_module ❰mikker❙~/.puppetlabs/bolt/modules❱✔≻ ls postgresql test_module ❰mikker❙~/.puppetlabs/bolt/modules❱✔≻ cd .. ❰mikker❙~/.puppetlabs/bolt❱✔≻ bolt puppetfile install Successfully synced modules from /Users/mikker/.puppetlabs/bolt/Puppetfile to /Users/mikker/.puppetlabs/bolt/modules ❰mikker❙~/.puppetlabs/bolt❱✔≻ ls -al modules/ total 0 drwxr-xr-x 3 mikker staff 96 Jan 16 14:39 . drwxr-xr-x 5 mikker staff 160 Jan 16 14:31 .. drwxr-xr-x 21 mikker staff 672 Jan 10 09:22 postgresql Add Comment
Jira (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Melissa Amos Labels: beginner docs_reviewed help_wanted Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4118) Test openjdk 11 in travis
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4118 Test openjdk 11 in travis Change By: Austin Blatt Summary: Test openjdk 11 in travis (perhaps instead of 9/10) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1905) Facter networking fact tests fail on redhat 8
Title: Message Title Casey Williams moved an issue Facter / FACT-1905 Facter networking fact tests fail on redhat 8 Change By: Casey Williams Key: PA FACT - 2399 1905 Project: Puppet Agent Facter Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4254) Update "end of life" information on the relevant branches
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4254 Update "end of life" information on the relevant branches Change By: Rob Browning e . g . https://github . com/puppetlabs/puppetdb/commit/b6b99b0c876e25fe3def5a3d36e3ef6dd2bd6d32... wonder if this might nudge us toward adding 6.0-doc style branches for the publishing infrastructure to use, for branches where the tip docs aren't accurate/appropriate now (but we need to add this commit). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4254) Update "end of life" information on the relevant branches
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4254 Update "end of life" information on the relevant branches Issue Type: Improvement Assignee: Unassigned Created: 2019/01/16 1:00 PM Priority: Normal Reporter: Rob Browning ...wonder if this might nudge us toward adding 6.0-doc style branches for the publishing infrastructure to use, for branches where the tip docs aren't accurate/appropriate now (but we need to add this commit). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9448) Improvements to Label Provider
Title: Message Title
Erwin Hom updated an issue
Puppet / PUP-9448
Improvements to Label Provider
Change By:
Erwin Hom
Each String Resource should This ticket will contain a complete phrase so some issues that it can will need to be localized.Reviewing `puppet.pot` addressed in Transifex (Localization Tool) reveals the following Text Fragmentation: label provider and string resources that rely on it. {noformat}one of %{expected) are{noformat} {noformat}%{expected} The label_provider is {noformat} localed here: *BAD_SLICE_KEY_TYPE* Content Source: * [https://github.com/puppetlabs/puppet/blob/master/ locales lib /puppet /pops/label_provider . pot#L5096 rb ] * This file should be referred to when making decisions just in case: [https://github.com/puppetlabs/puppet/blob/master/ locales lib /puppet /pops/model/model_label_provider . pot#L5100 rb ]Point of Usage: * [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/issues.rb#L433]
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9448) Improvements to Label Provider
Title: Message Title Erwin Hom updated an issue Puppet / PUP-9448 Improvements to Label Provider Change By: Erwin Hom This ticket will contain some issues that will need to be addressed in the label provider and string resources that rely on it.The label_provider is localed here: [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/label_provider.rb]This file should be referred to when making decisions just in case:[https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/model/model_label_provider.rb]Point of Usage: * [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/issues.rb #L433 ] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9448) Improvements to Label Provider
Title: Message Title Erwin Hom updated an issue Puppet / PUP-9448 Improvements to Label Provider Change By: Erwin Hom Summary: CLONE - Text Fragmentation: Incomplete phrases in string resources Improvements to Label Provider Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9448) Improvements to Label Provider
Title: Message Title Erwin Hom updated an issue Puppet / PUP-9448 Improvements to Label Provider Change By: Erwin Hom Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title
Trevor Vaughan commented on PUP-523
Re: Make it possible to declare classes, defines and functions (and more) as private to a module
Exactly, yes. Also:
<| Foo |> {
y => 20
} # error, y is a constant
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title
Henrik Lindberg commented on PUP-523
Re: Make it possible to declare classes, defines and functions (and more) as private to a module
Ah, so you mean not even giving it in a resource instantiation _expression_? Example where "CONSTANT" is an imaginary marker declaring $y to be a constant.
define foo($x, CONSTANT $y = 10) { ... }
foo { 'a foo':
x => 'hello', # ok
y => 20, # error, y is a constant
}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg I was thinking for defined types as well. It would prevent anything from ever modifying that parameter. So ASL would ignore it, resource collectors would ignore it, etc... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Henrik Lindberg commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Trevor Vaughan Do you mean that it would prevent a resource override? IIRC that is the only way (except hackery in Ruby) that would alter already set values in resources (It is already forbidden to alter a class' parameters). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4253) Use fixed refs rather than branch tips for published docs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4253 Use fixed refs rather than branch tips for published docs Change By: Rob Browning ... e.g. tags, so that we won't publish documentation for unreleased features by default. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4253) Use fixed refs rather than branch tips for published docs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4253 Use fixed refs rather than branch tips for published docs Change By: Rob Browning Summary: Use explicit tags fixed refs rather than branch tips for published docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4253) Use explicit tags rather than branch tips for published docs
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4253 Use explicit tags rather than branch tips for published docs Issue Type: Improvement Assignee: Unassigned Created: 2019/01/16 11:55 AM Priority: Normal Reporter: Rob Browning ...so that we won't publish documentation for unreleased features by default. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3471) Support "!=" syntax in PQL
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3471 Support "!=" syntax in PQL Change By: Rob Browning Fix Version/s: PDB 5.2.8 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3471) Support "!=" syntax in PQL
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3471 Support "!=" syntax in PQL Change By: Rob Browning Release Notes Summary: PQL now supports negated `=` and `~` operators, i.e. `!=` and '!~'. Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9449) Puppet limitations on osx-10.14 due to FDA restrictions
Title: Message Title Josh Cooper commented on PUP-9449 Re: Puppet limitations on osx-10.14 due to FDA restrictions Thanks Gheorghe Popescu! Heads up Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9449) Puppet limitations on osx-10.14 due to FDA restrictions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9449 Puppet limitations on osx-10.14 due to FDA restrictions Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9449) Puppet limitations on osx-10.14 due to FDA restrictions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9449 Puppet limitations on osx-10.14 due to FDA restrictions Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9324 Puppet agent run output to differentiate between corrective and intentional change Change By: Melissa Stone Release Notes Summary: Corrective changes in the logs are now explicitely called out as corrective. Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Josh Cooper commented on PUP-9324 Re: Puppet agent run output to differentiate between corrective and intentional change Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a75153e214b8b466b0eed8d3b8df67fcd63a91cb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Melissa Stone commented on PUP-9324 Re: Puppet agent run output to differentiate between corrective and intentional change That works for me, thank you! I'll coordinate this change and update both here and in FM-7682 when we have agent builds in the different streams that contain this change Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-987) Add CLI front end to plan executor
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-987 Add CLI front end to plan executor Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1090) Kick off release pipeline (Bolt 1.10.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1090 Kick off release pipeline (Bolt 1.10.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/16 10:03 AM Due Date: 2019/01/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-16) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1093) Send release announcements (Bolt 1.10.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1093 Send release announcements (Bolt 1.10.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/16 10:03 AM Due Date: 2019/01/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-16) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.10.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.10.0 is now available".
Jira (BOLT-1092) Docs for bolt release (Bolt 1.10.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1092 Docs for bolt release (Bolt 1.10.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/16 10:03 AM Due Date: 2019/01/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-16) Release notes and docs changes for bolt 1.10.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1089) Reconcile git commits, JIRA tickets, and versions (Bolt 1.10.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1089 Reconcile git commits, JIRA tickets, and versions (Bolt 1.10.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/16 10:03 AM Due Date: 2019/01/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1091) Update homebrew-puppet (Bolt 1.10.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1091 Update homebrew-puppet (Bolt 1.10.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/16 10:03 AM Due Date: 2019/01/16 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-16) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1088) Bolt 1.10.0 2019-01-16 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1088 Bolt 1.10.0 2019-01-16 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/01/16 10:02 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.10.0 2019-01-16 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module
Title: Message Title Trevor Vaughan commented on PUP-523 Re: Make it possible to declare classes, defines and functions (and more) as private to a module Henrik Lindberg Just had this thought... how about a Const Data Type that marks a parameter as immutable? It doesn't solve all of the proposed issues but it seems reasonable in terms of the data typing system and understandability. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7644) puppet installing pip rather than pip3 packages using the pip3 provider only on the first run
Title: Message Title Mia Ferguson commented on PUP-7644 Re: puppet installing pip rather than pip3 packages using the pip3 provider only on the first run I am currently having this issue - is there a plan to make this small change or is there a good workaround besides using exec? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Nick Lewis Release Notes Summary: Group names and node aliases in the Bolt inventory can now contain hyphens. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Nick Lewis Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 5_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 6_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9436
Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Change By:
Erik Hansen
Comment:
I've reproduced this now. The user resource in the cached 6.0.4 catalog looks like this:{code:json}"parameters": { "ensure": "present", "password": { "__ptype": "Binary", "__pvalue": "c2VjcmV0X3Bhc3MxMjM=" } },{code}Whereas the 5.5.4 catalog has:{code:json}"parameters": { "ensure": "present", "password": "secret_pass123" },{code}Additional details: When the 5.5.4 applies the 6.0.4 cached catalog there is an error:{noformat}Error: Could not send report: Error 400 on SERVER: Bad Request: The request body is invalid: Could not intern from json: Internal Error: Puppet Context ':loaders' missing{noformat}The catalog applies any changes, but the report isn't sentThere's a similar error if the 6.0.4 agent tries to apply the 6.0.4 cached catalog:{noformat}Error: Cached catalog for hmlilodi28f6x5y.delivery.puppetlabs.net failed: Could not parse JSON data for catalog hmlilodi28f6x5y.delivery.puppetlabs.net: Could not intern from rich_data_json: Internal Error: Puppet Context ':loaders' missing{noformat}In this case the cached catalog cannot be applied and the agent requests a new one.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 6_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 5_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title
Erik Hansen commented on PUP-9436
Re: Exported resources in Puppet 6.x are realized with Binary values from Eyaml
I've reproduced this now. The user resource in the cached 6.0.4 catalog looks like this:
"parameters": {
"ensure": "present",
"password": {
"__ptype": "Binary",
"__pvalue": "c2VjcmV0X3Bhc3MxMjM="
}
},
Whereas the 5.5.4 catalog has:
"parameters": {
"ensure": "present",
"password": "secret_pass123"
},
Additional details: When the 5.5.4 applies the 6.0.4 cached catalog there is an error:
Jira (FACT-1904) facter (leatherman) is slow if nofile ulimit is bigger than default
Title: Message Title Andrey Kolashtov updated an issue Facter / FACT-1904 facter (leatherman) is slow if nofile ulimit is bigger than default Change By: Andrey Kolashtov Facter is slow if nofile ulimit is set to big values like 500. E.g.: # $ ulimit -n 65536 # $ time facter networking > /dev/nullreal 0m0.396suser 0m0.200ssys 0m0.196s # $ ulimit -n 6553600 # $ time facter networking > /dev/nullreal 0m28.003suser 0m12.812ssys 0m15.190s The problem is in [https://github.com/puppetlabs/leatherman/blob/master/execution/src/posix/execution.cc#L318,] leatherman closes all descriptors from stderr to max open file limit before execve (for running _ip link_ or other command) and it takes about 3-4 seconds for 10M descriptors every time when it executes any binary. We use OS Ubuntu 18.04, puppet 6.1.0, facter 3.12.2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from
Jira (FACT-1904) facter (leatherman) is slow if nofile ulimit is bigger than default
Title: Message Title Andrey Kolashtov updated an issue Facter / FACT-1904 facter (leatherman) is slow if nofile ulimit is bigger than default Change By: Andrey Kolashtov Facter is slow if nofile ulimit is set to big values like 500 6553600 . E.g.:$ ulimit -n 65536$ time facter networking > /dev/null real 0m0.396s user 0m0.200s sys 0m0.196s$ ulimit -n 6553600$ time facter networking > /dev/null real 0m28.003s user 0m12.812s sys 0m15.190sThe problem is in [https://github.com/puppetlabs/leatherman/blob/master/execution/src/posix/execution.cc#L318,] leatherman closes all descriptors from stderr to max open file limit before execve (for running _ip link_ or other command) and it takes about 3-4 seconds for 10M descriptors every time when it executes any binary. We use OS Ubuntu 18.04, puppet 6.1.0, facter 3.12.2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from
Jira (FACT-1904) facter (leatherman) is slow if nofile ulimit is bigger than default
Title: Message Title Andrey Kolashtov created an issue Facter / FACT-1904 facter (leatherman) is slow if nofile ulimit is bigger than default Issue Type: Bug Affects Versions: FACT 3.12.3 Assignee: Unassigned Created: 2019/01/16 9:15 AM Priority: Normal Reporter: Andrey Kolashtov Facter is slow if nofile ulimit is set to big values like 500. E.g.: ulimit -n 65536 time facter networking > /dev/null real 0m0.396s user 0m0.200s sys 0m0.196s ulimit -n 6553600 time facter networking > /dev/null real 0m28.003s user 0m12.812s sys 0m15.190s The problem is in https://github.com/puppetlabs/leatherman/blob/master/execution/src/posix/execution.cc#L318, leatherman closes all descriptors from stderr to max open file limit before execve (for running ip link or other command) and it takes about 3-4 seconds for 10M descriptors every time when it executes any binary. We use OS Ubuntu 18.04, puppet 6.1.0, facter 3.12.2.
Jira (PUP-5216) Add Password Expiration for Windows User management
Title: Message Title Enis Inan commented on PUP-5216 Re: Add Password Expiration for Windows User management Geoff Nichols I'll move it over to Blocked since I won't be looking at this for some time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4234) Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4234 Bump pe-puppetdb-extensions to ezbake >= 1.9.1 to pull in TasksMax Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4233) Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4233 Bump puppetdb to ezbake >= 1.9.1 to pull in TasksMax Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9449) Puppet limitations on osx-10.14 due to FDA restrictions
Title: Message Title Gheorghe Popescu commented on PUP-9449 Re: Puppet limitations on osx-10.14 due to FDA restrictions Josh Cooper please add labels/components or other things that are needed. Let me know if anyone has questions about this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9449) Puppet limitations on osx-10.14 due to FDA restrictions
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-9449 Puppet limitations on osx-10.14 due to FDA restrictions Issue Type: Task Assignee: Unassigned Created: 2019/01/16 6:22 AM Priority: Normal Reporter: Gheorghe Popescu Puppet for OSX-10.14 will come with some limitations due to OSX-10.14 "Full Disk Access" restrictions. For now we have confirmed(running the puppet acceptance suite) that: - managing users and groups using puppet is not working properly. Other issues that we are not aware of might appear when using puppet without being whitelisted in FDA. You can find information about FDA here: https://macpaw.com/how-to/full-disk-access-mojave Whitelisting an app for FDA can be done in two official ways: Manual by the owner of the Macbook by clicking on the Apple icon > System Preferences > Go to Security & Privacy > Click on the privacy tab > Click Full Disk Access section in the side bar > Click on the “+” and add the path to the puppet executable: . Link: https://support.intego.com/hc/en-us/articles/360016683471-Enable-Full-Disk-Access-in-macOS-Mojave Automated using Privacy Preferences Control Profiles (PPCP) and a Mobile Device Management (MDM) Server.** This ticket can be used to track other issue that we might find.
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title David Mallon commented on PUP-9324 Re: Puppet agent run output to differentiate between corrective and intentional change Hey Melissa Stone, first off, thanks for the heads up on this change, the Modules team can plan some testing around this to make sure things are good on our side. If possible we would like to : 1. Get access to a nightly Agent build with the change 2. Modules team will test against each of our supported modules 3. If there are issues in any modules we will merge our test fixes to master - no need for a release 4. Let you guys know when we are good to go 5. You guys can proceed with the Agent release with that change. Does that work for you guys? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Henrik Lindberg commented on PUP-9436 Re: Exported resources in Puppet 6.x are realized with Binary values from Eyaml The PR to hiera-eyaml has now been merged (https://github.com/voxpupuli/hiera-eyaml/pull/274). Waiting for a release. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
