Jira (FACT-1441) Add "cloud" or similar fact that identifies AWS, Azure, etc
Title: Message Title Scott McClellan assigned an issue to Scott McClellan Facter / FACT-1441 Add "cloud" or similar fact that identifies AWS, Azure, etc Change By: Scott McClellan 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 (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title Nicholas Fagerlund commented on PDOC-85 Re: Handle the case of 4x functions and 3x stubs My working assumption is that we have no items in the second category. (This might not be true, but we can make it true with a puppet PR as soon as I have a working function reference generator.) The plan is to prefer v4 functions, to pave the way to remove v3 functions. Given JSON that includes both versions of a given function, this is simple to do in the template, and requires no add'l work in Strings itself. If I see two versions of a given function and only one of them is v4, I'll ignore the other. 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 (PDOC-95) Strings doesn't handle multiple `defaultfor`s in providers correctly
Title: Message Title Nicholas Fagerlund commented on PDOC-95 Re: Strings doesn't handle multiple `defaultfor`s in providers correctly Word. We'll want this for docs integration stage 2 (types and providers reference), but it's not relevant to stage 1 (function reference). 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-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title Shawn Ferry commented on PUP-6784 Re: http_proxy specs fail if proxy is defined in test env Added spec/unit/network/http/factory_spec.rb 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-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title Shawn Ferry commented on PUP-6784 Re: http_proxy specs fail if proxy is defined in test env Also added forge/repository_spec 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-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title Shawn Ferry assigned an issue to Shawn Ferry Puppet / PUP-6784 http_proxy specs fail if proxy is defined in test env Change By: Shawn Ferry Assignee: Shawn Ferry 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-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title
Shawn Ferry updated an issue
Puppet / PUP-6784
http_proxy specs fail if proxy is defined in test env
Change By:
Shawn Ferry
If http_proxy is defined in the test environment specs fail due to precedence of http_proxy over HTTP_PROXY. ...{code:java} 16) Puppet::Util::HttpProxy.http_proxy_password should use environment variable before puppet settings Failure/Error: expect(subject.http_proxy_password).to eq(password)expected: "pAssw0rd" got: nil(compared using ==) # ./spec/unit/util/http_proxy_spec.rb:120:in `block (4 levels) in ' # ./lib/puppet/util.rb:128:in `withenv' # ./spec/unit/util/http_proxy_spec.rb:118:in `block (3 levels) in ' # ./spec/spec_helper.rb:211:in `block (2 levels) in 'Finished in 0.08603 seconds (files took 1.21 seconds to load)30 examples, 16 failures rspec spec/unit/forge/repository_spec.rbRun options: exclude {:broken=>true, :benchmark=>true}.....F.F 1) Puppet::Forge::Repository making a request returns the result object from the request Failure/Error: proxy_class = Net::HTTP::Proxy(self.http_proxy_host, self.http_proxy_port, self.http_proxy_user, self.http_proxy_password) Mocha::ExpectationError: unexpected invocation: Net::HTTP.Proxy('...{code}
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
Jira (PUP-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title
Shawn Ferry updated an issue
Puppet / PUP-6784
http_proxy specs fail if proxy is defined in test env
Change By:
Shawn Ferry
If http_proxy is defined in the test environment specs fail due to precedence of http_proxy over HTTP_PROXY. ...{code:java} 16) Puppet::Util::HttpProxy.http_proxy_password should use environment variable before puppet settings Failure/Error: expect(subject.http_proxy_password).to eq(password)expected: "pAssw0rd" got: nil(compared using ==) # ./spec/unit/util/http_proxy_spec.rb:120:in `block (4 levels) in ' # ./lib/puppet/util.rb:128:in `withenv' # ./spec/unit/util/http_proxy_spec.rb:118:in `block (3 levels) in ' # ./spec/spec_helper.rb:211:in `block (2 levels) in 'Finished in 0.08603 seconds (files took 1.21 seconds to load)30 examples, 16 failures 1) Puppet::Forge::Repository making a request returns the result object from the request Failure/Error: proxy_class = Net::HTTP::Proxy(self.http_proxy_host, self.http_proxy_port, self.http_proxy_user, self.http_proxy_password) Mocha::ExpectationError: unexpected invocation: Net::HTTP.Proxy('... {code}
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.
Jira (PUP-6592) acceptance: Sensitive data
Title: Message Title William Hopper commented on PUP-6592 Re: acceptance: Sensitive data Merged up to master at https://github.com/puppetlabs/puppet/commit/0d46f67e456c9419b47928b14f54e48c1e1e853f 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-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Erik Hansen created an issue Puppet / PUP-6801 agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Issue Type: Bug Affects Versions: PUP 4.4.0 Assignee: Unassigned Created: 2016/10/06 4:33 PM Priority: Normal Reporter: Erik Hansen Currently, if I want to use the agent_specified_environment fact, I need to set the environment setting in puppet.conf in the [main] section. If I happen to be hitting this bug: PUP-6048, this isn't possible. Putting the environment setting in the [agent] section works around PUP-6048, but doesn't allow me to use agent_specified_environment, the fact ends up empty. Add Comment
Jira (PUP-6800) Better error messaging around invalid class names
Title: Message Title Erik Hansen commented on PUP-6800 Re: Better error messaging around invalid class names What I observed was that a Windows agent was unable to pick up a class role::appserver::windows_2012R2 until the second time that the agent ran the catalog. Here is an example of the info in puppetserver.log: 2016-09-16 14:47:58,964 ERROR [qtp1760965953-81] [puppetserver] Puppet Could not find class role::appserver::windows_2012R2 for puppetagent.example.comt on node puppetagent.example.com There wasn't really anything that identified the invalid class name, but when the class was renamed to role::appserver::windows_2012r2, I no longer saw the issue. 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 (PDOC-118) Add ruby version requirement in puppet-strings.gemspec
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-118 Add ruby version requirement in puppet-strings.gemspec Issue Type: Task Assignee: William Hopper Created: 2016/10/06 4:23 PM Priority: Normal Reporter: William Hopper The strings gemspec doesn't currently have a required_ruby_version field. This makes the required version show up as '> 0' on rubygems.org, but we really only test and support ruby >= 1.9.3. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1515) Facter does not respect the configuration file and still attempts to collect facts
Title: Message Title
Christian Mague created an issue
Facter / FACT-1515
Facter does not respect the configuration file and still attempts to collect facts
Issue Type:
Bug
Affects Versions:
FACT 3.4.1
Assignee:
Unassigned
Created:
2016/10/06 4:15 PM
Priority:
Normal
Reporter:
Christian Mague
uname -a Linux xen-28-125 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux
ii puppet-agent 1.7.0-1wheezy amd64 The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera
facter --version 3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc)
cat /tmp/facter.conf facts : { blocklist : [ "filesystems", "partitions", "file system", "timezone" ] }
facter --debug --config /tmp/facter.conf 2016-10-06 16:11:58.530112 INFO puppetlabs.facter - executed with command
Jira (PDOC-113) Build and smoke test gem (PDOC 0.99.0)
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-113 Build and smoke test gem (PDOC 0.99.0) Change By: William Hopper Summary: Build and smoke test gem (PDOC 0.99.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-6800) Better error messaging around invalid class names
Title: Message Title Henrik Lindberg commented on PUP-6800 Re: Better error messaging around invalid class names Erik Hansen Suspect you have been bitten by a specific case. There is really not much to go in in your description that make this actionable. Can you give examples? 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-6800) Better error messaging around invalid class names
Title: Message Title Henrik Lindberg assigned an issue to Erik Hansen Puppet / PUP-6800 Better error messaging around invalid class names Change By: Henrik Lindberg Assignee: Erik Hansen 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 (PDOC-117) Close all resolved tickets in Jira (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-117 Close all resolved tickets in Jira (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 4:06 PM Priority: Normal Reporter: William Hopper Close any tickets which have been resolved for the release. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-116) Send out announcements (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-116 Send out announcements (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 4:06 PM Priority: Normal Reporter: William Hopper Send out the release notes to puppet-dev, puppet-users and puppet-announce google groups, as well as internally at dev-t...@puppetlabs.com. Also ping in IRC and Slack. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-115) Push tag to GitHub (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-115 Push tag to GitHub (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 4:04 PM Priority: Normal Reporter: William Hopper 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
Jira (PDOC-114) Go/no-go meeting (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-114 Go/no-go meeting (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 4:03 PM Priority: Normal Reporter: William Hopper Verify the release with necessary strings stakeholders. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-112) Tag the release (PDOC 0.99.0)
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-112 Tag the release (PDOC 0.99.0) Change By: William Hopper Tag the release locally , but don't push tag it to GitHub yet . 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 (PDOC-113) Build and smoke test gem
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-113 Build and smoke test gem Issue Type: Sub-task Assignee: William Hopper Created: 2016/10/06 4:02 PM Priority: Normal Reporter: William Hopper Verify the gem works on a few platforms. Check that the major features of this release are all functional. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-112) Tag the release (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-112 Tag the release (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 3:59 PM Priority: Normal Reporter: William Hopper Tag the release, push tag to GitHub. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6785) Service start unit tests fail on Solaris
Title: Message Title Shawn Ferry updated an issue Puppet / PUP-6785 Service start unit tests fail on Solaris Change By: Shawn Ferry Environment: 4.7.0 Oracle Corporation SunOS 5 . Solaris Next 12 s12_109 September 2016 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-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Geoff Nichols Sprint: AP Triage 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 (PDOC-111) Prepare long form release notes (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-111 Prepare long form release notes (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 3:40 PM Priority: Normal Reporter: William Hopper These will go out to puppet-dev and puppet-users. Will collaborate with Jean Bond. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-110) Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-110 Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0) Issue Type: Sub-task Assignee: Unassigned Created: 2016/10/06 3:39 PM Priority: Normal Reporter: William Hopper (Initial planned release date: 2016-10-10) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone TestRail: Results Add Comment
Jira (PDOC-109) Reconcile git commits and JIRA tickets (PDOC 0.99.0)
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-109 Reconcile git commits and JIRA tickets (PDOC 0.99.0) Change By: William Hopper Summary: Reconcile git commits and JIRA tickets ( string PDOC 0.99.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 (PDOC-109) Reconcile git commits and JIRA tickets (string 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-109 Reconcile git commits and JIRA tickets (string 0.99.0) Issue Type: Sub-task Assignee: William Hopper Created: 2016/10/06 3:36 PM Priority: Normal Reporter: William Hopper This is the first time in a while this has been done, but we can probably use https://github.com/puppetlabs/ticketmatch to do this. Make sure all git commits (besides maint) have Jira tickets and vice versa. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6800) Better error messaging around invalid class names
Title: Message Title William Hopper updated an issue Puppet / PUP-6800 Better error messaging around invalid class names Change By: William Hopper Team: Puppet Developer Support 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-6782) Improve windows command line argument quoting
Title: Message Title William Hopper updated an issue Puppet / PUP-6782 Improve windows command line argument quoting Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6792) SMF should recursively enable services
Title: Message Title William Hopper updated an issue Puppet / PUP-6792 SMF should recursively enable services Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6783) Update all built-in resources to specify {{apply_to_all}} when appropriate
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6783
Update all built-in resources to specify {{apply_to_all}} when appropriate
Change By:
William Hopper
Labels:
maintenance
Team:
Agent & Platform
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-6785) Service start unit tests fail on Solaris
Title: Message Title William Hopper updated an issue Puppet / PUP-6785 Service start unit tests fail on Solaris Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6784) http_proxy specs fail if proxy is defined in test env
Title: Message Title William Hopper updated an issue Puppet / PUP-6784 http_proxy specs fail if proxy is defined in test env Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6793) pkg provider should be default for Solaris 12
Title: Message Title William Hopper updated an issue Puppet / PUP-6793 pkg provider should be default for Solaris 12 Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6796) Support setting/checking shell in user_role_add
Title: Message Title William Hopper updated an issue Puppet / PUP-6796 Support setting/checking shell in user_role_add Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6795) Solaris does not support gzipped man pages
Title: Message Title William Hopper updated an issue Puppet / PUP-6795 Solaris does not support gzipped man pages Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title William Hopper updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: William Hopper Story Points: 2 Team: Puppet Developer Support Sprint: PDS 2016-10-19 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-6797) service should check for smf service first
Title: Message Title William Hopper updated an issue Puppet / PUP-6797 service should check for smf service first Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title William Hopper updated an issue Puppet / PUP-6798 Ensuring latest does not use upgrade command in DNF Change By: William Hopper Labels: maintenance Team: Agent & Platform 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-6800) Better error messaging around invalid class names
Title: Message Title Erik Hansen created an issue Puppet / PUP-6800 Better error messaging around invalid class names Issue Type: Improvement Assignee: Unassigned Created: 2016/10/06 3:10 PM Priority: Normal Reporter: Erik Hansen The language guide is specific about what allowed class names are: https://docs.puppet.com/puppet/latest/reference/lang_reserved.html#classes-and-defined-resource-types However, if someone were unaware of the character limitation, it can cause issues that are difficult to track down, such as classes not loading or only being available to certain agents. It would be an improvement if puppet server or the console service (or both) would issue clear warnings about class names that do not follow the standard. Add Comment
Jira (PUP-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6524 The shell used with exec resource provider=shell should be configurable Change By: Geoff Nichols Team: Agent & Platform 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Geoff Nichols Team: Agent & Platform 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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Geoff Nichols Labels: Maintenance 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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Geoff Nichols Labels: Maintenance 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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Geoff Nichols Team: Agent & Platform 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-6741
When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Change By:
Eric Sorenson
In the case where `recurse => true' is added to a file resource which is actually a directory with a whole bunch of files in it, it appears that not all these files get tagged with either the default tags for the class/resource or with custom tags specified in the resource declaration.If these tags are then used later in a puppet run using --tags, the resource is not included.As an example, the following code will create a number of files in a directory, where the directory is marked as ` {{ recurse => true ` }} and the resource is tagged with a tag ` {{ sometag ` }} : ``` {code} class abc::component::ao { tag 'sometag' file { '/tmp/somefiles': tag => 'sometag', ensure => directory, source => "puppet:///static/somefiles", recurse => true, purge => true, owner => 'root', group => 'root', } exec { 'do something': tag => 'sometag', command => '/bin/echo do something', # 20 lines script refreshonly => true, subscribe => [ File['/tmp/somefiles'], ], } } ``` {code} However, when ` {{ puppet agent -t --tags sometag ` }} is run, the following is noted in the output: ``` {code} Notice: /Stage[main]/Abc::Component::Ao/File[/ao/basescripts/su_stop.ksh]/ensure: defined content as '{md5}1fd97a2fc03e639946d960ebd13bebd8'Debug: /Stage[main]/Abc::Component::Ao/File[/ao/basescripts/su_stop.ksh]: The container /ao/basescripts will propagate my refresh eventDebug: /ao/basescripts: Not tagged with sometagDebug: /ao/basescripts: Resource is being skipped, unscheduling all eventsInfo: /ao/basescripts: Unscheduling all events on /ao/basescripts ``` {code} This suggests that the tag was not set correctly on all files when the recurse was set and so the Exec is not refreshed.The exact same code without the `recurse => true` works exactly as expected.Is this a bug, and is there a workaround for this issue?Stefan
Add Comment
Jira (PUP-6423) The scheduled_task provider performs incorrect matching on file names
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6423 The scheduled_task provider performs incorrect matching on file names Change By: Geoff Nichols Sprint: AP Triage Grooming Top 11-20 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren commented on PUP-5834 Re: Handle extended data in the catalog I think it's bad practice to move a resolved ticket back to 'Ready for engineering'. I'm not even convinced that this ticket is at fault. My guess is that it has revealed a problem where some non json-compatible object leaks into the catalog. That could go undetected in the past. In any case, whether this is a regression or something else, it should not cause a reopen of this ticket IMO. 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-5834) Handle extended data in the catalog
Title: Message Title William Hopper commented on PUP-5834 Re: Handle extended data in the catalog This series of commits or another on top of it has caused a failure in PEZ in the 2016.5.x pipeline: https://jenkins.puppetlabs.com/job/enterprise_pe-acceptance-tests-feature-branch_integration-system_pe_fb_smoke-monolithic_2016.5.x/LAYOUT=64mcd,LEGACY_AGENT_VERSION=NONE,PLATFORM=redhat7,UPGRADE_FROM=NONE,label=beaker/7/console 19:50:16 Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Unable to serialize non-Data type parameters unless a serializer is provided 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title William Hopper updated an issue Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: William Hopper Summary: PEZ 2015 2016 . 3 5 .x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided 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-6799) PEZ 2015.3.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title William Hopper created an issue Puppet / PUP-6799 PEZ 2015.3.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Issue Type: Bug Assignee: Unassigned Created: 2016/10/06 1:22 PM Priority: Blocker Reporter: William Hopper https://jenkins.puppetlabs.com/job/enterprise_pe-acceptance-tests-feature-branch_integration-system_pe_fb_smoke-monolithic_2016.5.x/LAYOUT=64mcd,LEGACY_AGENT_VERSION=NONE,PLATFORM=redhat7,UPGRADE_FROM=NONE,label=beaker/7/console PEZ fails with the following in setup: 19:50:16 Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Unable to serialize non-Data type parameters unless a serializer is provided This was likely caused by this series of commits (part of PUP-5834 ): https://github.com/puppetlabs/puppet/commit/375bdeefef79e3984f1d53db04e14c94e5a3d30c
Jira (PDB-2810) Update benchmark tool and samples
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-2810 Update benchmark tool and samples Change By: Ryan Senior Assignee: Ryan Senior 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 (PDB-2810) Update benchmark tool and samples
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2810 Update benchmark tool and samples Change By: Ryan Senior Team: Systems Engineering 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 (PDB-2810) Update benchmark tool and samples
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2810 Update benchmark tool and samples Change By: Ryan Senior Sprint: Hopper SE 2016-10-19 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-6580) `puppet cert` does not appear to work on Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6580 `puppet cert` does not appear to work on Windows Change By: Moses Mendoza Sprint: Modules 2016-11-02 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-6580) `puppet cert` does not appear to work on Windows
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6580 `puppet cert` does not appear to work on Windows Change By: Kenn Hussey Sprint: Modules 2016-11-02 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-6079) The windows puppetagent version available for download in " https://puppetlabs.com/download-puppet-enterprise-get-expand " is more than the puppet master version available in the same
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6079 The windows puppetagent version available for download in " https://puppetlabs.com/download-puppet-enterprise-get-expand " is more than the puppet master version available in the same link Change By: Kenn Hussey Sprint: Windows Triage 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-6580) `puppet cert` does not appear to work on Windows
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6580 `puppet cert` does not appear to work on Windows Change By: Kenn Hussey Sprint: Windows Triage 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-6079) The windows puppetagent version available for download in " https://puppetlabs.com/download-puppet-enterprise-get-expand " is more than the puppet master version available in the same
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6079 The windows puppetagent version available for download in " https://puppetlabs.com/download-puppet-enterprise-get-expand " is more than the puppet master version available in the same link Change By: Kenn Hussey Sprint: Modules 2016-11-02 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-6786) ProviderParsed tests fail on Solaris for Darwin/Linux
Title: Message Title Shawn Ferry assigned an issue to Shawn Ferry Puppet / PUP-6786 ProviderParsed tests fail on Solaris for Darwin/Linux Change By: Shawn Ferry Assignee: Shawn Ferry 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-6787) directoryservice spec is trying to execute commands on Solaris
Title: Message Title Shawn Ferry assigned an issue to Shawn Ferry Puppet / PUP-6787 directoryservice spec is trying to execute commands on Solaris Change By: Shawn Ferry Assignee: Shawn Ferry 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 (PDB-3088) (maint) Ignore me - 3.2.x acc testing dummy
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3088 (maint) Ignore me - 3.2.x acc testing dummy Change By: Kenn Hussey Team: Systems Engineering 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-447) Get pre-suites working for Debian 9 Stretch (i386, amd64) for Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-447 Get pre-suites working for Debian 9 Stretch (i386, amd64) for Hiera Change By: Kenn Hussey Sprint: PCP Triage 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-5142) Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5142 Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet Change By: Kenn Hussey Sprint: PCP Triage 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-439) Get pre-suites working for Fedora 23 (i386, x86_64) for Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-439 Get pre-suites working for Fedora 23 (i386, x86_64) for Hiera Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1203) Add node definition for Debian 9 Stretch (i386, amd64) to Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1203 Add node definition for Debian 9 Stretch (i386, amd64) to Facter Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1204) Get pre-suites working for Debian 9 Stretch (i386, amd64) for Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1204 Get pre-suites working for Debian 9 Stretch (i386, amd64) for Facter Change By: Kenn Hussey Sprint: PCP Triage 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-5156) Get pre-suites working for Debian 9 Stretch (i386, amd64) for Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5156 Get pre-suites working for Debian 9 Stretch (i386, amd64) for Puppet Change By: Kenn Hussey Sprint: PCP Triage 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-438) Add node definition for Fedora 23 (i386, x86_64) to Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-438 Add node definition for Fedora 23 (i386, x86_64) to Hiera Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1196) Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1196 Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Facter Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1194) Get pre-suites working for Fedora 23 (i386, x86_64) for Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1194 Get pre-suites working for Fedora 23 (i386, x86_64) for Facter Change By: Kenn Hussey Sprint: PCP Triage 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-440) Add node definition for Ubuntu 15.10 (i386, x86_64) to Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-440 Add node definition for Ubuntu 15.10 (i386, x86_64) to Hiera Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1195) Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1195 Add node definition for Ubuntu 15.10 (i386, x86_64) to Facter Change By: Kenn Hussey Sprint: PCP Triage 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-5143) Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5143 Add node definition for Ubuntu 15.10 (i386, x86_64) to Puppet Change By: Kenn Hussey Sprint: PCP Triage 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-5141) Add node definition for Fedora 23 (i386, x86_64) to Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5141 Add node definition for Fedora 23 (i386, x86_64) to Puppet Change By: Kenn Hussey Sprint: PCP Triage 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 (FACT-1193) Add node definition for Fedora 23 (i386, x86_64) to Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1193 Add node definition for Fedora 23 (i386, x86_64) to Facter Change By: Kenn Hussey Sprint: PCP Triage 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-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5593 Update Cumulus Node config to use VM from VMpooler Change By: Kenn Hussey Sprint: PCP Triage 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-5144) Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5144 Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Puppet Change By: Kenn Hussey Sprint: PCP Triage 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-441) Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-441 Get pre-suites working for Ubuntu 15.10 (i386, x86_64) for Hiera Change By: Kenn Hussey Sprint: PCP Triage 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-6497) CapabilityFinder says a capability couldn't be found if there are multiple versions of it
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6497 CapabilityFinder says a capability couldn't be found if there are multiple versions of it Change By: Kenn Hussey Sprint: AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 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-6087) Multiple contradictory 'consumes' annotation do not lead to an error
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6087 Multiple contradictory 'consumes' annotation do not lead to an error Change By: Kenn Hussey Sprint: AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 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-6182) Application declarations don't properly validate component mappings
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6182 Application declarations don't properly validate component mappings Change By: Kenn Hussey Sprint: AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 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-6788) 4.x functions specs don't match errors on Solaris
Title: Message Title Shawn Ferry assigned an issue to Shawn Ferry This was an environment error. Having both older (3.8.6) puppet installed and testing from the git clone resulted in extraneous failures. Puppet / PUP-6788 4.x functions specs don't match errors on Solaris Change By: Shawn Ferry Resolution: Won't Fix Assignee: Shawn Ferry Status: Open Closed 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
Jira (PUP-6788) 4.x functions specs don't match errors on Solaris
Title: Message Title Shawn Ferry commented on PUP-6788 Re: 4.x functions specs don't match errors on Solaris Thank you, that made me realize I should try uninstalling the puppet we currently ship. I still don't see that message in Puppet 3.8.6 but the reported issue is not valid. Oracle Corporation SunOS 5.12 s12_109 September 2016 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 (PDOC-107) puppet-strings 0.99.0 Release
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-107 puppet-strings 0.99.0 Release Change By: William Hopper Summary: puppet-strings 0.99.0 Release Strings 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 (PDOC-108) Is the code ready for release? (PDOC 0.99.0)
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-108 Is the code ready for release? (PDOC 0.99.0) Issue Type: Sub-task Assignee: William Hopper Created: 2016/10/06 11:25 AM Priority: Normal Reporter: William Hopper If there are any version dependencies expressed in the code base, make sure these are up to date. Strings will need its CHANGELOG and gemspec updated. All tests (spec, acceptance) should be passing on all platforms. Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. Add Comment This message was
Jira (PDB-2849) correct deprecation warning around export tool
Title: Message Title Ryan Senior commented on PDB-2849 Re: correct deprecation warning around export tool Wyatt Alt Do you have any more recommendations on approach here? AFAIK, the packages are different from PE and FOSS, is there something that is package independent that we could point the user at? Maybe a packaging change to "suggest" the CLI package (PE or FOSS) 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 (PDB-2997) OOM on upgrade to PDB 4.2.0
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2997 OOM on upgrade to PDB 4.2.0 Change By: Susan McNerney Labels: davis-triage pdb-ss 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 (PDB-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2985 Fix excessive CPU usage by clj-i18n Change By: Susan McNerney Labels: davis-triage i18n pdb-ss 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 (PDB-3089) Fix intermittent pdbext test failures around 2016-10-06
Title: Message Title Rob Browning commented on PDB-3089 Re: Fix intermittent pdbext test failures around 2016-10-06 I was able to reproduce some failures which may be the same as the ones Dan saw by running postgres under "trickle -u 1 -d 1". 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 (PDB-3089) Fix intermittent pdbext test failures around 2016-10-06
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3089 Fix intermittent pdbext test failures around 2016-10-06 Issue Type: Bug Assignee: Rob Browning Created: 2016/10/06 8:50 AM Labels: maintenance Priority: Normal Reporter: Rob Browning 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
Jira (PUP-6788) 4.x functions specs don't match errors on Solaris
Title: Message Title John Duarte updated an issue Puppet / PUP-6788 4.x functions specs don't match errors on Solaris Eric Thompson I am not familiar with this condition. I have run the puppet#master spec tests at SHA 83c1c8f95265e7d689b975ac421b92ef3b80389a on Solaris 11.2 x86. Seven failures were present in this run, but none of them exhibit the error described in this ticket. I am attaching the results of this test run. Shawn Ferry can you provide additional information about how to reproduce the errors that you witnessed? — Steps taken to produce the attached spec run. System tested: Solaris 11.2 x86_64 Oracle Corporation SunOS 5.11 11.2June 2014 As root: pkg install git git clone https://github.com/puppetlabs/puppet cd puppet/ pkg install --accept ruby pkg install --accept gcc /usr/ruby/2.1/bin/bundle install
Jira (PUP-3630) The compiler does not process metaparameter inheritance for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen commented on PUP-3630 Re: The compiler does not process metaparameter inheritance for resources declared outside of Class[main] So, how about filtering out the classes so they do not get the meta parameters ? Coming back to this, I think classes should at least get and propagate the noop metaparameter. Otherwise, there isn't a clean way to put a new or upgraded class definitions into noop for testing purposes. Even the usual dirty tricks such as resource defaults and resource collectors won't work because there isn't a single resource type to target. If we're still opposed to adding metaparameters to resource-style class declarations, then we should find an alternate way to enable the use case of no-opping an entire class or namespace for testing purposes. 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-6768) Implement 'lookup invocation' object in the lookup v5 API
Title: Message Title Henrik Lindberg commented on PUP-6768 Re: Implement 'lookup invocation' object in the lookup v5 API Agree - and change the name to cached_entries, or perhaps each_cached since it behaves like each? 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-6768) Implement 'lookup invocation' object in the lookup v5 API
Title: Message Title
Thomas Hallgren commented on PUP-6768
Re: Implement 'lookup invocation' object in the lookup v5 API
I would prefer if we had distinct method names instead of overloads.
cache(key, value)
cache_all(hash)
cached_value(key)
all_cached | $key, $val | { }
having both cache_all and all_cached is perhaps not ideal. Perhaps the latter could be cached_entries instead?
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to
Jira (PUP-6768) Implement 'lookup invocation' object in the lookup v5 API
Title: Message Title Henrik Lindberg commented on PUP-6768 Re: Implement 'lookup invocation' object in the lookup v5 API I am ok with LookupContext; more straight forward and shorter. 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-6768) Implement 'lookup invocation' object in the lookup v5 API
Title: Message Title Thomas Hallgren commented on PUP-6768 Re: Implement 'lookup invocation' object in the lookup v5 API I think we should change the name from LookupInvocation to LookupContext. The reason being that the current LookupInvocation is instantiated when the top invocation starts. It's then used for by the explainer and by the recursion guard throughout all calls until the top invocation returns. That object must also maintain a stack of contexts which in turn is unique for each combination of contextual path and lookup function. 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-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title
Peter Souter updated an issue
Puppet / PUP-6798
Ensuring latest does not use upgrade command in DNF
Change By:
Peter Souter
tl;dr using ensure latest with a previous install will use the install command in dnf, which does not upgrade the package:{code}Debug: /Stage[main]/Main/Package[cockpit]/ensure: cockpit "0.55-1.fc22" is installed, latest is "0:0.67-2.fc22" Debug: Package[cockpit](provider=dnf_update): Ensuring => latest Debug: Package[cockpit](provider=dnf_update): Asking for latest, so run upgrade command Debug: Executing: '/usr/bin/dnf -d 0 -e 1 -y install cockpit' Notice: /Stage[main]/Main/Package[cockpit]/ensure: ensure changed '0.55-1.fc22' to '0:0.67-2.fc22' Debug: /Stage[main]/Main/Package[cockpit]: The container Class[Main] will propagate my refresh event{code}The original issue of failing to update when a new version is specified was fixed in https://tickets.puppetlabs.com/browse/PUP-6324, but the code doesn't cover the case of a package that is installed, then later attempted to update with ensure => latest.
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.
