Jira (PUP-7815) Modules can find and list all their tasks
Title: Message Title
Justin Holguin updated an issue
Puppet / PUP-7815
Modules can find and list all their tasks
Change By:
Justin Holguin
This ticket covers giving modules the ability to list all the tasks that they contain. This involves:* finding all files in the tasks folders that do not end in '.conf' or '.md';* checking if every executable file *not* ending in '.json' (the 'executable file') has a matching metadata file with the same basename that *does* end in '.json' (the 'metadata file'):** if so, then each of those matching file pairs constitutes one task;** if not, each metadata file needs to be parsed to find the matching executable file, and any executable files left over that are not named by any metadata files are tasks that have no metadata;* returning an array of hashes with the files for each task: the executable file and (if it exists) the metadata file.Similar to https://github.com/puppetlabs/puppet/blob/ebd96213cab43bb2a8071b7ac0206c3ed0be8e58/lib/puppet/info_service.rbCan be used to call from Clojure (Puppet server) so that the Puppet team can change the underlying implementation if we wish.The new API:- Is defined in Puppet::InfoService that has class level methods that defines services*tasks_per_environment*A class level method `tasks_per_environment` that returns the names and modules of available tasks in the environment. Arguments: "environment_name" as a string (or a list of "environment_name")Output:{code} [{:module => {:name => "apache"}, :name => "install"}, …]{code}If there are no tasks in the named environment, returns the empty array.If the named environment does not exist, raises {{EnvironmentNotFound}}.Note that no information about the task itself is returned (e.g. metadata or file information), so no files are read or statted; the only filesystem IO performed is directory scans of each modules' tasks directory.*task_data*A class level method that returns files associated with a given task. Returns absolute file path of task metadata if found (else nil) and returns list of absolute paths to any non-metadata files with the provided name (empty list if none). Files list excludes any files with .json, .md, .conf extensions.Arguments: "environment_name", "module", "task_name"Output:{code}{:metadata_file => "path/to/file/.json", :files => ["path/to/file/.exe", "path/to/file/", ...]}{code}If the named module or task does not exist : , raises { code} { Puppet : metadata_file => nil, : files => nil Module::MissingModule } {code } . If the named environment does not exist, raises {{ Puppet::Environments:: EnvironmentNotFound}}. If the named task does not exist, raises {{Puppet::Module::Task::TaskNotFound}}. The path to the metadata file of a task should be retreivable from outside the task class; if no metadata file was provided when the task was created, it should be nil.
Jira (PUP-7837) Need to consider how the language used by puppet is decided
Title: Message Title Eric Delaney created an issue Puppet / PUP-7837 Need to consider how the language used by puppet is decided Issue Type: Bug Affects Versions: PUP 5.2.0 Assignee: Unassigned Created: 2017/08/11 3:05 PM Priority: Normal Reporter: Eric Delaney Problem: We need to consider how exactly the configured language of puppet is determined when started as a service when started as a user Short version: Puppet agent uses the LANG/LANGUAGE settings of the process that starts it. If that's the system its during startup, its Posix/C If its restarting the puppet agent service on Rhel5/6 its the settings of the user
Jira (PUP-7678) Add functions 'all' and 'any'
Title: Message Title Branan Riley commented on PUP-7678 Re: Add functions 'all' and 'any' This appears to have landed in master before we cut the 5.1.x branch, so I'm re-targeting this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7732) Audit puppet acceptance tests to remove duplicate pipeline duplication
Title: Message Title Branan Riley updated an issue Puppet / PUP-7732 Audit puppet acceptance tests to remove duplicate pipeline duplication Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7678) Add functions 'all' and 'any'
Title: Message Title Branan Riley updated an issue Puppet / PUP-7678 Add functions 'all' and 'any' Change By: Branan Riley Fix Version/s: PUP 5.2.0 Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6994) acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Title: Message Title Branan Riley updated an issue Puppet / PUP-6994 acceptance: no_exception_in_reduce_with_bignum doesn't test anything Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Branan Riley updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Branan Riley Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Branan Riley updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Branan Riley Sprint: Platform OS 2017-08-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Branan Riley updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Branan Riley Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Branan Riley updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title Branan Riley updated an issue Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Branan Riley updated an issue Puppet / PUP-6966 Tidy and File cannot remove fifo or socket files Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7815) Modules can find and list all their tasks
Title: Message Title Julia Ramer updated an issue Puppet / PUP-7815 Modules can find and list all their tasks Change By: Julia Ramer Issue Type: New Feature Story Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5047) POSIX Exec throws error when group has no name
Title: Message Title Branan Riley updated an issue Puppet / PUP-5047 POSIX Exec throws error when group has no name Change By: Branan Riley Fix Version/s: PUP 5.0.z Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5645) Can't install gems on Arch Linux
Title: Message Title Branan Riley updated an issue Puppet / PUP-5645 Can't install gems on Arch Linux Change By: Branan Riley Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7836) [SPIKE] Analysis of Heira 3 to 5 upgrade strategy
Title: Message Title Susan McNerney created an issue Puppet / PUP-7836 [SPIKE] Analysis of Heira 3 to 5 upgrade strategy Issue Type: Task Assignee: Unassigned Created: 2017/08/11 1:17 PM Priority: Normal Reporter: Susan McNerney This spike captures work to understand what tickets are needed to provide a smooth transition from Glisan to Hoyt with respect to Heira. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1728) facter -p dies with an inscrutable error if puppet crashes
Title: Message Title Geoff Nichols assigned an issue to Scott McClellan Facter / FACT-1728 facter -p dies with an inscrutable error if puppet crashes Change By: Geoff Nichols Assignee: Scott McClellan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7730) acceptance: add test ensuring v5 sends report as json when catalog cached
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-7730 acceptance: add test ensuring v5 sends report as json when catalog cached Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7729) acceptance: add preferred serialization format test
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-7729 acceptance: add preferred serialization format test Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title Anthony Chevalet commented on PUP-7813 Re: Yum package provider: ensure => latest fails when packages update available Bug reported on katello-agent: http://projects.theforeman.org/issues/20567 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title
Anthony Chevalet commented on PUP-7813
Re: Yum package provider: ensure => latest fails when packages update available
The culprit is the enabled_repos_upload yum plugin:
d-infra-mgt.cfc.ks.net 15:56:48 ~ # puppet resource package kernel ensure=latest
Error: Could not get latest version: undefined method `[]' for nil:NilClass
Error: /Package[kernel]/ensure: change from 3.10.0-514.10.2.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass
package { 'kernel':
ensure => '3.10.0-514.10.2.el7',
}
d-infra-mgt.cfc.ks.net 15:56:57 ~ #
d-infra-mgt.cfc.ks.net 15:56:57 ~ # sed -i 's:enabled=1:enabled=0:g' /etc/yum/pluginconf.d/enabled_repos_upload.conf
d-infra-mgt.cfc.ks.net 15:57:04 ~ # puppet resource package kernel ensure=latest
Jira (PUP-7835) undefined method `from' for #
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7835 undefined method `from' for # Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7835) undefined method `from' for #
Title: Message Title
Matteo Cerutti updated an issue
Puppet / PUP-7835
undefined method `from' for #
Change By:
Matteo Cerutti
The problem occurs when including a class that might look like the following:{code:puppet}class test ( String $var, Test::Options $opts) {}{code}Let's assume that Test::Options is defined as:{code:puppet}type Test::Options = Struct[{ var => String}]{code}If the 'var' parameter doesn't get passed to the keepalived test class, an evaluation error would be generated as expected. This works indeed.However, one would expected to see the same evaluation error popping up if var is not specified in the 'opts' hash, since it is required. Instead, the following error occurs:{noformat}Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Method call, undefined method `from' for #{noformat}This problem does not occur when using puppet apply (masterless).
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7835) undefined method `from' for #
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7835 undefined method `from' for # Change By: Henrik Lindberg Assignee: Thomas Hallgren Team: Platform Core Sprint: Language Triage Component/s: Puppet Server Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails
Jira (PUP-7835) undefined method `from' for #
Title: Message Title Matteo Cerutti created an issue Puppet / PUP-7835 undefined method `from' for # Issue Type: Bug Affects Versions: PUP 5.0.1 Assignee: Unassigned Components: Puppet Server Created: 2017/08/11 4:00 AM Priority: Normal Reporter: Matteo Cerutti The problem occurs when including a class that might look like the following: class test ( String $var,
Jira (PUP-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7834 Change all calls to YAML.load into YAML.safe_load Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7834 Change all calls to YAML.load into YAML.safe_load Issue Type: Improvement Assignee: Unassigned Created: 2017/08/11 3:40 AM Priority: Normal Reporter: Thomas Hallgren Now, when all serialization of YAML data is ensured to be Data, we must also ensure that no unsafe data can be loaded using YAML. Psych provides the method YAML.safe_load to accomplish this. We do have some places were we still load objects that are not Data for backward compatibility causes. We allow Symbol keys in hiera in some places and we provide a YAML-specificit tag for Puppet::Node::Facts to make it directly deserializable into instances of that class. Such exceptions can (and should) be declared specifically as arguments to YAML.safe_load. Add Comment
Jira (PUP-7768) Heredoc is not accepted by the Puppet TypeParser
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7768 Heredoc is not accepted by the Puppet TypeParser Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-577) Standalone `hiera` command errors with hiera v5 config file
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Hiera / HI-577 Standalone `hiera` command errors with hiera v5 config file Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
