Jira (PUP-1188) Extract Modulefile parsing in a separate gem
Title: Message Title Ringo De Smet commented on an issue Re: Extract Modulefile parsing in a separate gem I'm not following Puppet development that closely. If the Modulefile is going away, how will dependencies between modules be expressed? If this information is just going to shift to some other file, then I think the problem remains. Add Comment Puppet / PUP-1188 Extract Modulefile parsing in a separate gem We all love librarian-puppet. While that gem states it does not depend on the Puppet gem, it's internals *do* use Puppet Ruby code directly: to extract some metadata from the Modulefile for modules retrieved via Git: https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/source/git.rb#L86 There are a few issues and pull requests... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-1720) Using a parameterized class that doesn't exist results in a confusing error.
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1720
Using a parameterized class that doesn't exist results in a confusing error.
Issue Type:
Bug
Assignee:
Unassigned
Created:
17/Feb/14 2:28 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Error message: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type class at ...
I expected that 'include foo' and 'class { foo: ...; }
' should result in the same error message if class 'foo' does not exist.
For example:
pre % puppet apply -e 'include notbar' Could not find class notbar at line 1 on node snack.home
% puppet apply -e 'class { notbar: ; }
' Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type class at line 1 on node snack.home /pre
Confirmed this problem is in both 2.6.2 and 2.6.3
Add Comment
Jira (PUP-1721) Version 3.4.2 broken on FreeBSD
Title: Message Title Jo Rhett created an issue Puppet / PUP-1721 Version 3.4.2 broken on FreeBSD Issue Type: Bug Affects Versions: 3.4.2 Assignee: Unassigned Created: 17/Feb/14 2:52 AM Environment: FreeBSD fireagate 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Priority: Normal Reporter: Jo Rhett After upgrading Puppet to 3.4.2 on FreeBSD, I now receive the following tagmail output for every scheduled run. Mon Feb 17 02:22:00 -0800 2014 /File[/var/puppet/lib] (err): Failed to generate additional resources using 'eval_generate: uninitialized constant Puppet::FileSystem::File Mon Feb 17 02:22:00 -0800 2014 Puppet (err): Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Mon Feb 17 02:22:00 -0800 2014 Puppet (err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation There is no evidence that the system is receiving a catalog from the puppetmaster. It has disappeared from the messages
Jira (PUP-1721) Version 3.4.2 broken on FreeBSD
Title: Message Title
Jo Rhett commented on an issue
Re: Version 3.4.2 broken on FreeBSD
Environment details for this host:
root@fireagate etc$ ruby --version
ruby 1.9.3p484 (2013-11-22 revision 43786) [amd64-freebsd9]
root@fireagate etc$ puppet --version
3.4.2
root@fireagate etc$ pkg info puppet
puppet-3.4.2_2
Name : puppet
Version: 3.4.2_2
Installed on : Sun Feb 16 22:00:31 PST 2014
Origin : sysutils/puppet
Architecture : freebsd:9:x86:64
Prefix : /usr/local
Categories : sysutils
Licenses : APACHE20
Maintainer : swi...@freebsd.org
WWW: http://www.puppetlabs.com
Comment: A configuration management framework written in Ruby
Options:
DOCS : on
EXAMPLES : on
PACKAGE_ORIGIN : on
PACKAGE_ROOT : off
Flat size : 3.65MiB
Description:
Puppet lets you centrally manage every important aspect of your system using
a cross-platform specification language that manages all the separate
elements normally aggregated in different files, like users, cron jobs, and
hosts, along with obviously discrete elements like packages, services, and
files.
WWW: http://www.puppetlabs.com
Add Comment
Puppet / PUP-1721
Version 3.4.2 broken on FreeBSD
After upgrading Puppet to 3.4.2 on FreeBSD, I now receive the following tagmail output for every scheduled run. {code} Mon Feb 17 02:22:00 -0800 2014 /File[/var/puppet/lib] (err): Failed to generate additional resources using 'eval_generate: uninitialized constant Puppet::FileSystem::File Mon Feb 17 02:22:00 -0800 2014 Puppet (err): Could not autoload ...
Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs
Title: Message Title Dominic Cleal created an issue Puppet / PUP-1722 Yumrepo doesn't permit HTTPS URLs Issue Type: Bug Affects Versions: 3.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 17/Feb/14 5:14 AM Priority: Normal Reporter: Dominic Cleal Since PUP-789, the yumrepo type doesn't permit HTTPS URLs in yumrepo definitions. These are valid for base URLs, mirror lists etc and are used particularly by Fedora. $ bin/puppet resource yumrepo test baseurl=https://example.com Error: Could not run: Parameter baseurl failed on Yumrepo[test]: Must be a valid URL Wrapped exception: Must be a valid URL Add Comment
Jira (PUP-1723) Yumrepo logs info messages without context
Title: Message Title Dominic Cleal created an issue Puppet / PUP-1723 Yumrepo logs info messages without context Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 17/Feb/14 5:27 AM Priority: Trivial Reporter: Dominic Cleal Since PUP-789, the yumrepo inifile provider logs two messages without any context (e.g. the resource or provider). create new repo SCL in file /etc/yum.repos.d/SCL.repo /Stage[main]/Foreman::Install::Repos::Extra/Yumrepo[SCL]/ensure: created changing mode of /etc/yum.repos.d/SCL.repo from 600 to 644 The provider code calls Puppet.info currently when it should use just info to add context. As these are class utility methods, it should ideally use the context from the instance to provide even better context, related to the resource that made the change. Add Comment
Jira (PUP-864) Deprecate Data Structure Mutation
Title: Message Title
Igor Galić commented on an issue
Re: Deprecate Data Structure Mutation
Are there any (style?) guidelines on how to handle operations where mutations so far have been used? Example from puppetlabs-apache: https://github.com/puppetlabs/puppetlabs-apache/issues/625
Add Comment
Puppet / PUP-864
Deprecate Data Structure Mutation
The puppet language right now allows: {code} $a = [1, 2, 3] $a[3] = 4 {code} This should produce a deprecation warning about the assignment on line 2.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs
Title: Message Title Dominic Cleal assigned an issue to Dominic Cleal Puppet / PUP-1722 Yumrepo doesn't permit HTTPS URLs Change By: Dominic Cleal Assignee: DominicCleal Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-337) facter/master on solaris 11: Caught recursion on virtual
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-337 facter/master on solaris 11: Caught recursion on virtual Change By: Kylo Ginsberg Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-462) HTTP/2.0
Title: Message Title Kenneth Barber commented on an issue Re: HTTP/2.0 Christopher Price has already been working to switch us to Jetty 9 which introduces SPDY v3 support at least, what work is required to enable that is another thing: https://github.com/puppetlabs/puppetdb/pull/826. Of course SPDY 3.1 is out now, which Jetty doesn't seem to support yet (at least I can't see anything indicated so in 9.0 or 9.1 release notes). So really, we're beholden to Jetty and when the standard comes out, and we'll have to jump on that version that supports it. But for now at least we have the potential to support some of the features with the SPDY v3 protocol. So probably what is more immediately valuable would be a ticket to enable SPDY support, since we can probably do that once that PR I mentioned gets merged in. Christopher Price have you had any thoughts in this direction yet? Add Comment PuppetDB / PDB-462 HTTP/2.0 As a spec for HTTP/2.0 is starting to slowly emerge and people are starting to experiment with it I think it's a good time to bring up this issue. I'm sure some investigation will have to be done and the libraries that are used will have to be updated to support HTTP/2.0. Even though it's still early days it there should at least be an issue about it. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1513) 'puppet doc' does not correctly parse hashes with facts on the left hand side.
Title: Message Title
Trevor Vaughan commented on an issue
Re: 'puppet doc' does not correctly parse hashes with facts on the left hand side.
Sorry, I just realized that I responded directly but not back here.
That technique does indeed work but is certainly doesn't help maintain a clean code base.
Add Comment
Puppet / PUP-1513
'puppet doc' does not correctly parse hashes with facts on the left hand side.
Parsing the following code block fails with the error: Error: Could not generate documentation: Syntax error at '::fqdn'; expected '}'. {code} $foo = { $::fqdn = 'bar' } {code} This code parses correctly using puppet lint and applies properly in production.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-1724) deep_merge in stdlib clobbers the first parameter
Title: Message Title
Justin Burnham created an issue
Puppet / PUP-1724
deep_merge in stdlib clobbers the first parameter
Issue Type:
Bug
Assignee:
Unassigned
Created:
17/Feb/14 12:19 PM
Priority:
Normal
Reporter:
Justin Burnham
Example:
class foo {
$bar = { foo = { bar = 1 } }
}
include foo
$bar_updates = { foo = { baz = 1 } }
alert $foo::bar
$baz = deep_merge( $foo::bar, $bar_updates )
alert $foo::bar
Current output:
alert: Scope(Class[main]): foobar1
alert: Scope(Class[main]): foobaz1bar1
Expected:
alert: Scope(Class[main]): foobar1
alert: Scope(Class[main]): foobar1
Add Comment
Jira (PUP-1724) deep_merge in stdlib clobbers the first parameter
Title: Message Title
Justin Burnham commented on an issue
Re: deep_merge in stdlib clobbers the first parameter
https://github.com/puppetlabs/puppetlabs-stdlib/pull/220
Add Comment
Puppet / PUP-1724
deep_merge in stdlib clobbers the first parameter
Example: {noformat} class foo { $bar = { foo = { bar = 1 } } } include foo $bar_updates = { foo = { baz = 1 } } alert $foo::bar $baz = deep_merge( $foo::bar, $bar_updates ) alert $foo::bar {noformat} Current output: {noformat} alert: Scope(Class[main]): foobar1 alert: Scope(Class[main]): foobaz1bar1 {noformat} Expected: {noformat} ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Aaron John-Baptiste commented on an issue Re: Some modules fail to install into target_dir Also same problem on Ubuntu 12.10 Add Comment Puppet / PUP-1639 Some modules fail to install into target_dir puppet module install puppetlabs/apache -i puppet/forge-modules Notice: Preparing to install into /home/www/puppet/forge-modules ... Notice: Created target directory /home/www/puppet/forge-modules Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file or directory - /home/www/puppet/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-864) Deprecate Data Structure Mutation
Title: Message Title
Dominic Cleal commented on an issue
Re: Deprecate Data Structure Mutation
merge() perhaps from stdlib?
$_directory = {
provider = 'directory',
path = $docroot,
options = $options,
allow_override = $override,
directoryindex = $directoryindex,
}
if $apache_version == 2.4 {
$_directory_version = {
require = 'all granted',
}
} else {
$_directory_version = {
order = 'allow,deny',
allow = 'from all',
}
}
$_directories = [ merge($_directory, $_directory_version) ]
Add Comment
Puppet / PUP-864
Deprecate Data Structure Mutation
The puppet language right now allows: {code} $a = [1, 2, 3] $a[3] = 4 {code} This should produce a deprecation warning about the assignment on line 2.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (PUP-1397) hyphen in class name messes with qualified variables
Title: Message Title Henrik Lindberg commented on an issue Re: hyphen in class name messes with qualified variables Yes, deprecation warnings are needed. Add Comment Puppet / PUP-1397 hyphen in class name messes with qualified variables $module::class-name::variable This tricks puppet. I suppose it thinks the - is a minus... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-864) Deprecate Data Structure Mutation
Title: Message Title
Henrik Lindberg commented on an issue
Re: Deprecate Data Structure Mutation
Now, there is also a PR for merge See PUP-1724
Add Comment
Puppet / PUP-864
Deprecate Data Structure Mutation
The puppet language right now allows: {code} $a = [1, 2, 3] $a[3] = 4 {code} This should produce a deprecation warning about the assignment on line 2.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Stefan Schulte updated an issue Facter / FACT-234 Add Facts showing the UUID of partitions Change By: Stefan Schulte Fix Version/s: 2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-115) hiera recursive guard
Title: Message Title Charlie Sharpsteen updated an issue Hiera / HI-115 hiera recursive guard Change By: Charlie Sharpsteen Affects Version/s: 1.3.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
