Jira (PUP-1394) NFS on Fedora 20 requires both path and device
Title: Message Title
Juraci Paixo Krhling commented on an issue
Re: NFS on Fedora 20 requires both path and device
I'm not sure if this is still the case (this ticket was opened in Jan, and it's Jun), but this is how I specified it:
mount {'/mnt/backups':
atboot = 'true',
fstype = 'nfs',
ensure = mounted,
device = '192.168.122.1:/mnt/storage/backups',
require = [File['/mnt/backups'], Package['nfs-utils']],
}
I remember having to manually change the file /usr/share/ruby/vendor_ruby/puppet/provider/mount.rb every time there was an update for the puppet package, but I can't remember when was the last time I did this. The version of puppet that I have is the following:
$ yum info puppet
Loaded plugins: langpacks, refresh-packagekit
newrelic 14/14
Installed Packages
Name: puppet
Arch: noarch
Version : 3.4.3
Release : 3.fc20
Size: 3.6 M
Repo: installed
>From repo : fedora-updates
Summary : A network tool for managing many disparate systems
URL : http://puppetlabs.com
License : ASL 2.0
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.
If I unmount the target and remove the args self.device from the mentioned file, I get this on the next puppet execution:
$ sudo puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for anhanguera
Info: Applying configuration version '1404040690'
Notice: /Stage[main]/Backup-mountpoint/Mount[/mnt/backups]/ensure: ensure changed 'unmounted' to 'mounted'
Error: /Stage[main]/Backup-mountpoint/Mount[/mnt/backups]: Could not evaluate: Execution of '/bin/mount /mnt/backups' returned 32: mount.nfs: an incorrect mount option was specified
Notice: /Stage[main]/Backup-pgsql-mariadb/Cron[backup-databases]: Dependency Mount[/mnt/backups] has failures: true
Warning: /Stage[main]/Backup-pgsql-mariadb/Cron[backup-databases]: Skipping because of failed dependencies
Notice: Finished catalog run in 14.54 seconds
After the run, the mountpoint is still not mounted.
I'm not sure if the server's part is relevant, as it seems it's a problem in how the mount command is composed, but here's how I specified it:
class nfs-utils {
package {'nfs-utils':
ensure = installed,
}
}
class nfs-server {
include nfs-utils
service {'nfs-server':
ensure = running,
require = Package['nfs-utils'],
}
}
class nfs-server-acai {
include nfs-server
file
Jira (PUP-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters
Title: Message Title Andreas Papst commented on an issue Re: unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters Hi Henrik, adding the option you mentioned (puppet agent -t --parser future) doesn't change anything. But this seems not to be a big surprise, due to template command is extrapolated at the puppet master but not at the agent side. Recall: Default for parameter $foobar = 0 node.yaml: — classes: test = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: 0 = /tmp/test: foobar foobar == 0 node.yaml: — classes: test test::foobar: '0' = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: true = /tmp/test: foobar foobar == true node.yaml: — classes: test test::foobar: false = /tmp/test: empty node.yaml: — classes: test test::foobar: 1 = /tmp/test: foobar Hope this is something useful to you Andreas puppet -V 3.6.2 cat /etc/debian_version 7.3 dpkg -l | grep puppet ii facter 2.0.2-1puppetlabs1 amd64 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.4-1puppetlabs1 all A simple pluggable Hierarchical Database. ii puppet 3.6.2-1puppetlabs1 all Centralized configuration management - agent startup and compatibility scripts ii
Jira (PUP-2853) Class default parameter true not overriden by Hiera
Title: Message Title Pedro Gonzlez updated an issue Puppet / PUP-2853 Class default parameter true not overriden by Hiera Change By: Pedro Gonzlez Affects Version/s: 3.6.2 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/d/optout.
Jira (PUP-2853) Class default parameter true not overriden by Hiera
Title: Message Title Pedro Gonzlez commented on an issue Re: Class default parameter true not overriden by Hiera Sorry for the inconvenience, I recovered my test class and see it works just fine. Meantime the value was overriden in another point in the manifest Sorry for the inconvenience Add Comment Puppet / PUP-2853 Class default parameter true not overriden by Hiera I'm experiencing the exact behaviour described on https://projects.puppetlabs.com/issues/17474#note-3 which is supposed to be fixed 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/d/optout.
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Bernd Zeimetz commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
The first major problem is that the ipaddress6 fact uses ifconfig -a, which is deprectaed since a longish time and - which is much more important - is not able to show all IP addresses which are assigned to an interface. A good start would be something like this:
ip -o -6 a sh | grep -Ev 'inet6 (fe80:|::1)' 2: eth0 inet6 :1aa4:5004:106::e891/64 scope global deprecated \ valid_lft forever preferred_lft forever 2: eth0 inet6 :1aa8:5004:106::6aaf/64 scope global \ valid_lft forever preferred_lft forever
Non deprecated addresses should probably be listed first. See http://www.davidc.net/networking/ipv6-source-address-selection-linux for details. WIthout looking at the code I'm kinde sure that the ipaddress fact has similar issues, at least regarding the usage of the deprecated ifconfig tool.
Add Comment
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall...
Jira (FACT-345) IPv6 - interface missing
Title: Message Title Andre Nathan commented on an issue Re: IPv6 - interface missing net-tools version is 1.60-24.1ubuntu2. I'm adding the ifconfig output below (real IP addresses masked): eth0 Link encap:Ethernet HWaddr 00:15:17:d7:dc:80 inet addr:1.2.3.4 Bcast:1.2.3.255 Mask:255.255.252.0 inet6 addr: fe80::215:17ff:fed7:dc80/64 Scope:Link inet6 addr: :::2::4a5c/48 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:355839042 errors:0 dropped:6493903 overruns:0 frame:0 TX packets:3951964 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23029783986 (23.0 GB) TX bytes:1401885103 (1.4 GB) Memory:b1a2-b1a4 eth1 Link encap:Ethernet HWaddr 00:0e:0c:d9:97:31 inet addr:10.0.0.149 Bcast:10.0.255.255 Mask:255.255.0.0 inet6 addr: fe80::20e:cff:fed9:9731/64 Scope:Link inet6 addr: :::2::4a5c/48 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20723514962 errors:51 dropped:6529767 overruns:0 frame:26 TX packets:43089146196 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3416120820219 (3.4 TB) TX bytes:53895564482768 (53.8 TB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:549496 errors:0 dropped:0 overruns:0 frame:0 TX packets:549496 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:50142364 (50.1 MB) TX bytes:50142364 (50.1 MB) facter | grep ipaddress6 ipaddress6 = :::2::4a5c ipaddress6_eth0 = :::2::4a5c Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6
Jira (FACT-345) IPv6 - interface missing
Title: Message Title Bernd Zeimetz commented on an issue Re: IPv6 - interface missing As mentioned on the other bug report: On Linux the first major problem is that the ipaddress6 fact uses ifconfig -a, which is deprectaed since a longish time and - which is much more important - is not able to show all IP addresses which are assigned to an interface. A good start would be something like this: ip -o -6 a sh | grep -Ev 'inet6 (fe80:|::1)' 2: eth0 inet6 :1aa4:5004:106::e891/64 scope global deprecated \ valid_lft forever preferred_lft forever 2: eth0 inet6 :1aa8:5004:106::6aaf/64 scope global \ valid_lft forever preferred_lft forever Non deprecated addresses should probably be listed first. See http://www.davidc.net/networking/ipv6-source-address-selection-linux for details. WIthout looking at the code I'm kinde sure that the ipaddress fact has similar issues, at least regarding the usage of the deprecated ifconfig tool. I'm mentioning this here as FACT-345 was closed, marking it as duplicate of this bug. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ...
Jira (FACT-345) IPv6 - interface missing
Title: Message Title Bernd Zeimetz commented on an issue Re: IPv6 - interface missing http://linux.die.net/man/8/ifconfig says: This program is obsolete! For replacement check ip addr and ip link. For statistics use ip -s link. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ... 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 (PDB-722) PuppetDB response hanging on select-nodes subquery
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-722 PuppetDB response hanging on select-nodes subquery Change By: Ryan Senior Story Points: 2 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/d/optout.
Jira (PUP-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters
Title: Message Title Henrik Lindberg commented on an issue Re: unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters That is inconclusive, you need to run with either puppet apply --parser future, or have the setting parser = future in your settings for the master. Setting --parser future on the agent does not have any effect since it is not doing parsing/evaluation. In Puppet 3x manifests, unquoted and quoted numbers (e.g. 123 and '123') are equivalent. In 3x there is no way to enter a literal numeric value in a .pp manifest. You can force it to produce a numeric value by evaluating an _expression_; e.g. $foobar = 1-1 to produce a numeric 0 (yeah, I know it is ridiculous). Alternatively, enter a string in your hiera yaml instead of a number by quoting it (i.e. '0' instead of 0). Add Comment Puppet / PUP-2735 unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters I'm not sure, if this should be considered as an error. At least it should be stressed in the documentation: 0 (a digit) used as default value of a class parameter is converted into a string or character when the variable is interpreted in a template by Ruby. On the other hand, 0 entered as a value in an hiera-yaml file is interpreted as an integer va... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2853) Class default parameter true not overriden by Hiera
Title: Message Title Henrik Lindberg commented on an issue Re: Class default parameter true not overriden by Hiera Thanks for checking and closing. Add Comment Puppet / PUP-2853 Class default parameter true not overriden by Hiera I'm experiencing the exact behaviour described on https://projects.puppetlabs.com/issues/17474#note-3 which is supposed to be fixed 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/d/optout.
Jira (PDB-725) host rename problems
Title: Message Title Christopher May created an issue PuppetDB / PDB-725 host rename problems Issue Type: Bug Assignee: Unassigned Created: 30/Jun/14 6:32 AM Priority: Normal Reporter: Christopher May During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-queue-s01.visualdna.com Exported resources constantly finds two hosts and I've tried everything from node clean, node deactivate, purging /var/lib/puppet on the host as well. Everytime I run puppet on bl-queue-s01, it brings back the stagdmz entries as well (on another box it spits out two files, one being the stagdmz one as well). I'm about to go do some sql-fu to nuke all references to stagdmz but thought I'd raise this first in case im doing something wrong or if there is a better way of doing this. Cheers, Chris Add Comment
Jira (PDB-725) host rename problems
Title: Message Title Kenneth Barber commented on an issue Re: host rename problems So ... 'puppet node deactivate' should be the correct trick here. If you feel it is 'coming back' this could be for a number of reasons: The data genuinely is getting re-inserted. The puppetdb.log entry for a 'replace catalog' on the hostname will show this. Check your logs to ensure the data is not getting put back. The data is coming from a place you didn't expect. I usually recommend looking at this tool first: https://forge.puppetlabs.com/zack/exports. It is able to show you what resources are exported, and what host is exporting them. Most of the time these problems stem from assumptions around where the data is coming from - often the data is coming from a hostname you didn't expect and the node deactivate hostname is a mismatch. If you can try the tool, and show the attempts at trying to clear the data with deactivate, and back it up with puppetdb.log info, that would be very useful. Your bug reports talk about the symptoms, but I need more examples and I need you to show me transcripts on the CLI of how you've come to your conclusions if you can. Thanks. Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Henrik Lindberg Assignee: AndyParker HenrikLindberg 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/d/optout.
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Henrik Lindberg Sprint: Week2014-6-25to2014-7-9 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/d/optout.
Jira (PUP-2864) yum provider can't handle installonly packages
Title: Message Title Christian Becker created an issue Puppet / PUP-2864 yum provider can't handle installonly packages Issue Type: Bug Affects Versions: 3.2.2 Assignee: Unassigned Created: 30/Jun/14 6:54 AM Priority: Normal Reporter: Christian Becker We just started managing CentOS Kernel Packages and pin them to a specific version. This causes failed agent runs, because it seems as the yum provider can't handle multiple installed packages with the same name. Error: Could not update: Failed to update to version 3.14.4-1.el6.elrepo, got version 3.11.5-1.el6.elrepo instead Error: /Stage[main]/Packages::Kernel/Package[kernel]/ensure: change from 3.11.5-1.el6.elrepo to 3.14.4-1.el6.elrepo failed: Could not update: Failed to update to version 3.14.4-1.el6.elrepo, got version 3.11.5-1.el6.elrepo instead But the package is already installed: rpm -qa | grep -i kernel-ml kernel-ml-3.11.5-1.el6.elrepo.x86_64 kernel-ml-3.14.4-1.el6.elrepo.x86_64 And also yum knows this yum info kernel-ml Loaded plugins: downloadonly, fastestmirror, security Loading mirror speeds from cached hostfile Installed Packages Name : kernel-ml Arch : x86_64 Version : 3.11.5 Release : 1.el6.elrepo Size : 154 M Repo : installed From repo : elrepo_org Summary : The Linux kernel. (The core
Jira (PDB-725) host rename problems
Title: Message Title Christopher May commented on an issue Re: host rename problems that zack-exports module seems to have solved my issue, it seems; bl-queue-p04.visualdna.com Nagios_service[check_total_procs_bl-stream-p01.proddmz.bl.visualdna.com] So I was deactivating the new nodes hostname but because queue-p04 wasn't deactivated, it was keeping the data alive even though the hostname and the export resource caused a weird conflict. I'm sure this is working as intended, just the way puppet behaves whilst the box is being renamed underneath it. Sorry for wasting your time, and thanks for highlighting an extremely useful tool! Cheers, Chris Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Henrik Lindberg commented on an issue Re: Specify signatures for blocks of block-accepting methods Hm, turns it is one of those cases where you can't have and eat the cake at the same time... If Callable means, this callable thing must be callable with these arguments (it may be callable in more generic ways, but at least it is callable the way I want it), then there is no way to type check a callable the other way (I do not want to accept a callable that accepts a more generic signature). There are two ways of solving this: Simply change Callable's assignability to be in the reverse; What is expressed is the constraints on the intent to call it Add yet another type, say Lambda that expresses what the signature is (it looks exactly like a Callable, in fact, a Callable can refer to a Lambda) but the type calculations are the same. Keep Callable's assignability (it is now what a Lambda type would do), and instead check parameter assignability differently when the type is a Callable. The first solution is fine as I can't think of reasonable scenarios where it is of value to express that a more generic signature is disallowed. Add Comment Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the
Jira (PDB-725) host rename problems
Title: Message Title Kenneth Barber commented on an issue Re: host rename problems Well, we've had discussions recently about making that tool part of core - and documented it a bit more. For now though, this seems like an information problem more than a bug. Closing . Add Comment PuppetDB / PDB-725 host rename problems During a server rename, puppet briefly ran on the box with the dns address rather then the usual hostname address. Another run fixed this but now I have duplicate hosts in puppetdb that I cannot seem to get rid off. So consider the following; Original name - bl-queue-s01.visualdna.com Temp name - bl-queue-s01.stagdmz.visualdna.com Final name - bl-... 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/d/optout.
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title
Henrik Lindberg commented on an issue
Re: Specify signatures for blocks of block-accepting methods
Now, back to the case of improving the type checking of the iterative functions. Naturally, it will not work to declare that the iterative function will make a call with 1 or 2 parameters, since a given block that only accepts one parameter will then not be acceptable (since it must optionally expect two). We could describe it using a Variant[Callable[Any], Callable[Any, Any]], but this means that the given block can not be typed more specifically than Any. In order to correctly specify this, we must either add type parameters (so we can specify how it will actually be called, (or we can create the signature dynamically by making the dispatcher accept a block), or we need to use just Callable (which accepts any callable - but then we are back on square one and not checking the given block's signature at all).
Maybe we can handle it as Variant[Callable[1], Callable[2] - i.e. without stating the types that will be given to the block, only that it must accept one or two. Now investigating if the Callable type handles this.
Add Comment
Puppet / PUP-2794
Specify signatures for blocks of block-accepting methods
Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should...
Jira (PUP-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Adrien Thebo commented on an issue Re: Make puppet able to configure a facter implementation to use Merged fixups in cac43b3. Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use 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/d/optout.
Jira (PUP-501) Test Evaluation of ResourceExpressions
Title: Message Title Andy Parker updated an issue Puppet / PUP-501 Test Evaluation of ResourceExpressions Change By: Andy Parker Sprint: Week2014-7-9to2014-7-23 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/d/optout.
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Andy Parker Sprint: Week2014-7-9to2014-7-23 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/d/optout.
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API Change By: Andy Parker Assignee: AndyParker 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/d/optout.
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Andy Parker Assignee: HenrikLindberg 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/d/optout.
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 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/d/optout.
Jira (PDB-715) Create PuppetDB 2.1.0 blog post
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-715 Create PuppetDB 2.1.0 blog post Change By: Kenneth Barber Assignee: KennethBarber 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/d/optout.
Jira (PUP-501) Test Evaluation of ResourceExpressions
Title: Message Title Andy Parker updated an issue Puppet / PUP-501 Test Evaluation of ResourceExpressions Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 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/d/optout.
Jira (PUP-1112) Puppet Packages should be built to support Ruby 1.9 from Software Collections.
Title: Message Title Brian Rak commented on an issue Re: Puppet Packages should be built to support Ruby 1.9 from Software Collections. Another reason for this is Ruby 1.9.3 is supposed to fix the massive amount of rt_sigprocmask spam, which should improve performance. http://timetobleed.com/fix-a-bug-in-rubys-configurein-and-get-a-30-performance-boost/ This is from a puppet master: strace -cttp 12617 Process 12617 attached - interrupt to quit ^CProcess 12617 detached % time seconds usecs/call calls errors syscall --- --- - - 68.04 0.001007 1 855 select 30.07 0.000445 0 49325 rt_sigprocmask (truncated) Add Comment Puppet / PUP-1112
Jira (PUP-2682) Trailing commas should be allowed in node definitions
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2682 Trailing commas should be allowed in node definitions Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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/d/optout.
Jira (PUP-1027) Add warning for use of bare words that clash with new keywords
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-1027 Add warning for use of bare words that clash with new keywords Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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/d/optout.
Jira (PUP-2800) Selector string match behavior change (future parser)
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2800 Selector string match behavior change (future parser) Change By: Nicholas Fagerlund Labels: docs_reviewed future-parser 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/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Assignee: AdrienThebo 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/d/optout.
Jira (PUP-2798) Stop issuing deprecation warnings for reserved words
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2798 Stop issuing deprecation warnings for reserved words Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily Matteo Cerutti one thing I noticed is that on SLE* 10, both rug and zypper will both be default, in your opinion does this matter? Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... 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/d/optout.
Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2737 user purge_ssh_keys cannot remove keys with spaces in the comment Change By: Adrien Thebo Fix Version/s: 3.6.3 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/d/optout.
Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title
Adrien Thebo commented on an issue
Re: user purge_ssh_keys cannot remove keys with spaces in the comment
We don't plan on releasing a 3.6.3, so I'm retargeting this at 3.7.0.
Add Comment
Puppet / PUP-2737
user purge_ssh_keys cannot remove keys with spaces in the comment
Given the following: {noformat} # /root/.ssh/authorized_keys # HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXev...
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/d/optout.
Jira (PDB-182) Document backup and restoration advice
Title: Message Title
Mike Hall commented on an issue
Re: Document backup and restoration advice
Nick Walker, yup: The documentation was added in April (well after this ticket was created, to address another issue):
https://github.com/puppetlabs/puppet-docs/commit/859e113b97da53e323d23059043e4876758bc1cc
Add Comment
PuppetDB / PDB-182
Document backup and restoration advice
We always get asked about how to backup PuppetDB, we probably should write a formal doc. From notes after discussion with @glarizza, the following could be used for Postgres: {noformat} pg_dump -Z 9 -Fc puppetdb /tmp/backup.dump pg_restore -c --jobs=2 -Fc -d puppetdb /tmp/backup.dump {noformat} (be mindful this will not backup/restore the `p...
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-480) Complete handling of undef/nil
Title: Message Title Andy Parker commented on an issue Re: Complete handling of undef/nil Functionally this seems to be working, but there are still a lot of cases where :undef is used that need to either be explained or removed. Add Comment Puppet / PUP-480 Complete handling of undef/nil A decision needs to be made regarding handling of undef as nil. There is agreement that it should be handled as a nil value everywhere except one case; when setting an attribute value. Currently setting undef as an attribute value has the meaning do not set this attribute (as opposed to set this attribute to nil) - which has the effect of selectin... 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/d/optout.
Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title
Adrien Thebo commented on an issue
Re: user purge_ssh_keys cannot remove keys with spaces in the comment
Merged in 4682445.
Add Comment
Puppet / PUP-2737
user purge_ssh_keys cannot remove keys with spaces in the comment
Given the following: {noformat} # /root/.ssh/authorized_keys # HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXev...
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/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title
Andy Parker commented on an issue
Re: Complete handling of undef/nil
While experimenting with this I put together some functions and puppet code to check how undef was being passed around.
Puppet::Parser::Functions.newfunction(:ident, :type = :rvalue) do |args|
args[0]
end
Puppet::Functions.create_function(:ident4) do
def ident4(value)
value
end
end
undef.pp
notice('$x == undef')
notice($x == undef)
notice('undef == undef')
notice(undef == undef)
notice(' != undef')
notice( != undef)
define a($value = 'default', $desc) {
notice($desc)
notice($value == 'default')
}
a { a: desc = a { a: } }
a { b: value = undef, desc = a { b: value = undef } }
a { c: value = $x, desc = 'a { c: value = $x }' }
notice(erb w/unbound lookupvar)
notice(inline_template(%= scope.lookupvar('x').nil? %))
$missing = undef
notice(erb w/bound but undef lookupvar)
notice(inline_template(%= scope.lookupvar('missing').nil? %))
notice('match vars without a match ($0 == undef)')
notice($0 == undef)
notice('undef literal passed to function translated to empty string (3x function)')
notice(ident(undef) == '')
notice('unbound variable passed to function translated to empty string (3x function)')
notice(ident($x) == '')
notice('variable bound to undef passed to function translated to empty string (3x function)')
notice(ident($missing) == '')
if $settings::parser == future {
notice(epp w/unbound var)
notice(inline_epp('%= $x == undef %'))
notice(epp w/bound but undef var)
notice(inline_epp('%= $missing == undef %'))
notice(epp with undef passed as param uses default)
notice(inline_epp('%-|$value = default|-%%= $value == default %'), { value = undef })
notice('undef literal passed to function (4x function)')
notice(ident4(undef) == undef)
notice('unbound variable passed to function (4x function)')
notice(ident4($x) == undef)
notice('variable bound to undef passed to function (4x function)')
notice(ident4($missing) == undef)
}
The undef.pp file can be used to show the differences in undef between parser current and parser future.
Add Comment
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker HenrikLindberg 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/d/optout.
Jira (PUP-2865) Puppet wipes /etc/hosts if any entry cannot be parsed
Title: Message Title
R K created an issue
Puppet / PUP-2865
Puppet wipes /etc/hosts if any entry cannot be parsed
Issue Type:
Bug
Affects Versions:
3.6.1, 2.7.25
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
30/Jun/14 11:23 AM
Priority:
Critical
Reporter:
R K
If any entry in /etc/hosts is unparsable and a host entity is created, Puppet will add the host entry to a blank /etc/hosts file thus deleting the actual contents of the /etc/hosts file.
Simple demonstration: root@host# wc -l /etc/hosts 37 /etc/hosts root@host# echo ' 1.0.0.1 test-93bc213cf5e6bc992791e6002e296b594b9650b2' /etc/hosts root@host# puppet apply --verbose --execute 'host {'test1-93bc213cf5e6bc992791e6002e296b594b9650b2': ensure= present, ip = 1.0.0.2 }
' ... err: Could not prefetch host provider 'parsed': Could not parse line 1.0.0.1 test-93bc213cf5e6bc992791e6002e296b594b9650b2 at /etc/hosts:38 ... root@host# wc -l /etc/hosts 4 /etc/hosts root@host#
Jira (PDB-182) Document backup and restoration advice
Title: Message Title
Kenneth Barber commented on an issue
Re: Document backup and restoration advice
I think since this ticket really covered PE customers, this can probably be closed then.
The restore advice probably isn't the most optimal in that doc, but it will do for most cases.
Add Comment
PuppetDB / PDB-182
Document backup and restoration advice
We always get asked about how to backup PuppetDB, we probably should write a formal doc. From notes after discussion with @glarizza, the following could be used for Postgres: {noformat} pg_dump -Z 9 -Fc puppetdb /tmp/backup.dump pg_restore -c --jobs=2 -Fc -d puppetdb /tmp/backup.dump {noformat} (be mindful this will not backup/restore the `p...
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
Jira (PUP-500) Test CollectExpressions
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-500 Test CollectExpressions Change By: Andy Parker Assignee: AndyParker 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/d/optout.
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title
Andy Parker commented on an issue
Re: Move epp() and inline_epp() to 4x function API
Merged into master in aa60e3
Add Comment
Puppet / PUP-2845
Move epp() and inline_epp() to 4x function API
The {{epp()}} and {{inline_epp()}} functions must be moved to the 4x function API in order to work correctly. The 3x function API requires transformation of all undef/nils to empty string, and that catalog entry types are transformed to Resource references. This does not work well when these values again emerge in Puppet logic. This also blocks the wan...
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/d/optout.
Jira (PUP-1760) Update win32-security gem to latest (after string_to_sid fix)
Title: Message Title
Rob Reynolds commented on an issue
Re: Update win32-security gem to latest (after string_to_sid fix)
Validated both
https://github.com/djberg96/win32-security/issues/4
https://github.com/djberg96/win32-security/issues/3 work appropriately.
Add Comment
Puppet / PUP-1760
Update win32-security gem to latest (after string_to_sid fix)
Hoping for 3.5.0 but not a blocker. We have a small blocker to upgrading to the latest win32-security gem. It seems to truncate the binary representation of the SID when calling Win32::Security::SID.string_to_sid('some sid'). We rely on this method in several places so we need to get this fixed prior to upgrading our gem. For more information, pleas...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You
Jira (PUP-1760) Update win32-security gem to latest (after string_to_sid fix)
Title: Message Title
Rob Reynolds commented on an issue
Re: Update win32-security gem to latest (after string_to_sid fix)
There really isn't functional review here and this has already been through CI, so moving to resolved.
Add Comment
Puppet / PUP-1760
Update win32-security gem to latest (after string_to_sid fix)
Hoping for 3.5.0 but not a blocker. We have a small blocker to upgrading to the latest win32-security gem. It seems to truncate the binary representation of the SID when calling Win32::Security::SID.string_to_sid('some sid'). We rely on this method in several places so we need to get this fixed prior to upgrading our gem. For more information, pleas...
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/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Rob Reynolds Assignee: RobReynolds 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/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Rebasing against PUP-2777. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... 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/d/optout.
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2626 Accept module paths in Puppet::Parser::Functions.file() Change By: Adrien Thebo Component/s: DSL Component/s: Community 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/d/optout.
Jira (PUP-2513) puppet module install fails when url includes basic auth
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Adrien Thebo Labels: github pupet puppetpuppet -module puppet 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/d/optout.
Jira (PUP-2513) puppet module install fails when url includes basic auth
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Rob Reynolds commented on an issue Re: Support Bundler workflow on x64 With 005c28d x64 calling gem spec puppet-x64.gem: - !ruby/object:Gem::Dependency name: ffi requirement: !ruby/object:Gem::Requirement requirements: - - '=' - !ruby/object:Gem::Version version: 1.9.3 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - '=' - !ruby/object:Gem::Version version: 1.9.3 - !ruby/object:Gem::Dependency name: win32-dir requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.4.8 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.4.8 - !ruby/object:Gem::Dependency name: win32-eventlog requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.6.1 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.6.1 - !ruby/object:Gem::Dependency name: win32-process requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.7.4 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.7.4 - !ruby/object:Gem::Dependency name: win32-security requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.2.5 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.2.5 - !ruby/object:Gem::Dependency name: win32-service requirement: !ruby/object:Gem::Requirement requirements: - - '=' - !ruby/object:Gem::Version version: 0.8.4 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - '=' - !ruby/object:Gem::Version version: 0.8.4 - !ruby/object:Gem::Dependency name: win32-taskscheduler requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.3.0 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.3.0 - !ruby/object:Gem::Dependency name: minitar requirement: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.5.4 type: :runtime prerelease: false version_requirements: !ruby/object:Gem::Requirement requirements: - - ~ - !ruby/object:Gem::Version version: 0.5.4 Add Comment
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Nick Walker commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
I agree that puppet config print should not work without specifying a section because it does not output enough information to let us know what section or runmode it ran it and confuses users.
Add Comment
Puppet / PUP-2038
`puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
{{puppet config print}} is rarely accurate, and mostly just confusing to users. It should be deprecated in favor of {{puppet agent --configprint someoption}}, which currently works fairly well. Puppet 3.something should issue deprecation warnings, and Puppet 4 should remove it entirely.
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
Jira (PUP-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Peter Huene created an issue Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. Issue Type: Bug Affects Versions: 3.6.0 Assignee: Peter Huene Components: Types and Providers Created: 30/Jun/14 12:44 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Peter Huene Add Comment
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Support Bundler workflow on x64
With 005c28d calling gem spec pkg/puppet-*x86*.gem --ruby
s.add_runtime_dependency(%qffi, [= 1.9.0])
s.add_runtime_dependency(%qwin32-api, [= 1.4.8])
s.add_runtime_dependency(%qwin32-dir, [~ 0.4.3])
s.add_runtime_dependency(%qwin32-eventlog, [~ 0.5.3])
s.add_runtime_dependency(%qwin32-process, [~ 0.6.5])
s.add_runtime_dependency(%qwin32-security, [~ 0.2.5])
s.add_runtime_dependency(%qwin32-service, [= 0.7.2])
s.add_runtime_dependency(%qwin32-taskscheduler, [~ 0.2.2])
s.add_runtime_dependency(%qwin32console, [= 1.3.2])
s.add_runtime_dependency(%qwindows-api, [~ 0.4.2])
s.add_runtime_dependency(%qwindows-pr, [~ 1.2.2])
s.add_runtime_dependency(%qminitar, [~ 0.5.4])
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Ethan Brown commented on an issue Re: Support Bundler workflow on x64 Gem installed under Ruby 2.0 x64 C:\source\gem-testgem install puppet-3.6.2.511-x64-mingw32.gem --install-dir c:\source\gem-test\gems Successfully installed json_pure-1.8.1 Fetching: rgen-0.6.6.gem (100%) Successfully installed rgen-0.6.6 Fetching: hiera-1.3.4.gem (100%) Successfully installed hiera-1.3.4 Fetching: ffi-1.9.3-x64-mingw32.gem (100%) Successfully installed ffi-1.9.3-x64-mingw32 Fetching: win32-dir-0.4.8.gem (100%) Successfully installed win32-dir-0.4.8 Fetching: win32-security-0.2.5.gem (100%) Successfully installed win32-security-0.2.5 Fetching: facter-2.1.0-x64-mingw32.gem (100%) Successfully installed facter-2.1.0-x64-mingw32 Fetching: minitar-0.5.4.gem (100%) Successfully installed minitar-0.5.4 Fetching: win32-eventlog-0.6.1.gem (100%) Successfully installed win32-eventlog-0.6.1 Fetching: structured_warnings-0.1.4.gem (100%) Successfully installed structured_warnings-0.1.4 Fetching: win32-taskscheduler-0.3.0.gem (100%) Successfully installed win32-taskscheduler-0.3.0 Fetching: win32-service-0.8.4.gem (100%) Successfully installed win32-service-0.8.4 Fetching: win32-process-0.7.4.gem (100%) Successfully installed win32-process-0.7.4 Successfully installed puppet-3.6.2.511-x64-mingw32 Parsing documentation for json_pure-1.8.1 Installing ri documentation for json_pure-1.8.1 Parsing documentation for rgen-0.6.6 Installing ri documentation for rgen-0.6.6 Parsing documentation for hiera-1.3.4 Installing ri documentation for hiera-1.3.4 Parsing documentation for ffi-1.9.3-x64-mingw32 Installing ri documentation for ffi-1.9.3-x64-mingw32 Parsing documentation for win32-dir-0.4.8 Installing ri documentation for win32-dir-0.4.8 Parsing documentation for win32-security-0.2.5 Installing ri documentation for win32-security-0.2.5 Parsing documentation for facter-2.1.0-x64-mingw32 Installing ri documentation for facter-2.1.0-x64-mingw32 Parsing documentation for minitar-0.5.4 Installing ri documentation for minitar-0.5.4 Parsing documentation for win32-eventlog-0.6.1 Installing ri documentation for win32-eventlog-0.6.1 Parsing documentation for structured_warnings-0.1.4 Installing ri documentation for structured_warnings-0.1.4 Parsing documentation for win32-taskscheduler-0.3.0 Installing ri documentation for win32-taskscheduler-0.3.0 Parsing documentation for win32-service-0.8.4 Installing ri documentation for win32-service-0.8.4 Parsing documentation for win32-process-0.7.4 Installing ri documentation for win32-process-0.7.4 Parsing documentation for puppet-3.6.2.511-x64-mingw32 Installing ri documentation for puppet-3.6.2.511-x64-mingw32 14 gems installed C:\source\gem-testruby --version ruby 2.0.0p481 (2014-05-08) [x64-mingw32] Add Comment
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Support Bundler workflow on x64
Merged into master at 84e5814
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Ethan Brown commented on an issue Re: Support Bundler workflow on x64 Gem installed under Ruby 1.9.3 / x86 C:\source\gem-test gem install .\puppet-3.6.2.511-x86-mingw32.gem --install-dir C:\source\gem-test\x86-gems Fetching: json_pure-1.8.1.gem (100%) Fetching: rgen-0.6.6.gem (100%) Fetching: hiera-1.3.4.gem (100%) Fetching: ffi-1.9.3-x86-mingw32.gem (100%) Fetching: win32-dir-0.4.8.gem (100%) Fetching: win32-security-0.2.5.gem (100%) Fetching: facter-2.1.0-x86-mingw32.gem (100%) Fetching: minitar-0.5.4.gem (100%) Fetching: win32-api-1.4.8-x86-mingw32.gem (100%) Fetching: windows-api-0.4.2.gem (100%) Fetching: windows-pr-1.2.3.gem (100%) Fetching: win32-eventlog-0.5.3.gem (100%) Fetching: win32-taskscheduler-0.2.2.gem (100%) Fetching: win32-service-0.7.2-x86-mingw32.gem (100%) Fetching: win32-process-0.6.6.gem (100%) Successfully installed json_pure-1.8.1 Successfully installed rgen-0.6.6 Successfully installed hiera-1.3.4 Successfully installed ffi-1.9.3-x86-mingw32 Successfully installed win32-dir-0.4.8 Successfully installed win32-security-0.2.5 Successfully installed facter-2.1.0-x86-mingw32 Successfully installed minitar-0.5.4 Successfully installed win32-api-1.4.8-x86-mingw32 Successfully installed windows-api-0.4.2 Successfully installed windows-pr-1.2.3 Successfully installed win32-eventlog-0.5.3 Successfully installed win32-taskscheduler-0.2.2 Successfully installed win32-service-0.7.2-x86-mingw32 Successfully installed win32-process-0.6.6 Successfully installed puppet-3.6.2.511-x86-mingw32 16 gems installed Installing ri documentation for json_pure-1.8.1... Installing ri documentation for rgen-0.6.6... Installing ri documentation for hiera-1.3.4... Installing ri documentation for ffi-1.9.3-x86-mingw32... Enclosing class/module 'moduleFFI' for class AbstractMemory not known Enclosing class/module 'moduleFFI' for class NullPointerError not known Enclosing class/module classMemory for alias put_ #name, put_ #old); \ rb_define_alias(classMemory, get_ #name, get_ #old); \ rb_define_alias(classMemory, put_u #name, put_u #old); \ rb_define_alias(classMemory, get_u #name, get_u #old); \ rb_define_alias(classMemory, write_ #name, write_ #old); \ rb_define_alias(classMemory, read_ #name, read_ #old); \ rb_define_alias(classMemory, write_u #name, write_u #old); \ rb_define_alias(classMemory, read_u #name, read_u #old); \ rb_define_alias(classMemory, put_array_of_ #name, put_array_of_ #old); \ rb_define_alias(classMemory, get_array_of_ #name, get_array_of_ #old); \ rb_define_alias(classMemory, put_array_of_u #name, put_array_of_u #old); \ rb_define_alias(classMemory, get_array_of_u #name, get_array_of_u #old); \ rb_define_alias(classMemory, write_array_of_ #name, write_array_of_ #old); \ rb_define_alias(classMemory, read_array_of_ #name, read_array_of_ #old); \ rb_define_alias(classMemory, write_array_of_u #name, write_array_of_u #old); \ rb_define_alias(classMemory, read_array_of_u #name, read_array_of_u #old); ALIAS(char, int8); ALIAS(short, int16); ALIAS(int, int32); ALIAS(long_long, int64); /* * Document-method: put_float32 * call-seq: memory.put_float32offset, value) * @param [Numeric] offset * @param [Numeric] value * @return [self] * Put +value+ as a 32-bit float in memory at offset +offset+ (alias: #put_float). */ rb_define_method(classMemory, put_float32, memory_put_float32, 2); /* * Document-method: get_float32 * call-seq: memory.get_float32(offset) * @param [Numeric] offset * @return [Float] * Get a 32-bit float from memory at offset +offset+ (alias: #get_float). */ rb_define_method(classMemory, get_float32, memory_get_float32, 1);
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Adrien Thebo Assignee: PietervandeBruggen 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/d/optout.
Jira (PUP-2867) Support user home directories (Unix) in file resources
Title: Message Title Raphal Pinson created an issue Puppet / PUP-2867 Support user home directories (Unix) in file resources Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 30/Jun/14 1:15 PM Priority: Normal Reporter: Raphal Pinson It is currently not possible to use paths in the form of `~user` in file resources, but it would be very useful, so home directories are resolved on the agent. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Support Bundler workflow on x64
Surprised you didn't also bump win32-dir to 0.4.8 as facter requires that as well.
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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/d/optout.
Jira (PUP-2867) Support user home directories (Unix) in file resources
Title: Message Title Raphal Pinson commented on an issue Re: Support user home directories (Unix) in file resources PR https://github.com/puppetlabs/puppet/pull/2820 adds this functionality. Add Comment Puppet / PUP-2867 Support user home directories (Unix) in file resources It is currently not possible to use paths in the form of `~user` in file resources, but it would be very useful, so home directories are resolved on the agent. 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/d/optout.
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title
Andy Parker commented on an issue
Re: The manifests directory should be recursively loaded when using directory environments
After talking with William Van Hevelingen in IRC, I think we should try to get this into puppet 3.7, but gate it with the parser future so that users get the Puppet 4 behavior. The problem is that he can't upgrade and use directory environments until it has this functionality and by leaving it out of 3.7 it means that there isn't actually a good upgrade path for him.
I'm concerned about adding this functionality without the feature flag because of the possibility of code being loaded that would not have been before this change.
Add Comment
Puppet / PUP-2711
The manifests directory should be recursively loaded when using directory environments
We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Fix Version/s: 4.0.0 Fix Version/s: 3.7.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/d/optout.
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Component/s: DSL 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/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Ethan Brown commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
PRs added to remove sys-admin gem - still checking tests
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
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/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker created an issue Puppet / PUP-2868 `puppet config print` confusing for users Issue Type: Bug Affects Versions: 3.4.0 Assignee: Unassigned Created: 30/Jun/14 2:07 PM Priority: Normal Reporter: Andy Parker puppet config print doesn't require a --section to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. Add Comment
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker assigned an issue to Zachary Stern Zachary Stern, Nick Walker, could you two provide a bit of a run down about how users have been confused? What commands are they executing and what output do they expect to see? If you have suggestions to have it better match their expectations and have it clearer to them when it isn't, that would be really helpful as well. Puppet / PUP-2868 `puppet config print` confusing for users Change By: Andy Parker Assignee: ZacharyStern 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/d/optout.
Jira (PUP-2867) Support user home directories (Unix) in file resources
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2867 Support user home directories (Unix) in file resources Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker 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/d/optout.
Jira (HI-277) Remove sid and unstable from build_defaults
Title: Message Title Eric Timmerman assigned an issue to Eric Timmerman Hiera / HI-277 Remove sid and unstable from build_defaults Change By: Eric Timmerman Assignee: EricTimmerman 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/d/optout.
Jira (FACT-606) Remove sid/unstable from build_defaults
Title: Message Title Eric Timmerman assigned an issue to Eric Timmerman Facter / FACT-606 Remove sid/unstable from build_defaults Change By: Eric Timmerman Assignee: EricTimmerman 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/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title garrett honeycutt commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them +1 This behavior seems to have changed with Puppet 3.6 Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. 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/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Pieter van de Bruggen commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them garrett honeycutt Can you provide an example of how this behavior has changed? Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. 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/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title garrett honeycutt commented on an issue Re: module skeleton is using deprecated way to configure spec_helper Adrien Thebo asked in the PR for me to include .fixtures.yml, which I have done, though this hits bug PUP-2079. Add Comment Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper [~josh] states that we are using a deprecated method for configuring rspec 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/d/optout.
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title gepetto-bot commented on an issue Re: PR (125): Ensure db and db users created before validation - rickerc tdb commented: Another me too. ``` Notice: /Stage[main]/Puppetdb::Server::Validate_db/Postgresql::Validate_db_connection[validate puppetdb postgres connection]/Exec[validate postgres connection for localhost/puppetdb]/returns: Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb Error: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb ' false returned 1 instead of one of [0] Error: /Stage[main]/Puppetdb::Server::Validate_db/Postgresql::Validate_db_connection[validate puppetdb postgres connection]/Exec[validate postgres connection for localhost/puppetdb]/returns: change from notrun to 0 failed: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb ' false returned 1 instead of one of [0] Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Role[puppetdb]/Postgresql_psql[CREATE ROLE puppetdb ENCRYPTED PASSWORD 'xDyfygrgxnphey1jLutccjt2lwsmms' LOGIN NOCREATEROLE NOCREATEDB NOSUPERUSER CONNECTION LIMIT -1]/command: command changed '' to 'CREATE ROLE puppetdb ENCRYPTED PASSWORD 'XX' LOGIN NOCREATEROLE NOCREATEDB NOSUPERUSER CONNECTION LIMIT -1' Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Database_grant[GRANT puppetdb - all - puppetdb]/Postgresql::Server::Grant[database:GRANT puppetdb - all - puppetdb]/Postgresql_psql[GRANT ALL ON DATABASE puppetdb TO puppetdb]/command: command changed '' to 'GRANT ALL ON DATABASE puppetdb TO puppetdb' ``` You can clearly see the validation is done before the role is created and the permissions set up. So it's just an ordering issue. @kbarber maybe in your case the order just happens to work out better? The right fix would appear to be ensuring the database is fully set up before validation is done. Please reopen the issue. Add Comment PuppetDB / PDB-566
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title
garrett honeycutt commented on an issue
Re: puppet module generate can't copy template files without parsing/renaming them
Generating a module now produces an incorrectly named file that has not been interpolated.
.fixtures.yml.erb pre fixtures: repositories: stdlib: repo: 'git://github.com/puppetlabs/puppetlabs-stdlib.git' ref: '3.2.0' symlinks: %= metadata.name %: # {source_dir} /pre it used to create .fixtures.yml with the following, provided that the module's name is 'foo' pre .fixtures.yml.erb fixtures: repositories: stdlib: repo: 'git://github.com/puppetlabs/puppetlabs-stdlib.git' ref: '3.2.0' symlinks: foo: #{source_dir}
/pre
Add Comment
Puppet / PUP-2079
puppet module generate can't copy template files without parsing/renaming them
When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: puppet module generate ignores ERB files beginning with a dot
PUP-2079 seems to be an unrelated issue, focused on providing a facility for copying unexpanded templates from the skeleton into the generated module. The issue being reported here is that templated dotfiles are not being properly expanded.
Add Comment
Puppet / PUP-2806
puppet module generate ignores ERB files beginning with a dot
When using 'puppet module generate' with a custom skeleton directory, any files prefixed with a dot (for example, .fixtures.yml.erb) are ignored by the 'populate_erb_templates' method. Example: After running 'puppet module generate treydock-munge' using a custom skeleton directory. {code} $ ls -la treydock-munge/ total 112 drwxr-xr-x 18 tr...
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
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Pieter van de Bruggen commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them Ah; that's the issue reported in PUP-2806 . This issue is specifically focused on providing a facility for copying templates into the generated module without doing expansion (though the PR at https://github.com/puppetlabs/puppet/pull/2759 does incidentally fix PUP-2806 as well). Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2869) Puppet should be able to use authenticated proxies
Title: Message Title Brett Gray created an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Issue Type: Bug Affects Versions: 3.6.2, 3.6.1, 3.6.0, 3.5.1, 3.5.0, 3.4.3 Assignee: Unassigned Components: PMT Created: 30/Jun/14 3:24 PM Priority: Normal Reporter: Brett Gray Currently Puppet has the ability to use proxies when performing network communications. The current settings allow for a host and a port, but not for a username or a password. This limitation prevents tools such as PMT from being utilised from a Puppet master that is behind an authenticated proxy. Add Comment
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: puppet module generate ignores ERB files beginning with a dot
This will be resolved when the pull requests here (https://github.com/puppetlabs/puppet/pull/2759) is merged.
Add Comment
Puppet / PUP-2806
puppet module generate ignores ERB files beginning with a dot
When using 'puppet module generate' with a custom skeleton directory, any files prefixed with a dot (for example, .fixtures.yml.erb) are ignored by the 'populate_erb_templates' method. Example: After running 'puppet module generate treydock-munge' using a custom skeleton directory. {code} $ ls -la treydock-munge/ total 112 drwxr-xr-x 18 tr...
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/d/optout.
Jira (PUP-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (PUP-2811) Provide method for class masquerading
Title: Message Title
Jok Thuau commented on an issue
Re: Provide method for class masquerading
it seems to me that the consensus is that it'd be useful. I think in the end, it can be split in a couple of different phases:
a simpler approach where just the class name is used (aliasing sort of thing, at the class level?)
an advanced approach later on where the spec of the class need to match (and possibly a mechanism/infrastructure to agree on what that is, so that different implementation of modules can use the same namespace
full solver with tracking to point out exactly what is wrong with the implementations of modules.
the first one would be sufficient in my case the last one would be awesome. but let's walk first.
Add Comment
Puppet / PUP-2811
Provide method for class masquerading
this stems from a discussion on puppet-dev. this is an attempt at putting on the radar. ~/modules/sssd/manifests/init.pp class sssd as auth { # do something to install/setup/etc sssd } ~/modules/nslcd/manifests/init.pp class nslcd as auth { # do something to install/setup/etc nslcd } ~/modules/ssh_authz/manifests/init.pp class ssh_auth...
Jira (PUP-2869) Puppet should be able to use authenticated proxies
Title: Message Title Andy Parker updated an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Change By: Andy Parker Issue Type: Bug Improvement 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/d/optout.
Jira (FACT-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo updated an issue Facter / FACT-547 Limit the output of prtdiag on Solaris Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title Adrien Thebo updated an issue Facter / FACT-598 fqdn is concatenation of hostname -s and domainname instead of hostname -f Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (FACT-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Change By:
Adrien Thebo
Component/s:
Community
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/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Nick Walker commented on an issue
Re: `puppet config print` confusing for users
Andy Parker to my knowledge the largest problem is someone runs puppet config print setting_name and they expect it to be either the agent or the master setting but it's really the user run mode which is less used.
I think in order to resolve that confusion we could do one or both of the following:
1. Output which section or run mode the command ran in 2. Force the user to choose a run mode or section so there's no question about which it ran in
Add Comment
Puppet / PUP-2868
`puppet config print` confusing for users
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you
Jira (PUP-2870) sample auth.conf gives invalid syntax for deny
Title: Message Title
Patrick Carlisle created an issue
Puppet / PUP-2870
sample auth.conf gives invalid syntax for deny
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
30/Jun/14 4:27 PM
Priority:
Normal
Reporter:
Patrick Carlisle
The sample auth.conf give deny [host|backreference|*|regex] as the syntax for deny, but using deny * gives me the error Error: Invalid pattern * at line 4 of }} (and the filename is missing from the error message). As far as I understand it {{deny * is redundant anyway.
Add Comment
Jira (PUP-1294) The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys
Title: Message Title joe b commented on an issue Re: The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys 3.6.2-1.el6 still seeing attempted group changes with groups from NIS listed as current groups for a forcelocal = true user. Add Comment Puppet / PUP-1294 The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys I have a particular configuration where a custom NSS plugin intercepts getent passwd calls and replaces the login shell with a new shell. In this situation, using the standard 'user' resource causes a false-positive for Puppet where it thinks the shell is configured as this new value, but it should be set to the value specified in the manifest. Unfortunat... 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-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Peter Huene updated an issue Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. Change By: Peter Huene Sprint: Week2014-6-25to2014-7-9 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/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker commented on an issue Re: Complete handling of undef/nil Merged into master in d32c49 Add Comment Puppet / PUP-480 Complete handling of undef/nil A decision needs to be made regarding handling of undef as nil. There is agreement that it should be handled as a nil value everywhere except one case; when setting an attribute value. Currently setting undef as an attribute value has the meaning do not set this attribute (as opposed to set this attribute to nil) - which has the effect of selectin... 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/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Support Bundler workflow on x64
Merged #2825 into master at 92cb4f4
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Ethan Brown commented on an issue
Re: Support Bundler workflow on x64
The original x64 platform test was incorrect. A new test has been added that will more accurately determine which gems / platform to use.
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
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/d/optout.
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title
Henrik Lindberg commented on an issue
Re: The manifests directory should be recursively loaded when using directory environments
ok, we can do that (and the test that slurps the entire puppet code base for .pp files needs to be fixed).
Add Comment
Puppet / PUP-2711
The manifests directory should be recursively loaded when using directory environments
We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ...
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-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter Change By: Kylo Ginsberg Assignee: KyloGinsberg 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/d/optout.
Jira (PUP-2871) Add :install_options and :uninstall_options to the pacman provider
Title: Message Title Anthony Weems created an issue Puppet / PUP-2871 Add :install_options and :uninstall_options to the pacman provider Issue Type: New Feature Assignee: Anthony Weems Components: Types and Providers Created: 30/Jun/14 8:19 PM Priority: Normal Reporter: Anthony Weems Original Estimate: 4 hours Remaining Estimate: 4 hours The pacman provider does not currently support adding options to install and uninstalls. For example, it is possible to add a flag to remove all dependencies using :uninstall_options. As a user, I expect the pacman provider to support the use of :install_options and :uninstall_options.
