Jira (PUP-5491) The "client_data" Directory Permissions Incorrect After Installation
Title: Message Title Glenn Sarti commented on PUP-5491 Re: The "client_data" Directory Permissions Incorrect After Installation Josh Cooper Was that under cygwin or local cmd.exe session for the install ? 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-8771) Write integration/acceptance tests for NTFS permissions for PUP-6729
Title: Message Title Glenn Sarti commented on PUP-8771 Re: Write integration/acceptance tests for NTFS permissions for PUP-6729 So...it looks like PUP-6729 may not be as big an issue right now. Going to put this on hold until we can prove that PUP-6729 is indeed still an issue. Raised WIN-160 to track the work. 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-521) I want to escalate with a non-sudo command
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command Change By: Alex Dreyer Assignee: Alex Dreyer 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-8857) Remove type/provider code from puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8857 Remove type/provider code from puppet Change By: Josh Cooper Fix Version/s: PUP 6.0.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 (PUP-8857) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8857 Re: Remove type/provider code from puppet Merged to master in https://github.com/puppetlabs/puppet/commit/8562b2704ba1febf207d409a04ef025e27e3c1c1 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-8898) Change default input_method for Task object type
Title: Message Title Cas Donoghue created an issue Puppet / PUP-8898 Change default input_method for Task object type Issue Type: Improvement Assignee: Unassigned Created: 2018/05/29 4:18 PM Priority: Normal Reporter: Cas Donoghue When a Task is run using BOLT puppet code is used to parse the task metadata. If `input_method` is not defined the default is set to `both`. https://github.com/puppetlabs/puppet/blob/a5385a74bdf7eb754dafed1f557563d97eb68bcd/lib/puppet/pops/pcore.rb#L74 In the case where Bolt is used to run a task the default `input_method` should be set based on the combination of programming language the task is implemented in and the transport. For example if a powershell task is run over winrm the default `input_method` should be `powershell`. Proposed change: Puppet sets default value for `input_method` to `nil` when `input_method` is not defined. The responsibility for setting appropriate `input_method` for running tasks in Bolt will be handled in the various transport implementations. Relates to BOLT-536 https://tickets.puppetlabs.com/browse/BOLT-536 Add Comment
Jira (PUP-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes assigned an issue to Ethan Brown Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Assignee: Ethan Brown 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Alex Dreyer commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode Bolt currently will 'just fail' if no password is provided after sudo asks for a password. Is there a specific failure case you're running into where this isn't working? 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-521) I want to escalate with a non-sudo command
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command Change By: Alex Dreyer Assignee: Alex Dreyer 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-533) Move facts to an external module
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Lucy Wyman Assignee: Lucy Wyman 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-8897) check_manage_home useradd provider needs to add -M on Debian
Title: Message Title
Kevin Paulisse created an issue
Puppet / PUP-8897
check_manage_home useradd provider needs to add -M on Debian
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/05/29 2:40 PM
Priority:
Normal
Reporter:
Kevin Paulisse
Regarding the code here: https://github.com/puppetlabs/puppet/blob/1c77bfb8961587ddf5399cd4a70fc908cac6a6ec/lib/puppet/provider/user/useradd.rb#L127-L135 There is an edge case that is missed. If force_local is true and manage_home is false, then "-M" should be added as a command line argument on Debian Jessie (and possibly others). If this is not in place, a bug occurs as follows when running on Debian Jessie (and possibly others). First manually create `/home/bob` (like pam_mkhomedir might do) and then try to add `bob` with a resource like this, and it will fail: user { 'bob': force_local => true, manage_home => false, ... Other Params ... }
Add Comment
Jira (PUP-4684) windows file resource doesn't grant group full permissions
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-4684
windows file resource doesn't grant group full permissions
Change By:
Ethan Brown
If you grant {{rwx}} permission to a file's group:{code:puppet} user { 'foo': ensure => present, managehome => false, password => 'foo1234!', groups => ['Users'],} file { 'C:\foo': ensure => directory, owner => 'foo', group => 'Administrators', mode => '0770',}file { 'C:\foo\foo.bat': ensure => file, content => 'echo "hello"'}{code}The windows provider does not map that to full control. Instead the group receives a subset of permissions. More specifically, any file contained in the directory being managed is not executable:{noformat}C:\> puppet apply foo.ppNotice: Compiled catalog for win-qp47voha2p4.solar.lan in environment production in 0.50 secondsNotice: /Stage[main]/Main/File[C:\foo]/ensure: createdNotice: /Stage[main]/Main/File[C:\foo\foo.bat]/ensure: defined content as '{md5}84b8f5c3577073eac07c9e9915e5b8c9'Notice: Applied catalog in 0.06 secondsC:\> icacls c:\fooc:\foo WIN-QP47VOHA2P4\ albert foo :(F) BUILTIN\Administrators:(RX,W,DC) Everyone:(Rc,S,RA) NT AUTHORITY\SYSTEM:(F) CREATOR OWNER:(CI)(IO)(F) CREATOR GROUP:(CI)(IO)(RX,W,DC) CREATOR OWNER:(OI)(IO)(R,W,D,WDAC,WO,DC) CREATOR GROUP:(OI)(IO)(R,W,DC)Successfully processed 1 files; Failed processing 0 filesC:\> icacls C:\foo\foo.batC:\foo\foo.bat BUILTIN\Administrators:(I)(R,W,D,WDAC,WO,DC) WIN-QP47VOHA2P4\None:(I)(R,W,DC){noformat}
Add Comment
Jira (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Michael Smith Assignee: Nick Lewis Michael Smith 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-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Assignee: Melissa Stone Josh Cooper 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title
Nick Lewis created an issue
Puppet / PUP-8896
Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/05/29 1:23 PM
Priority:
Normal
Reporter:
Nick Lewis
As part of the work for PUP-4242, validation was introduced to check that the name of a definition (class, define, function, type, plan) matches the path to the file it's in. That code works by searching up the ancestry until it finds a directory named one of manifests, functions, types, or plans, and assuming the parent of that directory must be the module. That works fine, so long as there isn't a nested directory with one of those names. In that case, the manifest fails validation because its name (though correct) doesn't match what was expected (incorrect). For example:
# modulename/manifests/foo/bar/types/baz.pp
class modulename::foo::bar::types::baz() { }
This manifest has the correct name, but the validation thinks the module name is bar and that the path to the file is bar/types/baz.pp. Thus, it believes the correct name for the entity defined in the manifest ought to be bar::baz, causing an error.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Ludovic Jerome commented on FACT-1847 Re: Implement "cloud" fact Azure identification for Windows platform Hello, I don't know if this could help but there is a azure metadata service now : https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service 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-8895) CD4PE does not correctly recognize failed orchestrator jobs
Title: Message Title Reid Vandewiele created an issue Puppet / PUP-8895 CD4PE does not correctly recognize failed orchestrator jobs Issue Type: Bug Assignee: Unassigned Created: 2018/05/29 12:23 PM Priority: Normal Reporter: Reid Vandewiele Problem description See deployments 19 and 20. See Jobs 6-9. E.g. https://10.32.174.120/#/run/jobs/6. Reproduction / credentials cd4pe url: http://10.32.164.56:8080/ login: r...@puppet.com password: puppetlabs Gitlab url: https://10.32.174.121/cd4pe/control-repo login: root password: puppetlabs PE url: https://10.32.174.120/ login: admin password: puppetlabs ssh login to PE server host: 10.32.174.120 login: root password: puppetlabs Add Comment This message
Jira (PUP-8894) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland created an issue Puppet / PUP-8894 Add deprecation warnings for manifests declaring things in wrong namespace Issue Type: Improvement Assignee: Kris Bosland Created: 2018/05/29 11:59 AM Fix Versions: PUP 5.5.z Priority: Normal Reporter: Kris Bosland This should add deprecation warnings for the problems described in PUP-1434 so that strict naming can be enforced. It may also be supported as a --strict_naming option that will error instead of just warn. A better specification than the text in PUP-1434 is also needed (it is a bit dated and there are now also additional artifacts being loaded). Add Comment
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace This ticket will now be for the errors we want in Puppet 6.0.0, and a new ticket for deprecation in 5.5.x is PUP-7426(https://tickets.puppetlabs.com/browse/PUP-7426). 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-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland updated an issue Puppet / PUP-4242 Add errors for manifests declaring things in wrong namespace Change By: Kris Bosland Summary: Add deprecation warnings errors for manifests declaring things in wrong namespace 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-548) Generate function reference docs for core plan language functions automatically
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Issue Type: Task Assignee: Unassigned Created: 2018/05/29 11:50 AM Priority: Normal Reporter: Alex Dreyer Reference information about the plan language should be autogenerated with puppet strings. In scope: Update plan language functions in boltlib to have strings based documentation Create a skeleton template(s) for documentation pages Create rake task to generate docs Update templates to DITA(kate) Update writing plans page to include less reference info and links Out of scope: reference docs for datatypes reference docs for modules other than boltlib Questions: How should output be structured into files? What templating language should we use? Do we need links in generated content
Jira (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Michael Smith Assignee: Michael Smith 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-547) Finish plans when using the pcp transport.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-547 Finish plans when using the pcp transport. Issue Type: New Feature Assignee: Unassigned Created: 2018/05/29 10:42 AM Priority: Normal Reporter: Alex Dreyer currently bolt does not finish plans to avoid unnecessary error logging with ORCH-2224 This work is blocked on the PE 2018.1.1 release or should be feature flagged. This work should be tested by updating the orchestrator acceptance tests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8768) Ability to export puppet Task output to CSV/Text file.
Title: Message Title max buehler commented on PUP-8768 Re: Ability to export puppet Task output to CSV/Text file. Specifically for the puppet enterprise console is what I was referring to. Not puppet task via command line. 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Kenn Hussey commented on FACT-1851 Re: Linux networking resolver doesn't collect DHCP information under systemd-networkd Casey Williams please provide release notes for this issue if needed, thanks! 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-7600) Deprecate built-in LDAP Node Terminus
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7600 Deprecate built-in LDAP Node Terminus Change By: Craig Gomes Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-7600) Deprecate built-in LDAP Node Terminus
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7600 Deprecate built-in LDAP Node Terminus Change By: Craig Gomes Sprint: Platform Core Hopper KANBAN 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-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7407 Add deprecation warning to Puppet::Util.absolute_path? Change By: Craig Gomes Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-7534) Deprecate using file checksums in `content` property
Title: Message Title Kenn Hussey commented on PUP-7534 Re: Deprecate using file checksums in `content` property Jennifer Solman please provide release notes for this issue if needed, thanks! 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-8568) Extract cron type/provider into a module
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8568 Extract cron type/provider into a module Change By: Jorie Tappa Assignee: Jorie Tappa 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-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Craig Gomes Fix Version/s: PUP 5.5.x Fix Version/s: PUP 6.0.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 (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Craig Gomes Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 5.5.x 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-503) Use local config automatically to embed bolt in a project
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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-523) I want to install modules with bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: Michael Smith Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby (we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions:1. pmt is too broken an unmaintained to add support for2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo(task-modules)3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master.4. r10k is cryptic a cryptic command name and should be hidden from new users.Solution:Bolt should be packaged with the r10k gem but not expose the r10k commandBolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy.Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode.Questions:What should the command be?Should bolt become more opinionated on where code lives outside of the context of a boltdir? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: Michael Smith Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby(we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions:1. pmt is too broken an unmaintained to add support for2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo(task-modules)3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master.4. r10k is cryptic a cryptic command name and should be hidden from new users.Solution:Bolt should be packaged with the r10k gem but not expose the r10k commandBolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy.Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode.Questions:What should the command be?Should bolt become more opinionated on where code lives outside of the context of a boltdir? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-1965) Clients are hung when server has intermittent service
Title: Message Title Josh Cooper commented on PUP-1965 Re: Clients are hung when server has intermittent service We've added a watchdog/supervisor to the agent (in PUP-7517), but it not activated by default in 5.x. I recommend setting runtimeout to a non-infinite value to activate it. Also note you may want to change http_read_timeout to a non-infinite value. We will be changing the default value of both settings in 6.0 in PUP-8683. 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-8893) external, executable facts via pluginsync get executable flag removed
Title: Message Title Branan Riley moved an issue Puppet / PUP-8893 external, executable facts via pluginsync get executable flag removed Change By: Branan Riley Key: FACT PUP - 1856 8893 Project: Facter Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Michael Smith commented on BOLT-546 Re: mktemp is not available on all platform (AIX specifically) https://stackoverflow.com/questions/10224921/how-to-create-a-temporary-file-with-portable-shell-in-a-secure-way has some suggestions on what a fallback could be. 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-8710) Smarter cached catalogs
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8710 Smarter cached catalogs Change By: Craig Gomes Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-8770) Puppet resource service status should be more than binary
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Craig Gomes Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-8889) Puppet Agent : cannot add certificates for HTTPS
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8889 Puppet Agent : cannot add certificates for HTTPS Change By: Craig Gomes Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-8774) puppet device does not use locking
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8774 puppet device does not use locking Change By: Craig Gomes Team: Modules 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-521) I want to escalate with a non-sudo command
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Michael Smith commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode Specifically you'll configure escalation-command: [sudo, -n]. 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title David Kramer assigned an issue to Eoin McQuillan Puppet Task Runner / BOLT-534 Request for ability to run tasks with escalated privileges in non interactive mode Change By: David Kramer Assignee: Eoin McQuillan 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-8892) puppet reporting fails on Fedora, Errors(Could not write/send report: undefined method `split' for :ensure:Symbol)
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8892 puppet reporting fails on Fedora, Errors(Could not write/send report: undefined method `split' for :ensure:Symbol) Change By: Craig Gomes Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-521) I want to escalate with a non-sudo command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-521
I want to escalate with a non-sudo command
Change By:
Alex Dreyer
Some users use a command other than sudo to escalate privileges. Bolt should support running a different command for escalationIn scope:{{escalation-command}} ssh and local transport config option. It should accept an array of arguments to the command.{{escalation-command}} gets used in place the sudo wrapper : { { noformat} {noformat } } out of scope:interactive password support with escalation-command.
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
Jira (BOLT-521) I want to escalate with a non-sudo command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-521
I want to escalate with a non-sudo command
Change By:
Alex Dreyer
Some users use a command other than sudo to escalate privileges. Bolt should support running a different command for escalationIn scope:{{escalation-command}} ssh and local transport config option. It should accept an array of arguments to the command.{{escalation-command}} gets used in place the sudo wrapper:{noformat} sudo -n echo whoami {noformat}out of scope:interactive password support with escalation-command.
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
Jira (BOLT-521) I want to escalate with a non-sudo command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-521
I want to escalate with a non-sudo command
Change By:
Alex Dreyer
Some users use a command other than sudo to escalate privileges. Bolt should support running a different command for escalationIn scope:{{escalation-command}} ssh and local transport config option. It should accept an array of arguments to the command.{{escalation-command}} gets used in place the sudo wrapper {{ }} out of scope:interactive password support with escalation-command.
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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title David Kramer commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode We will address this request with the fix for BOLT-521. 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-521) I want to escalate with a non-sudo command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-521
I want to escalate with a non-sudo command
Change By:
Alex Dreyer
Some users use a command other than sudo to escalate privileges. Bolt should support running a different command for escalation In scope:{{escalation-command}} ssh and local transport config option. It should accept an array of arguments to the command.{{escalation-command}} gets used in place the sudo wrapper {{ out of scope:interactive password support with escalation-command.
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-521) I want to escalate with a non-sudo command
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command Change By: Michael Smith Sprint: Bolt Ready for Grooming 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Alex Dreyer commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode I don't know that we need a CLI flag for this. I think we could also discuss doing more generic escalation command support to solve this use case. 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-533) Move facts to an external module
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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-399) Update fact gathering task to leverage cross-platform support
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-399 Update fact gathering task to leverage cross-platform support Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-534 Request for ability to run tasks with escalated privileges in non interactive mode Change By: Alex Dreyer On discovery we use bolt to run tasks and use the --run-as to escalate the privileges upon failure. Our use case is non interactive so we would like to be able to use sudo with the -n option and then if passwordless sudo isn't setup bolt would just fail.It would be then up to uses users to setup their sudo as they should. Our credentials may just be a key so we may not (and probably won't) have access to a password. 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 (BOLT-533) Move facts to an external module
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-533
Move facts to an external module
Change By:
Michael Smith
The facts module implements several improvements over facter_task for Bolt users, and we feel is a better name long-term for this module. It's also in-use by Bolt Plans. With the move to use Bolt with PE more, we want the facts module to be available when running Plans with PE as well (requiring it be a module you can install). 1. make plan for updating tasks on forge with cross platform implementation2. update facter_task module with Create a new improvements3. when releasing breaking changes to tasks use opportunity to change name of module from facter_task to called {{ facts This ticket will be for updating facter_task module with improvements from }} containing the facts task tasks and plans currently in Bolt, with updates from bolt BOLT-399 . We plan to address item (3) before releasing these changes continue maintaining facter_task as well for the duration if its use in PE, but deprecate it on the Forge in favor of {{facts}} .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-533) Move facts to an external module
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Michael Smith The facts module implements several improvements over facter_task for Bolt users , and we feel is a better name long-term for this module. It's also in-use by Bolt Plans. With the move to use Bolt with PE more, we want the facts module to be available when running Plans with PE as well (requiring it be a module you can install).1. make plan for updating tasks on forge with cross platform implementation2. update facter_task module with new improvements3. when releasing breaking changes to tasks use opportunity to change name of module from facter_task to factsThis ticket will be for updating facter_task module with improvements from the facts task from bolt. We plan to address item (3) before releasing these changes. 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
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8597 Modify rich data serialization to use shorter tags instead of __pcore_type__ Change By: Henrik Lindberg Release Notes Summary: The earlier rich data experimental --rich_data format used the tags __pcore_type__ and __pcore_value__, these are now shortened to __ptype and __pvalue respectively. If you are using this experimental feature and have stored serializations you need to change them or write them again with the updated version. 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-1737) Add "disks" and "partitions" facts on FreeBSD
Title: Message Title Jonathan Morris assigned an issue to Unassigned Facter / FACT-1737 Add "disks" and "partitions" facts on FreeBSD Change By: Jonathan Morris Assignee: Jonathan Morris 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-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely commented on BOLT-545 Re: upload/script/task doesn't work with --run-as on AIX (and possibly others) FYI, OSX has the same chown syntax, per the man page: SYNOPSIS chown [-fhv] [-R [-H | -L | -P]] owner[:group] file ... chown [-fhv] [-R [-H | -L | -P]] :group file ... However, it doesn't give a syntax error (like on AIX), it just doesn't do the "primary group" thing... # chown tmcneely: testfile # ls -l testfile -rw-r--r-- 1 tmcneely wheel 0 May 29 09:21 testfile Add Comment
Jira (BOLT-545) upload/script/task doesn't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely updated an issue Puppet Task Runner / BOLT-545 upload/script/task doesn't work with --run-as on AIX (and possibly others) Change By: Tommy McNeely Summary: upload/script/task don doesn 't work with --run-as on AIX (and possibly others) 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely updated an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Change By: Tommy McNeely Method Found: Needs Assessment Customer Feedback 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely commented on BOLT-546 Re: mktemp is not available on all platform (AIX specifically) Workaround --tmpdir /tmp 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Tommy McNeely created an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Issue Type: Bug Assignee: Unassigned Created: 2018/05/29 8:12 AM Environment: AIX 7.1 TL4 Priority: Normal Reporter: Tommy McNeely We recently were trying to run a "script" to install bash on AIX (which is not as simple as "yum install bash") and noticed that it was trying to run "mktemp" to make a temporary directory to upload the 'random' filename of the script to. While I appreciate not creating predictable temporary directories, we should probably use a more portable mechanism, or at least test for its existence (similar to how the PE install.bash does). Add Comment
Jira (BOLT-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Tommy McNeely commented on BOLT-545 Re: upload/script/task don't work with --run-as on AIX (and possibly others) Alternatively, you can just remove the ":" because the group ownership of the file matching the run-as user is not likely to really matter. 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-1519) mountpoints fact does not show mounts on nfs
Title: Message Title
Andrey Khomyakov commented on FACT-1519
Re: mountpoints fact does not show mounts on nfs
I am no coder, but the issue was there and I just wrote a custom fact to solve the problem at hand a few days after I opened this bug.
# nfs_mountpoints.rb
Facter.add('nfs_mountpoints') do
setcode do
# Define nfs_mountpoints as hash
nfs_mountpoints = {}
# Execute shell command with timeout to prevent hung puppet agent
begin
# List all mounted volumes with FS time NFS. Multiple mounts will show up on different lines. \n is end of line and splits string into array.
# Iterate through the list of mounted NFS volumes taking the index of array entry
Facter::Core::Execution.execute('/bin/mount | /bin/grep nfs', :timeout => 5).split("\n").each do |nfs_mountpoint_entry|
# Initialize temporary hash variable to build a sub hash for our final reply
nfs_mountpoint_entry_hash = {}
Jira (PDOC-213) Add support for @note tag
Title: Message Title Nick Miller commented on PDOC-213 Re: Add support for @note tag Referencing @note from the style guide should be removed until this ticket is completed. https://puppet.com/docs/puppet/5.5/puppet_strings_style.html#classes-and-defined-types 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-1519) mountpoints fact does not show mounts on nfs
Title: Message Title Thomas Hufschmidt updated an issue Facter / FACT-1519 mountpoints fact does not show mounts on nfs Change By: Thomas Hufschmidt Affects Version/s: FACT 3.6.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-1519) mountpoints fact does not show mounts on nfs
Title: Message Title Thomas Hufschmidt commented on FACT-1519 Re: mountpoints fact does not show mounts on nfs I know is is quite old, but I recently stumbled upon this myself after switching from my custom mounts fact to the "new" facter mounpoints facts. This is a really annoying behaviour, that seems to be related to this issue: https://tickets.puppetlabs.com/browse/FACT-1482 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.
