Jira (PUP-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Geoff Nichols commented on PUP-6487 Re: puppet-agent fails to build on/for ubuntu, huawei This appears to be fixed. Passing CI run at https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_pkg-van-ship_daily-master/272/. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-6487 puppet-agent fails to build on/for ubuntu, huawei Change By: Michael Stahnke Sub-team: Platforms Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6468) Move PE acceptance tests to puppet core
Title: Message Title John Duarte updated an issue Puppet / PUP-6468 Move PE acceptance tests to puppet core Change By: John Duarte Sprint: Client 2016-07-27 facter.conf Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6498) Exec resource reports errors by splitting into multiple lines
Title: Message Title Ian Oberst created an issue Puppet / PUP-6498 Exec resource reports errors by splitting into multiple lines Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/07/12 6:10 PM Priority: Normal Reporter: Ian Oberst Currently when an error occurs within an exec resource (at this point, specifically with the Powershell provider) the resulting error is reported in the run report logs across multiple lines. This is due to the exec resource type splitting the output into multiple lines. The result, at least on windows, is a large amount of unintelligible lines in the Windows Event Logs as well as a difficult to read run log in the PE console. Instead of splitting the error it would be nice to have it return the error on a single line so it can be viewed in context. The offending code is here. Add Comment
Jira (FACT-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6440) Tag transaction events with sensitive data
Title: Message Title Eric Thompson commented on PUP-6440 Re: Tag transaction events with sensitive data Adrien Thebo do we think there is anything, new, user facing to test here? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte QA Risk Assessment Reason: Regression test too costly to reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1448) facter json output converts all booleans to true
Title: Message Title John Duarte commented on FACT-1448 Re: facter json output converts all booleans to true Acceptance test has been merged. This ticket can be resolved after a puppet-agent build >= c32198a passes CI. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 Nick Lewis created an issue Puppet / PUP-6497 CapabilityFinder says a capability couldn't be found if there are multiple versions of it Issue Type: Bug Assignee: Unassigned Components: DEV Created: 2016/07/12 4:34 PM Priority: Normal Reporter: Nick Lewis If two versions of a capability resource exist and neither corresponds to the code-id being compiled, the CapabilityFinder will fail with an error saying the resource couldn't be found and might not have been produced yet. This is inaccurate, since it was in fact produced multiple times and the real problem is that it's not clear which one to use. This message should be updated to better reflect that reality. Add Comment
Jira (PDB-2855) PQL - Possibility to create fact arrays like from Puppetdbquery
Title: Message Title
Andrew Roetker commented on PDB-2855
Re: PQL - Possibility to create fact arrays like from Puppetdbquery
Also you could use the following custom puppet function to accomplish what you want in the mean time as well André Bauer
require 'puppet/util/puppetdb' Puppet::Functions.create_function(:puppetdb_query_alt) do dispatch :puppetdb_query_alt do required_param 'Variant[String[1], Array[Data, 1]]', :query optional_param 'String', :grouphosts end
def puppetdb_query_alt(query, grouphosts = nil) results = Puppet::Util::Puppetdb.query_puppetdb(query) if grouphosts results.reduce({}) do |ret, item| ret[item['certname']] = [] unless ret.key? item['certname'] ret[item['certname']] << item ret end else results end end end {end}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-1457) Spike HOCON access layer
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1457 Spike HOCON access layer Change By: Maggie Dreyer Depending on how we want to be able to interact with the config file, we may want to define some wrapper methods around cpp-hocon's public API. Another consideration is whether the config object should be a singleton of some kind. This will depend on where we need to access it for the more complicated settings. For initial configuration of global, one-off settings like fact directories, this is overkill. But for settings dealing with the resolution of individual facts, it may be both cleaner and more efficient to have global access to a central settings or config object. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Justin Stoller assigned an issue to Nathaniel Smith Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Justin Stoller Assignee: Nathaniel Smith Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu moved an issue Puppet / PUP-6496 Add support for using hocon for main hiera config file Change By: Jane Lu Key: HI PUP - 523 6496 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Kurt Wall updated an issue Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Kurt Wall updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2868) Move how to setup and run PuppetDB unit tests
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2868 Move how to setup and run PuppetDB unit tests Issue Type: Bug Assignee: Unassigned Created: 2016/07/12 2:08 PM Priority: Normal Reporter: gepetto-bot This pull request moves how to set up postgresql to run the unit tests into the CONTRIBUTING doc. It also includes the contributing document in the navigation header. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title R.I.Pienaar commented on PUP-2018 Re: `puppet certificate generate` Generates Two CSRs in One Run side note, this breaks the mcollective install docs, be good to get this fixed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6494) exec resources leak the command string when execution fails
Title: Message Title Henrik Lindberg commented on PUP-6494 Re: exec resources leak the command string when execution fails The eyaml is currently a hiera (project) backend which makes it difficult to have settings for it in puppet. It would be best if it is was available as a data provider instead as it is then possible to pass arguments to the provider via the configuration file (a different format than for the 3.x hiera project). In general, data providers should be able to return rich data types such as a Sensitive[T] which requires a new set of providers than the current set of json/yaml ones. A port of eyaml could be the first. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2867) Maint/move postgres test setup docs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2867 Maint/move postgres test setup docs Issue Type: Bug Assignee: Unassigned Created: 2016/07/12 1:54 PM Priority: Normal Reporter: gepetto-bot This pull request moves how to set up postgresql to run the unit tests into the CONTRIBUTING doc. It also includes the contributing document in the navigation header. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Daniel Lu assigned an issue to Daniel Lu Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Change By: Daniel Lu Assignee: Daniel Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Eric Thompson Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Eric Thompson Scope Change Category: Found Scope Change Reason: puppetserver CI blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Eric Thompson Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Eric Thompson Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg commented on HI-523 Re: Add support for using hocon for main hiera config file That means that there is nothing to implement here in this ticket as the data providers are in puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg commented on HI-523 Re: Add support for using hocon for main hiera config file Chris Price That last clarified part makes sense (hiera.conf, then hiera.yaml, in the data providers but not in hiera-the-project (i.e. 3.x hiera)). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6495) Allow for assigning different environments to Solaris zones
Title: Message Title Erik Hansen created an issue Puppet / PUP-6495 Allow for assigning different environments to Solaris zones Issue Type: New Feature Assignee: Unassigned Created: 2016/07/12 12:31 PM Priority: Normal Reporter: Erik Hansen A Solaris server that has 5 local zones and each zone acts as a different environment for an application. Outside of installing a puppet agent on each zone, looking for a way to assign an environment to each of the zones. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Alright, we just got off of a call with Nicholas Fagerlund and he helped us clarify our understanding of how all of this works. I think that as a result of that we landed basically where Henrik suggested: 1. We will not try to do anything for the old/hiera3 version of hiera.yaml that lives in the conf/codedir. 2. For environment/module versions of hiera.yaml, we were confused and thought that Puppet's hiera_config setting would come into play somehow. We now understand that it does not, and that the hiera.yaml filename is hard-coded into the data provider. So for this ticket, Jane Lu will add some logic that allows us to look for either hiera.conf or hiera.yaml in that directory, and parse the config accordingly. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2651) Make sure the console log clearly includes the pdbext version
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2651 Make sure the console log clearly includes the pdbext version Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6327) Puppet module tool should handle invalid paths better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6327 Puppet module tool should handle invalid paths better Change By: Branan Riley Sprint: Client 2016-07-27 facter.conf Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6327) Puppet module tool should handle invalid paths better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6327 Puppet module tool should handle invalid paths better Change By: Branan Riley Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6327) Puppet module tool should handle invalid paths better
Title: Message Title Branan Riley updated an issue Puppet / PUP-6327 Puppet module tool should handle invalid paths better Change By: Branan Riley Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Jane Lu updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Jane Lu Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6486) Bundle install fails to find proper puppet version when source is path or vcs
Title: Message Title Branan Riley updated an issue Puppet / PUP-6486 Bundle install fails to find proper puppet version when source is path or vcs Change By: Branan Riley Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6486) Bundle install fails to find proper puppet version when source is path or vcs
Title: Message Title Branan Riley updated an issue Puppet / PUP-6486 Bundle install fails to find proper puppet version when source is path or vcs Change By: Branan Riley Sprint: Client 2016-07-27 facter.conf Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6476) Add Hocon support to Puppet
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Karen Van der Veer Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5938) windows, user to groupassign to local administrators failed
Title: Message Title
Alberto Morando commented on PUP-5938
Re: windows, user to groupassign to local administrators failed
Hi
We have the same issue
These info maybe can help:
Server with Agent 1.3.0 is ok
Server with Agent 1.5.2 not ok ( latest version)
So I run a the
puppet apply --verbose -e "user { dk2ec004 : ensure => present, groups => ['Administrators'], password => password, }
"
with Agent 1.5.2 I get the error:
Info: Loading facts Notice: Compiled catalog for dkatest-ec1.corp.lego.com in environment production in 0.09 seconds Info: Applying configuration version '1468339806' Error: ADSI connection error: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Wrapped exception: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Error: /Stage[main]/Main/User[dk2ec004]/password: change from [old password hash redacted] to [new password hash redacted] failed: ADSI connection error: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Error: ADSI connection error: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Wrapped exception: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Error: /Stage[main]/Main/User[dk2ec004]/groups: change from to Administrators failed: ADSI connection error: failed to parse display name of moniker `WinNT://./dk2ec004,user' HRESULT error code:0x800708ad The user name could not be found. Notice: Applied catalog in 0.19 seconds
With Agent 1.3.0 (the same as the others servers) I get:
Info: Loading facts Notice: Compiled catalog for dkatest-ec1.corp.lego.com in environment production in 0.05 seconds Info: Applying configuration version '1468341690' Notice: Applied catalog in 0.19 seconds
And the User is created correctly in the Admin group
So I believe there is a bug in the new agent (I don´t know when it was introduced from verion 1.3.0 to version 1.5.2 (latest version)
Please let us know when fixed
Thanks
Add Comment
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Jane Lu yes, based on the other thread, I think we would be using .conf here. Henrik Lindberg for the first stab at this I think we probably wouldn't be changing anything in packaging. We might not even change the search path stuff - we could just say "iff you set your hiera config path to a file that ends with .conf, we will attempt to parse it as HOCON. Hopefully the result of that would give us just a raw data structure (Ruby map) that we could pass along to the consuming code in just the same way that you currently parse the YAML into a map (before deciding whether it is v3 or v4). Does that sound tractable? I don't have any issue with not supporting hiera 3 config format in HOCON if there is a win to be had there, but it seems like if the steps are just: find config file parse into a map pass map to lookup code so it can decide what version it is and how to perform lookups Then the HOCON bit doesn't even really care whether we're talking about hiera 3 or 4? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-2866) PuppetDB should always return JSON
Title: Message Title Brian Cain commented on PDB-2866 Re: PuppetDB should always return JSON It looks like PuppetDB does have some middleware class where it handles http requests. This is probably the place to catch top level exceptions like the one above and always return a 500 with the error code included as a json response. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Karen Van der Veer Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu updated an issue Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Jane Lu Sub-team: emerald Story Points: 2 Sprint: Server Emerald 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Karen Van der Veer Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu assigned an issue to Jane Lu Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Jane Lu Assignee: Jane Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu assigned an issue to Unassigned Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Jane Lu Assignee: Jane Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2866) PuppetDB should always return JSON
Title: Message Title Brian Cain created an issue PuppetDB / PDB-2866 PuppetDB should always return JSON Issue Type: Bug Assignee: Unassigned Created: 2016/07/12 9:44 AM Priority: Normal Reporter: Brian Cain If PuppetDB encounters an exception from a given query, or is given an incorrect query, it does not return json. This makes it difficult for the consumer to figure out what went wrong. With a query that causes an exception: ["=", "deactivated", false] [root@xevuii7pbf15o9l ~]# curl -G https://$(hostname -f):8081/pdb/query/v4/nodes --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem --cert /etc/puppetlabs/puppet/ssl/certs/xevuii7pbf15o9l.delivery.puppetlabs.net.pem --key /etc/puppetlabs/puppet/ssl/private_keys/xevuii7pbf15o9l.delivery.puppetlabs.net.pem --data-urlencode 'query=["=", "deactivated", false]'
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu assigned an issue to Jane Lu Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Jane Lu Assignee: Jane Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-523) Add support for using hocon for main hiera config file
Title: Message Title Jane Lu commented on HI-523 Re: Add support for using hocon for main hiera config file Just to be clear Henrik Lindberg, we are going to be using hiera.yaml and hiera.conf, not hiera.hocon correct? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2864) (WIP) Sync with threadpool
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2864 (WIP) Sync with threadpool Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Erick Banks assigned an issue to Unassigned Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Change By: Erick Banks Assignee: Erick Banks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2528) Expose PQL Parser in HTTP Endpoint
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2528 Expose PQL Parser in HTTP Endpoint Change By: Ryan Senior Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2785) spec tests failing against puppet master
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2785 spec tests failing against puppet master Change By: Ryan Senior Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6482) Puppet logging information leaks
Title: Message Title Adrien Thebo commented on PUP-6482 Re: Puppet logging information leaks Brian Conner thanks for this information! This ticket is an epic to collect individual stories/tickets where Puppet might inappropriately emit debug or error messages, so the actual work for this ticket will be collected in tickets as part of this epic. I'm going to break out your comment in a separate issue to track this. In addition we're going to be implementing part of PUP-1974 as part of PUP-6433; it'll take a while to fully plumb through sensitive data type support but we're working towards this end goal. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Kurt Wall Assignee: qa Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Murphy commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Ethan Brown Thanks for the info. First time posting, so I wasn't exactly sure what the procedure was. This is in Puppet open source 4.5.0, so I'll get more detail and open a new ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6482) Puppet logging information leaks
Title: Message Title Brian Conner commented on PUP-6482 Re: Puppet logging information leaks If an exec is run as an inline sh script with an eyaml'd password variable, the password will get logged in plaintext on the console and agent if it fails. loglevel and logoutput don't do anything in this situation, as it's the command that's being displayed, not the output of the command. It was suggested to make the command into a script and run it that way, but that presents putting the password plaintext in the script, not a viable long-term solution. Having the exec's inline sh script executed in this manner presents another issue. The same data is present in the cached catalog on agents in /opt/puppetlabs/puppet/cache/client_data/catalog/*.json. I imagine this issue is caught somewhere in https://tickets.puppetlabs.com/browse/PUP-1974. Just an idea to branch off of the "sensitive" resource type mentioned in PUP-1974: Most passwords and sensitve data will be coming from an eyaml'd variable(at least, in our scenario). If there were a setting in puppet.conf that would mark all eyaml data as "sensitive", hashing or masking it in logs and cached catalogs, that might take care of the lion's share of sensitive information leaks. This would be in addition to being able "to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which are sensitive". Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ethan Brown Sprint: Windows 2015-04-08 , Windows 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ryan Gard QA Contact: Eric Thompson Erick Banks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Ethan Brown possible regression? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ethan Brown commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Ryan Murphy thanks for your comment. Note that we typically don't reopen tickets that have gone through validation and closed, so I'm returning this back to it's closed state. If it's determined that there is another issue, we can open a new ticket. First however, your comment doesn't give enough detail to go on. The most important missing detail is the Puppet version. This bug was fixed in Puppet open source 3.8.0 and 4.1.0. If you're using an open source version earlier than that, or if you're using a PE version that doesn't include at least that version of Puppet, then you will experience this issue. Typically when submitting bug reports, you'll want to include as much detail as possible, including output of a puppet run performed with --trace --debug --verbose and manifest for reproducing the problem at a minimum. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ryan Gard Sprint: Windows 2015-04-08 , Windows 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Gard assigned an issue to Ethan Brown Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ryan Gard Assignee: Ryan Gard Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2865) Implement a quicker "inner loop" retry of commands
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2865 Implement a quicker "inner loop" retry of commands Issue Type: Bug Assignee: Unassigned Created: 2016/07/12 7:46 AM Priority: Normal Reporter: Ryan Senior Current versions of PuppetDB incur a high cost when a command is retried. The command gets written to a scheduler queue, then re-enqueued in the regular queue, then reprocessed. A very common case is a database transaction issue, where two commands are attempting to update the same data. One thread wins, one loses and has to be retried. We should implement a quicker "inner loop" retry, where we don't incur the I/O overhead in this common case. When the quick retries fail, we can then go through the normal retry logic. Add Comment
Jira (PUP-6330) puppet uninstall exe resource fails on windows due to missing quotes
Title: Message Title Max Greifenstein commented on PUP-6330 Re: puppet uninstall exe resource fails on windows due to missing quotes Craig, thanks for your answer. From my understanding, this is already the latest version of puppet agent for windows? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Murphy commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful I had this issue show up in Server 2008 R2 and Server 2012 R2 when attempting to remove a user. It seemed that Puppet would remove the user the first run but then error out every run after that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Murphy updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Ryan Murphy Comment: Found this issue in both Server 2008 R2 and Server 2012 R2 on domain joined servers.It seems to properly remove the user the first time, but when the Puppet agent re-runs and the user is gone, it errors out. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Ryan Murphy commented on PUP-1279 Re: Windows Group and User fail during deletion even though it is successful Found this issue in both Server 2008 R2 and Server 2012 R2 on domain joined servers. It seems to properly remove the user the first time, but when the Puppet agent re-runs and the user is gone, it errors out. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Ryan Coleman commented on PUP-6042 Re: `puppet agent --test` does not override cached catalog behavior Adrien Thebo, it's the same use case as most other cases for agent -t, evaluating a change or debugging a problem locally. Say you run an orchestration job (or mcollective/dssh for that matter) but have node failures or unexpected results. The best way to obtain tighter feedback is to log onto the problem node and interactively run puppet agent -t. Yes, of course, the customer will get new catalogs. That's implied by the dormant ignorecache option that doesn't do anything today anyway. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better That's a good point Kylo Ginsberg, I'll check if that module still has this problem before moving ahead with anything else. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6485) make it easier to require based on tag
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6485 make it easier to require based on tag Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6492) Reports are not stored for current node
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6492 Reports are not stored for current node Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2016/07/12 12:57 AM Priority: Normal Reporter: Julien Pivotto In a 4 nodes environment, When Running Puppet agent --test, with report = true and reports = store in the directory /opt/puppetlabs/puppet/cache/reports I only see reports for the 3 nodes that are NOT the puppetserver On the Puppet server, the agent reports for the server host itself are not saved in /opt/puppetlabs/puppet/cache/reports Add Comment
