Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Josh Cooper commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Sounds like you're running into FACT-722 , where dmi returns binary data. It should be fixed in facter 2.2.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-7038) Deprecate ruby 2.0.0 support
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7038 Deprecate ruby 2.0.0 support Change By: Geoff Nichols Sprint: AP 2017-01-11 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-6885) Remove warning about server_list and server conflicting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6885 Remove warning about server_list and server conflicting Change By: Geoff Nichols Fix Version/s: PUP 4.9.0 Fix Version/s: PUP 5.0.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-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 1. I can't RCA the issue of only running the 1900 tests as the logs for that job have been lost and it has not occurred since. 2. I've updated the Hiera and MCO job configs so they now output Test Results into Jenkins so at least the test count can be audited 3. The ci:test:quick behaviour is not documented anywhere that I could find. I trawled through the source code to find that. Note that the full set of acceptance tests is run, but as part of the puppet-agent acceptance suite, not part of puppet. This looks like it's just a smoke acceptance test run. I cannot see this quick code in any of our other pipelines 4. I have noticed that the MCO acceptance tests (https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_marionette-collective_intn-van-sys_master/configure) doesn't actually run anything. echo "" echo "Running Tests:" echo "true" echo "" Add Comment
Jira (PUP-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Ethan Brown commented on PUP-7014 Re: Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Glenn Sarti is your final assessment that the cause of this was due to only running against "recently modified tests"? As we briefly discussed, I'm not sure that that approach is a good heuristic for determining which tests to run. Do we have the variable nature documented somewhere? How many pipelines does it impact? etc etc 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-6993) Puppet acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown commented on PUP-6993 Re: Puppet acceptance test failures for Japanese Windows I think this should be safe to move to done Glenn Sarti - was mostly just making sure no CI failures showed up and that the changes look sane. 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-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title Thomas Hallgren commented on PUP-7061 Re: Multiple hiera functions in one string does not work with hiera v4 I tested your nested lookup on 4.8.1 and it works OK. Can you do a lookup from command line? I.e. puppet lookup profile::php::proxy 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-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title
Jan Kröpke commented on PUP-7061
Re: Multiple hiera functions in one string does not work with hiera v4
root@puppet:/var/cache/puppet# /opt/puppetlabs/server/bin/puppetserver --version puppetserver version: 2.7.2 root@puppet:/var/cache/puppet# puppet -V 4.8.1
I'm on a fresh installed system (deployed 2017-01-01), i'm using Ubuntu 16.04 w/ upstream packages.
I also have some lines like:
profile::php::proxy: "%{hiera('profile::proxy::url')}"
Maybe the nested variable lookup cause is a problem.
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-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7061 Multiple hiera functions in one string does not work with hiera v4 Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title Thomas Hallgren commented on PUP-7061 Re: Multiple hiera functions in one string does not work with hiera v4 I don't recognize this error. Judging by the code, it should be impossible to get that error. Current master of invocation.rb looks like this: @name_stack.push(name) begin yield rescue Puppet::DataBinding::LookupError raise rescue Puppet::Error => detail raise Puppet::DataBinding::LookupError.new(detail.message, detail) ensure @name_stack.pop # <--- This is line 79 where the "undefined method `pop' for nil:NilClass" occurs end
Jira (PUP-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title Thomas Hallgren assigned an issue to Jan Kröpke Puppet / PUP-7061 Multiple hiera functions in one string does not work with hiera v4 Change By: Thomas Hallgren Assignee: Thomas Hallgren Jan Kröpke 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-7014) Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 20000
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-7014 Audit CI.next pipelines to ensure all tests are being run / RCA the Windows passing runs that ran 1900 tests instead of 2 Change By: Glenn Sarti Assignee: Ethan Brown 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-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Henrik Lindberg, this is how legacy Hiera 3 works. In my mind this was a flaw in backward compatibility that is now fixed. No release note needed (lookup support for Hiera 3 hasn't been released 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 (FACT-1554) spaces in a facts.d text file, may cause confusion
Title: Message Title Michael Smith updated an issue Facter / FACT-1554 spaces in a facts.d text file, may cause confusion Change By: Michael Smith 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 (FACT-1554) spaces in a facts.d text file, may cause confusion
Title: Message Title Michael Smith updated an issue Facter / FACT-1554 spaces in a facts.d text file, may cause confusion Change By: Michael Smith Affects Version/s: FACT 3.5.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 (FACT-1554) spaces in a facts.d text file, may cause confusion
Title: Message Title Michael Smith commented on FACT-1554 Re: spaces in a facts.d text file, may cause confusion It probably should (or at least "should have") stripped spaces. This appears to still be a usability issue in Facter 3. To query that fact I have to double-escape the key, as in facter '"mykey "'. 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-1554) spaces in a facts.d text file, may cause confusion
Title: Message Title
Michael Smith updated an issue
Facter / FACT-1554
spaces in a facts.d text file, may cause confusion
Change By:
Michael Smith
If I have a /etc/facter/facts.d/foo.txtand in that have:mykey = value# which should actually be:#mykey=valuefacter | grep mykeywill happily show mykey => valuewhich DOES have extra spaces in it, so " {{ mykey => value " }} instead of " {{ mykey => value " }} but if it's January 2nd and you are just back from holidays you might not notice the extra spacing ;) . It might be good to wrap this kind of thing in quotes or something to emphasise that the user has entered extra spacing.or ignore and close this issue, cuz user error. ;)Have a good day.-Shawn
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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Thomas Kishel commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Reviewing our list of package providers, I see two types of providers: single-instance and multiple-instance. For the single-instance providers, such as yum, there
should
be only one executable, and it
should
be in PATH. For multiple-instance providers, such as gem, there could be n-number of instances, each with its own executable and none of them may be in PATH. We recognize this with our puppet_gem provider, which differs from the gem provider only in that it defines an absolute path to :gemcmd (except on Windows).
The provider attribute of a package is, in practice, overloaded as a command attribute: but is an attribute that does not accept an absolute path. An optional command (or to a lesser extent{{environment}} and/or path) attribute for providers, as implemented in the Exec resource type would support multiple-instance providers without requiring a custom provider type for each instance.
So, I agree that an attribute-based solution would be preferable to the PR, which is limited to addressing this issue for one provider on one operating system. Modifying the package type is larger in scope, and may best be executed by someone else, but I'm willing.
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.go
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Corey Osman commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' command This is occuring on my setup as well. Using PE 2016.04.02 . It is super easy to reproduce. config = `puppet config print config` cat > $config << 'EOF' [main] environment = dev EOF puppet config print environment Add Comment
Jira (PUP-5958) Docs: Update installer screenshots when branding work is finished
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-5958 Docs: Update installer screenshots when branding work is finished Change By: Jorie Tappa Story Points: 1 Sprint: AP 2017-01-11 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-7067) hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Title: Message Title
Henrik Lindberg commented on PUP-7067
Re: hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
merged to master at: 156f601
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-7066) Revert #5237 and modify to return string content with deprecation
Title: Message Title Moses Mendoza assigned an issue to Ethan Brown Puppet / PUP-7066 Revert #5237 and modify to return string content with deprecation Change By: Moses Mendoza Assignee: Ethan Brown 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-7051) Static catalog compiler uses Puppet master hostname for %H in fileserver config
Title: Message Title Jeremy Barlow commented on PUP-7051 Re: Static catalog compiler uses Puppet master hostname for %H in fileserver config It would be great to get a backtrace to see what code path we took to get to: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/mount/file.rb#L70 Here's what I get when running Puppet from source at the 4.8.1 tag: /puppet/lib/puppet/file_serving/configuration/parser.rb:119:in `validate' /puppet/lib/puppet/file_serving/configuration/parser.rb:119:in `each' /puppet/lib/puppet/file_serving/configuration/parser.rb:119:in `validate' /puppet/lib/puppet/file_serving/configuration/parser.rb:48:in `parse' /puppet/lib/puppet/file_serving/configuration.rb:99:in `readconfig' /puppet/lib/puppet/file_serving/configuration.rb:38:in `initialize' /puppet/lib/puppet/file_serving/configuration.rb:13:in `configuration' /puppet/lib/puppet/indirector/file_server.rb:49:in `configuration'
Jira (PUP-7066) Revert #5237 and modify to return string content with deprecation
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7066 Revert #5237 and modify to return string content with deprecation Change By: Moses Mendoza Fix Version/s: PUP 4.7.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 (PUP-7057) User provider shows plaintext password when it changes a managed users password
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7057 User provider shows plaintext password when it changes a managed users password Change By: Moses Mendoza Labels: product- security security 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-7057) User provider shows plaintext password when it changes a managed users password
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7057 User provider shows plaintext password when it changes a managed users password Change By: Moses Mendoza Labels: Windows security 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-7057) User provider shows plaintext password when it changes a managed users password
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7057
User provider shows plaintext password when it changes a managed users password
Change By:
Moses Mendoza
When the user provider changes a managed users password, the plaintext password is shown in the console even if the password is encrypted in hiera.To reproduce: 1) In PE Console go to report where the password was changed. 2) Click on Events tab 3) Under resource type click user 4) The User resource will show the password in the Changed to column. *Notes*- Currently, Puppet will include password value(s) in the resource event logs when they change. This means passwords are written to the reports in plain text (though these reports are only root-readable).- The {{Sensitive}} type was recently added to Puppet, which obscures associated values where applicable. Ostensibly passwords are sensitive information and are applicable for this new type.*In Scope*- Plumb the {{Sensitive}} data type through the Puppet type system as needed, if at all, so that we can:- Set the {{password}} property of the {{user}} type to {{Sensitive}}. This will then apply to all {{user}} providers.
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
Jira (PUP-7057) User provider shows plaintext password when it changes a managed users password
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7057 User provider shows plaintext password when it changes a managed users password Change By: Moses Mendoza Fix Version/s: PUP 5.0.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-6847) The network_device configuration parser should not accept trailing whitespace
Title: Message Title Geoff Nichols assigned an issue to Rick Sherman Puppet / PUP-6847 The network_device configuration parser should not accept trailing whitespace Change By: Geoff Nichols Assignee: Rick Sherman 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-7051) Static catalog compiler uses Puppet master hostname for %H in fileserver config
Title: Message Title Josh Cooper commented on PUP-7051 Re: Static catalog compiler uses Puppet master hostname for %H in fileserver config Due to custom mount points, etc it is possible for the static compiler to inline most metadata, but exclude metadata for individual file resources. We should only attempt in inline file metadata if the following are true: 1) the file source URI uses the puppet scheme, 2) the source URI path starts with the modules (using the modules mount point, 2) the files being served are in a files directory as they would be for a module, etc. See https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/indirector/catalog/compiler.rb#L114-L125 https://github.com/puppetlabs/puppet/blob/4.8.1/lib/puppet/indirector/catalog/compiler.rb#L130-L136. That said it seems like the static compiler is trying to inline something when it shouldn't? It would be great to get a backtrace to see what code path we took to get to: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/mount/file.rb#L70 It would also be useful to get fileserver.conf and any mount related configuration. 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-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Geoff Nichols commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Current versions of Puppet have fixed a number of UTF-8 related issues. Any chance you could try to reproduce this in Puppet 4.8.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 (PDOC-149) Style Guide: add Strings info
Title: Message Title Jean Bond commented on PDOC-149 Re: Style Guide: add Strings info Duplicate of DOCUMENT-597 (my bad!). Advice to use Strings has been added to the Style Guide, with a reference to the Puppet Strings docs. The style guide is not the right place for the instructions, despite my earlier comment. 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-7057) User provider shows plaintext password when it changes a managed users password
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7057 User provider shows plaintext password when it changes a managed users password Change By: Geoff Nichols Sprint: AP Grooming 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-7009) Git acceptance broken on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7009 Git acceptance broken on Windows 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 (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units 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 (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support 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 (PUP-7066) Revert #5237 and modify to return string content with deprecation
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7066 Revert #5237 and modify to return string content with deprecation Change By: Moses Mendoza Assignee: Moses Mendoza 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-7070) Remove stacktrace property of http error response object
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Issue Type: Task Assignee: Unassigned Created: 2017/01/05 9:48 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Moses Mendoza We deprecated this property with PUP-7066 for security reasons. It can be removed in Puppet 5. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7050 Puppet apply is not reporting when fails to compile the catalog Change By: Henrik Lindberg Assignee: Peiman 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-7050) Puppet apply should send report when it fails to compile the catalog
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7050 Puppet apply should send report when it fails to compile the catalog Change By: Henrik Lindberg Summary: Puppet apply is not reporting should send report when it fails to compile the catalog 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Henrik Lindberg commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog Clear now! 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Peiman commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog This is nothing to do with Foreman. As R.I.Pienaar mentioned puppet apply will not create any type of reports (store, foreman, HTTP, ... ) if puppet has a failure while compiling the catalog but if we were using puppet master it would report if it fails to compile a catalog. 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-3241) Tests failing with "Maximum of 5000 keypairs reached"
Title: Message Title Doug Rosser commented on PDB-3241 Re: Tests failing with "Maximum of 5000 keypairs reached" I am going through the ESO-Puppetlabs AWS console and deleting every keypair with "2015" in the name. This should clear up some space. 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-3241) Tests failing with "Maximum of 5000 keypairs reached"
Title: Message Title Doug Rosser commented on PDB-3241 Re: Tests failing with "Maximum of 5000 keypairs reached" Looks like Beaker (wrapping the ruby AWS::SDK) is creating a new keypair with every run. 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-7048) Scoped context information to be displayed only when error occurs
Title: Message Title Henrik Lindberg commented on PUP-7048 Re: Scoped context information to be displayed only when error occurs Ah, got it right after I posted that. You would only want the information logged if there is a general error where puppet bails out. Sort of having a "catch" _expression_ that produces the information. Since we have no such thing, you would instead push the information and keep it until an error. Also, note that in late puppet 4.x the stack trace produced for an error contains references to .pp files and line numbers. This enables understanding the complete stack trace in puppet logic - not just the ruby code used to evaluate the puppet code. (There is even an API for stack information that allows ruby logic to reflect and produce better error messages based on the puppet call stack). In general the call stack of puppet is difficult due to the lazy evaluation that puppet does. As an example, an 'include' would occur immediately and would be in a nested context, whereas any resource instantiation is not. A resource could also be requested from multiple contexts meaning you would want to get the trace information from all those locations. That would require some kind of stack associated with each resource. The more I think about this, the messier it gets. 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title R.I.Pienaar commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog Henrik Lindberg Puppet should report on failures so people can find out about it on their dashboards (foreman or otherwise), agent behaved like apply does in the distant past - did not report on serious errors - but that got added at some point, apply must be using a different code path that did not get this feature. So this should be to add that feature where it report on these kind of critical issues 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Henrik Lindberg commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog R.I.Pienaar Are you saying puppet apply should report, or that that is what is happening in Peiman's case, and it needs to be considered by him and/or Foreman? 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-7048) Scoped context information to be displayed only when error occurs
Title: Message Title Henrik Lindberg commented on PUP-7048 Re: Scoped context information to be displayed only when error occurs What is it you cannot do with the logging functions already available in Puppet? What I have found missing is information in the error message to the agent that makes it easy to find the relevant information in the log on the master side. The issue is that all information cannot be sent in that error to the agent - it may be bulky and it is a potential security problem that may be exploited. 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-7048) Scoped context information to be displayed only when error occurs
Title: Message Title Henrik Lindberg assigned an issue to Matthias Hörmann Puppet / PUP-7048 Scoped context information to be displayed only when error occurs Change By: Henrik Lindberg Assignee: Matthias Hörmann 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-7069) puppet module generate fails on windows
Title: Message Title David Schmitt updated an issue Puppet / PUP-7069 puppet module generate fails on windows Change By: David Schmitt Environment: Windows 2012 R2;Ruby 2.3.1 installed from chocolateyPuppet 4.8.1 installed as gem 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title R.I.Pienaar commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog a good apply run reports: [rip@dev4]% puppet apply --report -e 'notice()' --debug|tail -5 <17:18:09 Debug: Finishing transaction 29848620 Debug: Received report to process from dev4.devco.net Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Processing report from dev4.devco.net with processor Puppet::Reports::Store a bad one doesnt: % puppet apply --report -e 'foo foo foo' --debug 2>&1|tail -5 }.
Jira (PUP-7069) puppet module generate fails on windows
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-7069
puppet module generate fails on windows
Change By:
David Schmitt
When creating a new module using {{puppet module generate}} the tool fails at the very end with an error very similar to PUP-4884:{code} tbd PS C:\vagrant> puppet module generate puppetlabs-picktest2 --trace --skip-interview Notice: Generating module at C:\vagrant/picktest2...Notice: Populating templates...Error: No such file or directory @ dir_s_rmdir - C:/vagrant/picktest2/metadata.json.erbc:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:240:in `unlink'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:240:in `unlink'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:240:in `block (2 levels) in populate_templates'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:234:in `each'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:234:in `block in populate_templates'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:231:in `each'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:231:in `populate_templates'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:219:in `duplicate_skeleton'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:140:in `generate'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/face/module/generate.rb:126:in `block (3 levels) in 'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application/face_base.rb:48:in `call'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application/face_base.rb:48:in `render'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application/face_base.rb:249:in `main'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application.rb:352:in `run_command'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application.rb:344:in `block in run'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/util.rb:540:in `exit_on_fail'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/application.rb:344:in `run'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/util/command_line.rb:132:in `run'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/lib/puppet/util/command_line.rb:72:in `execute'c:/tools/ruby23/lib/ruby/gems/2.3.0/gems/puppet-4.8.1-x64-mingw32/bin/puppet:5:in `'c:/tools/ruby23/bin/puppet:23:in `load'c:/tools/ruby23/bin/puppet:23:in `'Error: Try 'puppet help module generate' for usagePS C:\vagrant> {code}
Jira (PUP-7069) puppet module generate fails on windows
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-7069
puppet module generate fails on windows
Change By:
David Schmitt
When creating a new module using {{puppet module generate}} the tool fails at the very end with an error very similar to PUP-4884:{code}tbd{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.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7069) puppet module generate fails on windows
Title: Message Title David Schmitt updated an issue Puppet / PUP-7069 puppet module generate fails on windows Change By: David Schmitt Affects Version/s: PUP 4.8.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 (PUP-7069) puppet module generate fails on windows
Title: Message Title David Schmitt created an issue Puppet / PUP-7069 puppet module generate fails on windows Issue Type: Bug Assignee: Unassigned Created: 2017/01/05 8:08 AM Priority: Normal Reporter: David Schmitt 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.c
Jira (PUP-7069) puppet module generate fails on windows
Title: Message Title David Schmitt updated an issue Puppet / PUP-7069 puppet module generate fails on windows Change By: David Schmitt Component/s: Windows Component/s: PMT 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-7069) puppet module generate fails on windows
Title: Message Title David Schmitt updated an issue Puppet / PUP-7069 puppet module generate fails on windows Change By: David Schmitt Labels: windows 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-6659) Information Disclosure - Puppet Server Stacktraces
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6659 Information Disclosure - Puppet Server Stacktraces Change By: Kenn Hussey Team: Agent & Platform Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 4.8.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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Henrik Lindberg assigned an issue to Peiman Puppet / PUP-7050 Puppet apply is not reporting when fails to compile the catalog Change By: Henrik Lindberg Assignee: Peiman 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title Henrik Lindberg commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog Peiman - there is very little (to no) information here that helps recreate the error without Foreman being used. Can you provide a reproducible case? If not, it will be close to impossible for us to help you out. Also, try hopping on to Slack and ask for help, and talk to the Foreman folks if this is a problem they know about. 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-7061) Multiple hiera functions in one string does not work with hiera v4
Title: Message Title Henrik Lindberg commented on PUP-7061 Re: Multiple hiera functions in one string does not work with hiera v4 Jan Kröpke Can you provide information about the version of Puppet you are using? Ping Thomas Hallgren - any known issues that comes to mind? IIRC, we have fixed this already. 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-7067) hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-7067
hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Change By:
Thomas Hallgren
Acceptance Criteria:
The lookup framwork uses a default Hiera 3 configuration when the hiera.yaml file exists but is empty (as is the case for _/dev/null_).
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-7067) hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Title: Message Title
Thomas Hallgren assigned an issue to Unassigned
Puppet / PUP-7067
hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Change By:
Thomas Hallgren
Assignee:
Thomas Hallgren
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Thomas Hallgren Does this require a release note - or is this only for the internal support of being able to create a second "special" instance? 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-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml merged to master at: 80b7539 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-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Henrik Lindberg commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 It is quite a long chain that leads up to using facts and getting the error in question and I think some detective work is required in order to isolate the problem in order to reproduce at our end. First the chain of things: Custom fact logic is synced with agent - check if any fact implementation (ruby files etc) have non UTF-8 chars in them Facter runs to produce facts - check if a facter run produces data that is not UTF-8 A scheduled run on an agent runs facter and sends the facts to the master The master stores the facts in a cache & puppet DB - check if stored facts are corrupted The master retrieves the facts from cache/store and uses them when compiling a catalog - this is where you see the error. I suspect that the logic that does this is not to blame (unless possibly if server is running with non UTF-8 encoding) Ping Josh Cooper - any thoughts, known issues, etc.? 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 s
Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7068 Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7067) hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Title: Message Title
Thomas Hallgren assigned an issue to Thomas Hallgren
Puppet / PUP-7067
hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Change By:
Thomas Hallgren
Assignee:
Thomas Hallgren
Story Points:
1
Team:
Puppet Developer Experience
Sprint:
PDE 2017-01-11
Fix Version/s:
PUP 4.9.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 unsubscri
Jira (PUP-7045) Installing gems from rubygems.org using the packaged gem command fails with SSL error
Title: Message Title David Schmitt commented on PUP-7045 Re: Installing gems from rubygems.org using the packaged gem command fails with SSL error I'll try that next time around. 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-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7068 Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/01/05 3:39 AM Fix Versions: PUP 4.9.0 Priority: Normal Reporter: Thomas Hallgren A datadir that is defined as a relative path in a Hiera version 3 configuration must be treated as relative to the current working directory and not, as it is now, relative to the directory where the hiera.yaml file resides. Add Comment
Jira (PUP-7067) hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Title: Message Title
David Schmitt created an issue
Puppet / PUP-7067
hiera: YAML.load_file('/dev/null') returns `false`, instead of a hash
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/01/05 2:38 AM
Priority:
Normal
Reporter:
David Schmitt
331778e from PUP-6980 caused hiere to call YAML.load_file('/dev/null') in some situations, which returns `false`, instead of a hash, leading to failures. This e.g. breaks rspec-puppet's setup shenanigans: https://github.com/rodjek/rspec-puppet/issues/434
That link also has a stack-trace and travis log showing the problem.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7053) Test utf8_user_comments.rb fails to create user with UTF-8 comment on AIX
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-7053 Test utf8_user_comments.rb fails to create user with UTF-8 comment on AIX Change By: Kurt Wall Assignee: Kurt Wall 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-7053) Test utf8_user_comments.rb fails to create user with UTF-8 comment on AIX
Title: Message Title Kurt Wall commented on PUP-7053 Re: Test utf8_user_comments.rb fails to create user with UTF-8 comment on AIX Validated in puppet-agent 1.8.2.393.ge573003. https://jenkins.puppetlabs.com/view/puppet-agent/view/manual/view/master/job/platform_puppet-agent_intn-van-sys_suite-manual-puppet-master/68/SLAVE_LABEL=beaker,TEST_TARGET=aix-53-power/testReport/(root)/tests_resource_user/utf8_user_comments_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.
