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 much current thinking is to; 1. Use and integration test 2. Mock the appropriate Puppet settings and do a puppet apply via the apply application 3. Test that the permissions are "as expected" Repeat these tests for Admin and non-Admin users 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 Looks like I can skip the stub config file in the dest dir too @ECHO OFF RD "C:\Programdata\Puppetlabs" /s/q RD "C:\foo" /s/q MD "C:\foo" icacls C:\foo /inheritance:r /grant Administrators:(OI)(CI)F /grant SYSTEM:(OI)(CI)F ECHO [main] > C:\puppet.conf ECHO codedir=$confdir/code >> C:\puppet.conf ECHO logdir=$vardir/log >> C:\puppet.conf ECHO rundir=$vardir/run >> C:\puppet.conf puppet apply --confdir C:\foo --config
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 I have something that may be able to be patched together; Using the following batch script, I can get puppet to use an entirely different filesystem location for settings etc; @ECHO OFF REM Not really required but useful to detect if Puppet is creating new directories on you RD "C:\Programdata\Puppetlabs" /s/q RD "C:\foo" /s/q MD "C:\foo" icacls C:\foo /inheritance:r /grant Administrators:(OI)(CI)F /grant SYSTEM:(OI)(CI)F ECHO [main] > C:\foo\puppet.conf ECHO codedir=$confdir/code >> C:\foo\puppet.conf ECHO logdir=$vardir/log >> C:\foo\puppet.conf ECHO rundir=$vardir/run >> C:\foo\puppet.conf
Jira (PUP-8772) Using --confdir doesn't redirect other default directories
Title: Message Title Glenn Sarti commented on PUP-8772 Re: Using --confdir doesn't redirect other default directories Ok, so I forgot about -vardir But even then, I still needed to redirect codedir, logdir and rundir using a minimal puppet.conf ECHO [main] > C:\foo\puppet.conf ECHO codedir=$confdir/code >> C:\foo\puppet.conf ECHO logdir=$vardir/log >> C:\foo\puppet.conf ECHO rundir=$vardir/run >> C:\foo\puppet.conf Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8772) Using --confdir doesn't redirect other default directories
Title: Message Title Glenn Sarti created an issue Puppet / PUP-8772 Using --confdir doesn't redirect other default directories Issue Type: Bug Affects Versions: PUP 5.5.1 Assignee: Unassigned Created: 2018/05/22 7:29 PM Priority: Normal Reporter: Glenn Sarti Puppet Version: 5.5.1 Puppet Server Version: N/A OS Name/Version: Windows 10 - 1803 Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: When using the --confdir parameter the default locations for some directories are changed but not all. Repro On a fresh Windows node, download puppet agent Do NOT create a config file under c:\foo Run puppet config print --confdir C:\foo The following is output (I've removed any non-filebased settings) PS C:\Users\Administrator> puppet config print --confdir c:\foo agent_catalog_run_lockfile = C:/ProgramData/PuppetLabs/puppet/cache/state/agent_catalog_run.lock agent_disabled_lockfile =
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 Possible technical hurdles; Getting LOCALSYSTEM to run tests on Appveyor 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 assigned an issue to Glenn Sarti Puppet / PUP-8771 Write integration/acceptance tests for NTFS permissions for PUP-6729 Change By: Glenn Sarti Assignee: Glenn Sarti 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 created an issue Puppet / PUP-8771 Write integration/acceptance tests for NTFS permissions for PUP-6729 Issue Type: Task Assignee: Unassigned Created: 2018/05/22 6:29 PM Environment: Requires a Windows host Priority: Normal Reporter: Glenn Sarti In order to fix PUP-6729 it will need a series of failing tests for the scenarios described in the ticket. This issue will track the work to create adequate test coverage to show that PUP-6729 can be resolved. It will be preferred to add unit/integration tests as opposed to acceptance tests Add Comment
Jira (PUP-8668) Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver
Title: Message Title Kyle Harrington commented on PUP-8668 Re: Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver If you came here looking for a solution to the above error as i did: Error while evaluating a Function Call, undefined method `top_of_stack' for Puppet::Pops::PuppetStack:Module I can confirm that in my env my puppet master servers' agent's were updated and holding on to the cache as described. However, Restarting the server DID CORRECT the issue for me. Worth a shot. Good luck 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-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Branan Riley updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Branan Riley Labels: cloud windows windows-parity 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-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Sprint: Windows 2018-05-30 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 (HI-602) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Branan Riley updated an issue Hiera / HI-602 Migrate gemspec info in project_data.yaml to the .gemspec file Change By: Branan Riley Sprint: Platform OS 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 (FACT-1827) AIX hardwaremodel (os -> hardware) fact is non-standard
Title: Message Title Branan Riley commented on FACT-1827 Re: AIX hardwaremodel (os -> hardware) fact is non-standard We're evaluating this as a breaking change for Facter 4. If we decide to take it on, it will be added to FACT-1628 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-1497) system_uptime fact only updates every minute on AIX
Title: Message Title Branan Riley updated an issue Facter / FACT-1497 system_uptime fact only updates every minute on AIX Change By: Branan Riley Labels: aix aix-parity solaris solaris-parity 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-1497) system_uptime fact only updates every minute on AIX
Title: Message Title Branan Riley updated an issue Facter / FACT-1497 system_uptime fact only updates every minute on AIX Change By: Branan Riley Summary: system_uptime fact only updates every minute on Solaris and AIX 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-532) Bolt no longer prints completion message when plan doesn't explicitly return a result
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-532 Bolt no longer prints completion message when plan doesn't explicitly return a result Change By: Michael Smith Assignee: 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 (FACT-1855) Summer 2018 AIX Facter fixes
Title: Message Title Branan Riley created an issue Facter / FACT-1855 Summer 2018 AIX Facter fixes Issue Type: Epic Assignee: Unassigned Created: 2018/05/22 2:43 PM Priority: Normal Reporter: Branan Riley This is a constrained collection of easy AIX facter improvements. It's scope is defined by the set of tickets added at its creation. Other AIX and/or facter work is out of this scope, to prevent this becoming an open-ended bucket of similar work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-441) Analytics for bolt
Title: Message Title Yasmin Rajabi commented on BOLT-441 Re: Analytics for bolt Nick Lewis ^^ is this enough to get started? 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 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, 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 facts this This 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 "Puppet
Jira (BOLT-491) I want to know how many targets are present in bolt
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-491 I want to know how many targets are present in bolt Change By: Yasmin Rajabi how many unique targets are they running on 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-489) I want to know what OS bolt is being run from
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: Yasmin Rajabi osfamily > I want to know if its paid redhat, free linux, windows, 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-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7115 Un-vendor semantic_puppet gem for Puppet 6 Change By: Jorie Tappa Release Notes Summary: Puppet now loads semantic_puppet from a shared gem directory, so that Puppet, Puppet agent, and Puppet Server all require and use the same version of the gem. (~>1.0.x) 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-533) Move facts to an external module
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Yasmin Rajabi The facts module implements several improvements over facter_task, 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). Deprecate facter_task. Move the facts implementation out of Bolt to an external module with the same name. Add beaker testing for the task, similar to facter_task. 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 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7157) Remove 'semantic' shim in Puppet 6
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 6 Change By: Jorie Tappa Release Notes Summary: Puppet now uses the shared gem dependency for semantic_puppet, rather than loading its own vendored version. 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-533) Move facts to an external module
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Yasmin Rajabi The facts module implements several improvements over facter_task, 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).Deprecate facter_task. Move the facts implementation out of Bolt to an external module with the same name.Add beaker testing for the task, similar to facter_task.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 facts this ticket will be for updating facter_task module with improvements from the facts task from bolt 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 Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Yasmin Rajabi The facts module implements several improvements over facter_task, 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).Deprecate facter_task. Move the facts implementation out of Bolt to an external module with the same name.Add beaker testing for the task, similar to facter_task.1. make plan for updating tasks on forge with cross platform implemtentation implementation 2. update facter_task module with new imporvements improvements 3. whenreleasing breaking changes to tasks use opportunity to change name of module from facter_task to facts Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed
Jira (BOLT-533) Move facts to an external module
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-533 Move facts to an external module Change By: Yasmin Rajabi The facts module implements several improvements over facter_task, 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).Deprecate facter_task. Move the facts implementation out of Bolt to an external module with the same name.Add beaker testing for the task, similar to facter_task. 1. make plan for updating tasks on forge with cross platform implemtentation2. update facter_task module with new imporvements3. when 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
Jira (BOLT-399) Update fact gathering task to leverage cross-platform support
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-399 Update fact gathering task to leverage cross-platform support Change By: Yasmin Rajabi In order to validate and provide examples for cross platform tasks we should update the fact gathering tasks to be a single cross platform task. The plan can then be simplified to leverage this. Still have 3 different tasks in the facts module, but there will be a new task that is just facts and it is based on the cross platform criteria.this is a new metadata only task (task is defined by metadata file, implementation is based on the tasks that exist) 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-532) Bolt no longer prints completion message when plan doesn't explicitly return a result
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-532 Bolt no longer prints completion message when plan doesn't explicitly return a result Change By: Michael Smith Fix Version/s: BOLT Next 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-532) Bolt no longer prints completion message when plan doesn't explicitly return a result
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-532 Bolt no longer prints completion message when plan doesn't explicitly return a result Change By: Michael Smith Assignee: 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-8770) Puppet resource service status should be more than binary
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-8770
Puppet resource service status should be more than binary
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/05/22 12:32 PM
Priority:
Normal
Reporter:
Paul Schaffer
When the Puppet Agent runs during boot (or at other times, during changes of various sorts), some services may still be starting, which means they show a different state than "active" for the service units. When Puppet runs, it tries to enforce { ensure=>running , enable => true} on the Service resource, which ends up restarting the already-starting service. For example, when restarting a host running a MariaDB Galera cluster, MariaDB is in the process of "catching up" with the cluster (via IST) when Puppet restarts it. That ends up breaking the incremental updates, requiring the node to take even longer to start up again by doing a full SST (which also makes another node in the cluster unavailable at that time). The desired behavior is that Puppet would see that the service is already in the process of starting, and do nothing, or possibly just log a warning. A similar issue likely exists for services which are in the process of stopping. The command `systemctl status is-active mariadb.service` returns this output in these states:
active (exit code 0) – normal "fully started" state
inactive (exit code 3) – fully stopped
deactivating (exit code 3) – in the process of stopping
activating (exit code 3) – in the process of starting
Puppet is simply leveraging an exit code of 0 or nonzero to determine the state, but it should probably be interpreting the actual state, through the contents of STDOUT from `systemctl is-active $SERVICE_NAME` for instance, so that it can properly handle these other states.
Jira (PUP-8746) Improve time_metrics in report generation to use existing statuses
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8746 Improve time_metrics in report generation to use existing statuses Change By: Josh Cooper Release Notes Summary: Simplify logic for resolving resources' types in reports 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 (PUP-8769) When sending CSR, Puppet should emit output indicating the server
Title: Message Title Ethan Brown created an issue Puppet / PUP-8769 When sending CSR, Puppet should emit output indicating the server Issue Type: Improvement Assignee: Unassigned Components: Networking Services Created: 2018/05/22 11:09 AM Labels: SSL Priority: Normal Reporter: Ethan Brown When a cert request is initiated, its possible that a misconfiguration in puppet.conf has sent the request to the wrong server. This can happen often in the Portland Office, where puppet is the default server name, and also the name of a local master available on the network. It can also happen to end users who incorrectly specify the name of a master. There is :server setting in Puppet that might be usable to help emit this information during the request (however, it may also be inaccessible given the request is sent through the indirector, which may not have access to this information). Add Comment
Jira (PDB-3926) Find/fix integration test failures with agent/server master (2018-05-22)
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3926 Find/fix integration test failures with agent/server master (2018-05-22) Issue Type: Improvement Assignee: Rob Browning Created: 2018/05/22 10:43 AM Priority: Normal Reporter: Rob Browning 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
Jira (PUP-1965) Clients are hung when server has intermittent service
Title: Message Title R.I.Pienaar commented on PUP-1965 Re: Clients are hung when server has intermittent service This can probably be closed after PUP-7517 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 (PDOC-255) Differentiate between Table of Contents and Section headers
Title: Message Title Jacob Helwig commented on PDOC-255 Re: Differentiate between Table of Contents and Section headers It might be worth considering matching the style PDK uses for the ToC in the README? Table of Contents 1. [Description](#description) 2. [Setup - The basics of getting started with <%= name %>](#setup) * [What <%= name %> affects](#what-<%= name %>-affects) * [Setup requirements](#setup-requirements) * [Beginning with <%= name %>](#beginning-with-<%= name %>) 3. [Usage - Configuration options and additional functionality](#usage) 4. [Limitations - OS compatibility, etc.](#limitations) 5. [Development - Guide for contributing to the module](#development)
Jira (PDOC-243) should escape underscores outside of code blocks
Title: Message Title R.I.Pienaar updated an issue Puppet Strings / PDOC-243 should escape underscores outside of code blocks Change By: R.I.Pienaar Issue Type: New Feature 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 (PDOC-255) Differentiate between Table of Contents and Section headers
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-255 Differentiate between Table of Contents and Section headers Issue Type: Bug Affects Versions: 2.0.0, 1.2.0, 1.2.1 Assignee: Unassigned Attachments: image-2018-05-22-10-23-49-229.png Created: 2018/05/22 10:24 AM Labels: markdown Priority: Normal Reporter: Eric Putnam Currently, the headers in the table of contents and the section headers are the same level and in modules that only contain Resource types, for example, this looks broken (see attached image). This ticket is for possibly adding a "table of contents" heading to the markdown output and moving the table of contents headers down a level. Add Comment
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Kishel commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Charlie suggests something like what puppet agent uses: env = Puppet::Node::Environment.remote(Puppet[:environment]) Or if the agent is compiling a catalog like puppet apply ... env = if options[:apply].nil? Puppet::Node::Environment.remote(Puppet[:environment]) else Puppet.lookup(:environments).get(Puppet[:environment]) end Add Comment
Jira (PUP-8768) Ability to export puppet Task output to CSV/Text file.
Title: Message Title max buehler created an issue Puppet / PUP-8768 Ability to export puppet Task output to CSV/Text file. Issue Type: New Feature Assignee: Unassigned Created: 2018/05/22 9:39 AM Priority: Normal Reporter: max buehler There have been a few times where I have manipulated puppet task output, particularly on exec-related tasks, to get a better idea of how my data looks. Unfortunately, since we have many servers, I have to open multiple pages and copy/paste this data in to a notepad, then clean it up a little bit. Would be nice to be able to export the results of a puppet task run. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title
Henrik Lindberg commented on PUP-7822
Re: Add a get() function that supports dot syntax to "dig" into hash/array
Agree - the get('$var...') is not needed. Will make those changes on the PR... (hold by beer...)
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-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title
Reid Vandewiele commented on PUP-7822
Re: Add a get() function that supports dot syntax to "dig" into hash/array
I agree that get() and getvar() would group nicely. I like getvar() better than var(). Is this what you're suggesting?
$facts.get('os.family')
get('$facts.os.family')
getvar('facts.os.family')
If we included getvar()... seems like we don't actually need the get('$facts.os.family') style, yes? These two would be enough:
$facts.get('os.family')
getvar('facts.os.family')
One function for each use case / invocation. I would be fully to that.
Add Comment
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Kishel commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Running `puppet device` on a non-master proxy puppet agent is common, if not recommended. Simply adding an empty directory on the proxy agent avoids this error. Some tests ... With agent and device pinned to the development environment group in the Console ... With environment=development in puppet.conf on agent ... [root@pe-201810-agent ~]# puppet config print environment development [root@pe-201810-agent ~]# rm -rf /etc/puppetlabs/code [root@pe-201810-agent ~]# puppet device --verbose Error: Could not run: undefined method `loaders' for nil:NilClass [root@pe-201810-agent ~]# puppet device --verbose --environment=development Error: Could not run: undefined method `loaders' for nil:NilClass
Jira (PUP-8676) Add cache support to 4.x function API
Title: Message Title Henrik Lindberg commented on PUP-8676 Re: Add cache support to 4.x function API The simple cache still has merit as a function may need to talk to a specific client library that handles connections (may not be http based). OTOH - that would also need some kind of life cycle as it is too simplistic as I currently implemented it (for example, when is the connection closed in such a scenario?). 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-8676) Add cache support to 4.x function API
Title: Message Title Henrik Lindberg commented on PUP-8676 Re: Add cache support to 4.x function API Sure - the function API has support for injection of values (used to inject scope and the simple cache implemented in this ticket). For things like a Https Pool we could add an injection that resolves from the puppet context - maybe by using the name of an entry in the context, or by doing a fancier mapping of an interface. It could look like this: dispatch :example_lookup do injected_param 'Puppet::HttpPool', :http_pool param 'String', :a_regular_param end This implies that we create a Puppet::HttpPool data type and register it. That data type defines the API. (Done this way it is possible to also write a function that makes use of this using puppet language (even if that would require additional work in the language, it is at least forward compatible). Simplest would otherwise be to directly support a http_pool specifically. Something like this: dispatch :example_lookup do http_pool_param :http_pool param 'String', :a_regular_param end That builds on what we already have, but is more specific and it may be better to implement this in a more open ended way (as per the first example).
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title
Henrik Lindberg commented on PUP-7822
Re: Add a get() function that supports dot syntax to "dig" into hash/array
Reid Vandewiele Note that you can write:
'$facts.os.family'.get()
Does change anything for you? If you want a separate function for variable access; there is already getvar() in stdlib. With that you could just do this:
getvar('facts').get('os.family')
(The getvar() function does not use a leading $ since it is not needed and an unnecessary potential gotcha when users have it in double quotes). What I like with a separate getvar() is that it is possible to handle that a variable does not exists differently from navigation not succeeding. I can imagine moving getvar() to puppet, and either just give it the ability to have a default value, or make it so it has the API of the get() with "$var" case (without a leading $). I am less keen on using the word var since we in the future may want to use that as a keyword to declare a local variable that can be reassigned. I also think that get() and getvar() would make them nicely grouped.
Add Comment
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Henrik Lindberg commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Guessing that puppet device does not set up the environment the same way as the regular agent does. IIRC it creates something known as a "Remote Environment" (which is quite different from the compiling side's directory based environment). 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Martin Ewings updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Martin Ewings 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 (PUP-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title Russell Howe created an issue Puppet / PUP-8767 --config_version option to `puppet apply` leads to ruby-specific lastrun YAML Issue Type: Bug Affects Versions: PUP 5.5.1 Assignee: Unassigned Components: CLI Created: 2018/05/22 3:00 AM Priority: Minor Reporter: Russell Howe If you run puppet apply --custom_version='echo foo' then the last run summary YAML ends up looking like this --- version: config: !ruby/string:Puppet::Util::Execution::ProcessOutput "foo" [...] Having the explicit typing makes it difficult to parse with general
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Hallgren commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production The problem is that this line: env = Puppet.lookup(:environments).get(Puppet[:environment]) results in env being nil. AFAICT, that can only happen when given the environment doesn't exist. Testing the command with --environment= works OK. So I'm lowering the priority on this one. 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Thomas Hallgren Priority: Major Normal 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Martin Ewings updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Martin Ewings CS Priority: Needs Priority 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-8676) Add cache support to 4.x function API
Title: Message Title Josh Cooper commented on PUP-8676 Re: Add cache support to 4.x function API I'd rather handle caching of http connections using the http client we're working on for intermediate ca support. It handles proxy settings, user agents, SSL trust stores, and http timeouts. Can we make a "FunctionContext" object available to client side functions so they can retrieve a connection? 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 (PDOC-254) @hiera section for putting example hiera
Title: Message Title Henrik Lindberg commented on PDOC-254 Re: @hiera section for putting example hiera How would that work? Why is a tag required? 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: Henrik Lindberg 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 (PUP-8765) Resource overrides are order dependent
Title: Message Title Henrik Lindberg commented on PUP-8765 Re: Resource overrides are order dependent The issue PUP-6290 is something different - it is about making another type of change "after the fact". PUP-7623, and (referenced) PUP-7660 are about validation of meta parameters that should not have been made. The reason this was not documented as a breaking change was because we were not aware that it was breaking as we had no tests that asserted that the documented behavior was actually in place and thus the break went undetected. 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.
