Jira (PUP-1826) PR (2402): (pup-1825) Allow use of facter 2.x - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1826 PR (2402): (pup-1825) Allow use of facter 2.x - kylog Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 28/Feb/14 10:16 PM Labels: github Priority: Normal Reporter: gepetto-bot (pup-1825) Allow use of facter 2.x Author: Kylo Ginsberg <> Company: Github ID: kylog Pull Request 2402 Discussion Pull Request 2402 File Diff Pull Request Description Before this commit, Puppet uses pessimistic versioning (the ~> syntax) to specify t
Jira (PUP-1825) Allow use of Facter 2
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1825 Allow use of Facter 2 Change By: Kylo Ginsberg Sprint: Week 2014-2-26 to 2014-3-5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1825) Allow use of Facter 2
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-1825 Allow use of Facter 2 Issue Type: Improvement Assignee: Kylo Ginsberg Created: 28/Feb/14 10:08 PM Fix Versions: 3.5.0 Priority: Normal Reporter: Kylo Ginsberg 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
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Jeremy T. Bouse commented on an issue Re: No EC2 facts shown on newly-built Amazon Linux host Just testing 2.0.1 RC1 that was announced on the mailing lists on an EC2-VPC instance root@ip-192-168-112-190:~# dpkg -l facter puppet Desired=Unknown/Install/Remove/Purge/Hold Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend / Err?=(none)/Reinst-required (Status,Err: uppercase=bad) / Name Version Description +++ === ===-== ii facter 2.0.1-0.1rc1puppetlabs1 Ruby module for collecting simple facts about a host operating system ii puppet 3.4.3-1puppetlabs1 Centralized configuration management - agent startup and compatibility root@ip-192-168-112-190:~# facter -p architecture => amd64 augeasversion => 0.10.0 blockdevice_xvda1_size => 8589934592 blockdevices => xvda1 domain => ec2.internal facterversion => 2.0.1-rc1 filesystems => ext3,ext4,iso9660 fqdn => ip-192-168-112-190.ec2.internal hardwareisa => x86_64 hardwaremodel => x86_64 hostname => ip-192-168-112-190 id => root interfaces => eth0,lo ipaddress => 192.168.112.190 ipaddress_eth0 => 192.168.112.190 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 3.2 kernelrelease => 3.2.0-58-virtual kernelversion => 3.2.0 lsbdistcodename => precise lsbdistdescription => Ubuntu 12.04.4 LTS lsbdistid => Ubuntu lsbdistrelease => 12.04 lsbmajdistrelease => 12 lsbrelease => macaddress => 12:43:82:f7:b6:cf macaddress_eth0 => 12:43:82:f7:b6:cf memoryfree => 501.30 MB memoryfree_mb => 501.30 memorysize => 590.17 MB memorysize_mb => 590.17 mtu_eth0 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 192.168.112.0 network_lo => 127.0.0.0 operatingsystem => Ubuntu operatingsystemrelease => 12.04 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games physicalprocessorcount => 1 processor0 => Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz processorcount => 1 ps => ps -ef puppetversion => 3.4.3 rubysitedir => /usr/local/lib/site_ruby/1.8 rubyversion => 1.8.7 selinux => false sshdsakey => B3NzaC1kc3MAAACBAPKNjxy92NWg5tfv+75tKLkCMkMzvwStx4Prg2od8Q+cwjsNgPp5zRv6o7y1ij3ZCRBdiP3S1eWMpsTTHfq64MgWsYFkR3g7eCJWewsPN6rzjTtpwwGcTpGkg6KVNFqdV3PKisKSfxLY4imu+bgGtgIjPbpbMufy+vO7d/eZ8wUFFQCIFS3kBO7UpjlgqxfqBL+W+sVrkwAAAIB5nct4Z0lbUujetVGCMqLwdbSJALJdRquCIqvE1xqVzsCK3CBtMYWDboFPbNOOqGb2EKPUOyTJW55zFCU1PcKGJYEEZAGiR3MlIqVt3S1fRrs8xplskFagrTofh+VJ+YfZ6cONkUTi3SAe72lL1p/Myi+R6jgqV
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Jeremy T. Bouse updated an issue Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host Change By: Jeremy T. Bouse Affects Version/s: 2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1824) PR (225): Bump version and add metadata.json for forge - adreyer
Title: Message Title gepetto-bot created an issue Puppet / PUP-1824 PR (225): Bump version and add metadata.json for forge - adreyer Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 28/Feb/14 4:54 PM Labels: github Priority: Normal Reporter: gepetto-bot Bump version and add metadata.json for forge Author: Alex Dreyer Company: Github ID: adreyer Pull Request 225 Discussion Pull Request 225 File Diff Pull Request Description Is this based off the right branch? What should the earliest versio
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Sprint: Week 2014-2-26 to 2014-3-5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Henrik Lindberg commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
Merged in 2f972f3
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlab...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-222) PR (182): Allow options to be passed to deep_merge - devin-c
Title: Message Title gepetto-bot commented on an issue Re: PR (182): Allow options to be passed to deep_merge - devin-c puppetcla commented: CLA signed by all contributors. Add Comment Hiera / HI-222 PR (182): Allow options to be passed to deep_merge - devin-c h2. Allow options to be passed to deep_merge * Author: Devin Christensen <> * Company: * Github ID: [devin-c|https://github.com/devin-c] * [Pull Request 182 Discussion|https://github.com/puppetlabs/hiera/pull/182] * [Pull Request 182 File Diff|https://github.com/puppetlabs/hiera/pull/182/files] h2. Pull Request Description This enables the e... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1823) PR (224): Add "Release Notes/Known Bugs" to Changelog - laurenrother
Title: Message Title gepetto-bot created an issue Puppet / PUP-1823 PR (224): Add "Release Notes/Known Bugs" to Changelog - laurenrother Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 28/Feb/14 4:00 PM Labels: github Priority: Normal Reporter: gepetto-bot Add "Release Notes/Known Bugs" to Changelog Author: Lauren Company: Puppet Labs, Inc. Github ID: laurenrother Pull Request 224 Discussion Pull Request 224 File Diff Pull Request Description Per a request to have initial release notes th
Jira (PDB-480) Unicode characters in resource titles are converted to the same character
Title: Message Title
Alex Chamberlain updated an issue
PuppetDB / PDB-480
Unicode characters in resource titles are converted to the same character
Change By:
Alex Chamberlain
The Puppet documentation explicitly says that, unlike class names, which are limited to a character set matching a certain well-defined regex, resource titles may contain any characters. (source : http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#resources) Per this ticket: http://projects.puppetlabs.com/issues/11303 you should set the LC_CTYPE or LANG environment variables to whatever encoding system you want to use in your manifests.However, in a resource title that contains UTF-8 characters outside the ordinary lower-127 ASCII set, those characters seem to be handled correctly when Puppet compiles the catalog (see screenshot *puppet-utf8-ok.png*), but PuppetDB considers them the same. As a result, if there is more than one resource with a title that is the same length, but where only the high-bit characters differ, PuppetDB rejects the catalog with the following error message in /var/log/pe-puppetdb/puppetdb.log:{noformat}2014-02-28 19:04:58,026 ERROR [command-proc-48] [puppetdb.command] [bff94b44-0387-47f4-8bd1-1d600cf2cac3] [store report] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.{noformat}This PuppetDB behavior causes Event Inspector to fail with a plain white screen with a pink band containing the message: {{Could not load event inspector. Try refreshing your browser. For more information, check /var/log/pe-puppet-dashboard/event-inspector.log }}. However, the file referred to contains nothing except the timestamped message {{ ERROR Failed to connect to PuppetDB. Check settings (Timeout::Error)}}.
Add Comment
Jira (PDB-480) Unicode characters in resource titles are converted to the same character
Title: Message Title
Alex Chamberlain updated an issue
PuppetDB / PDB-480
Unicode characters in resource titles are converted to the same character
Change By:
Alex Chamberlain
The Puppet documentation explicitly says that, unlike class names, which are limited to a character set matching a certain well-defined regex, resource titles may contain any characters. (source : http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#resources) Per this ticket: http://projects.puppetlabs.com/issues/11303 you should set the LC_CTYPE or LANG environment variables to whatever encoding system you want to use in your manifests.However, in a resource title that contains UTF-8 characters outside the ordinary lower-127 ASCII set, those characters seem to be handled correctly when Puppet compiles the catalog (see screenshot *puppet-utf8-ok.png*), but PuppetDB considers them the same. As a result, if there is more than one resource with a title that is the same length, but where only the high-bit characters differ, PuppetDB rejects the catalog with the following error message in /var/log/pe-puppetdb/puppetdb.log:{noformat}2014-02-28 19:04:58,026 ERROR [command-proc-48] [puppetdb.command] [bff94b44-0387-47f4-8bd1-1d600cf2cac3] [store report] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.{noformat}This PuppetDB behavior causes Event Inspector to fail with a plain white screen with a pink band containing the message: {{ * Could not load event inspector. Try refreshing your browser. For more information, check /var/log/pe-puppet-dashboard/event-inspector.log }} * . However, the file referred to contains nothing except the timestamped message {{ * ERROR Failed to connect to PuppetDB. Check settings (Timeout::Error) }} * .
Add Comment
Jira (PDB-480) Unicode characters in resource titles are converted to the same character
Title: Message Title
Alex Chamberlain updated an issue
PuppetDB / PDB-480
Unicode characters in resource titles are converted to the same character
Change By:
Alex Chamberlain
The Puppet documentation explicitly says that, unlike class names, which are limited to a character set matching a certain well-defined regex, resource titles may contain any characters. (source : http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#resources) Per this ticket: http://projects.puppetlabs.com/issues/11303 you should set the LC_CTYPE or LANG environment variables to whatever encoding system you want to use in your manifests.However, in a resource title that contains UTF-8 characters outside the ordinary lower-127 ASCII set, those characters seem to be handled correctly when Puppet compiles the catalog (see screenshot *puppet-utf8-ok.png*), but PuppetDB considers them the same. As a result, if there is more than one resource with a title that is the same length, but where only the high-bit characters differ, PuppetDB rejects the catalog with the following error message in /var/log/pe-puppetdb/puppetdb.log:{noformat}2014-02-28 19:04:58,026 ERROR [command-proc-48] [puppetdb.command] [bff94b44-0387-47f4-8bd1-1d600cf2cac3] [store report] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "constraint_resource_events_unique" Detail: Key (report, resource_type, resource_title, property)=(3dd00aea8c43e71522ce03d2f869efaae25b315f, Exec, z3, returns) already exists.{noformat}This PuppetDB behavior causes Event Inspector to fail with a plain white screen with a pink band containing the message: {{Could not load event inspector. Try refreshing your browser. For more information, check /var/log/pe-puppet-dashboard/event-inspector.log }}. However, the file referred to contains nothing except the timestamped message {{ ERROR Failed to connect to PuppetDB. Check settings (Timeout::Error)}}.
Add Comment
Jira (PDB-480) Unicode characters in resource titles are converted to the same character
Title: Message Title Alex Chamberlain created an issue PuppetDB / PDB-480 Unicode characters in resource titles are converted to the same character Issue Type: Bug Affects Versions: 1.5.x Assignee: Unassigned Attachments: puppet-utf8-OK.png Created: 28/Feb/14 3:46 PM Environment: Browser: Firefox 25, Mac OS 10.8; Centos 6.4 i386 master and agent nodes running PE build 3.2.0-rc1-20-gf79138e Priority: Normal Reporter: Alex Chamberlain The Puppet documentation explicitly says that, unlike class names, which are limited to a character set matching a certain well-defined regex, resource titles may contain any characters. (source : http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html#resources) Per this ticket: http://projects.puppetlabs.com/issues/11303 you should set the LC_CTYPE or LANG environment variables to whatever encoding system you want to use in your manifests. However, in a resource title that contains UTF-8 characters outside the ordinary lower-127 ASCII set, those characters seem to be handled correctly when Puppet compiles the catalog (se
Jira (FACT-299) Facter 2.0.1-rc1 Release
Title: Message Title Adrien Thebo assigned an issue to Unassigned Facter / FACT-299 Facter 2.0.1-rc1 Release Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-84) Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application
Title: Message Title Andrew Parker commented on an issue Re: Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application Eric Sorenson this was already deprecated as Redmine 22910 and so should already be good for a 4.0.0 removal. Add Comment Puppet / PUP-84 Disable unnecessary termini, Puppet::Resource::Ral should never be enabled in the puppet master application This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend
Title: Message Title
Andrew Parker commented on an issue
Re: "puppet node clean" is hard-coded to use rails/activerecord backend
puppet node clean already calls destroy for the node, facts, and reports. It bypasses the indirector for removing the exported resources. I'm not sure how it can best be pluggable so that puppetdb can slot into this well. Maybe it should also call destroy on Puppet::Resource::Catalog? Ryan Senior or Kenneth Barber, do you have thoughts?
Add Comment
Puppet / PUP-1779
"puppet node clean" is hard-coded to use rails/activerecord backend
See #14721. PuppetDB already has code to remove a node's data ("puppet node deactivate"), but we can't get it to seamlessly work with "puppet node clean" as long as it's hard-coded to assume legacy storeconfigs. This face should use some manner of indirection to allow other storeconfigs backends to participate in node cleanup.
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...@googlegroup
Jira (PUP-1338) yumrepo module is too picky about white space
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: yumrepo module is too picky about white space
How frequently is this change occuring? Is it something that happens on every Puppet run?
Add Comment
Puppet / PUP-1338
yumrepo module is too picky about white space
Where white space exists in a a yum repo file, Puppet yumrepo insists on removing the whitespace. A yum plug-in (subscription-manager, it seems) sets the values as: {{enabled = 0}} Puppet insists on changing this valid entry to {{enabled=0}} Expected behaviour is that yumrepo allows the white space and only changes the value. For example, t...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1338) yumrepo module is too picky about white space
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1338 yumrepo module is too picky about white space Change By: Charlie Sharpsteen Assignee: Matt Willsher Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
It looks like the puppet agent was sent a kill signal at one point:
Feb 11 11:31:25 node1 puppet-agent[1333]: Caught TERM; calling stop
This could explain why an update to /etc/hosts failed to occur — the agent was stopped before flushing changes to that file.
Are you regularly killing or restarting agent daemons during their runs?
Add Comment
Puppet / PUP-1697
hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
The hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode. If a restart of the puppet agent is triggered, the changes are made. {code} Feb 11 11:17:59 node1 puppet-agent[5806]: Finished catalog run in 0.42 seconds Feb 11 11:20:59 node1 puppet-agent[5993]: Finished catalog run in 0.42 seconds Feb 11...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1697 hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode Change By: Charlie Sharpsteen Assignee: Laura Varga Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1665) PR - Puppet cert list behavior is suboptimal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1665 PR - Puppet cert list behavior is suboptimal Change By: Kylo Ginsberg Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1743) Catalog retrieval problems
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Catalog retrieval problems
Hmm... my first guess would be that this indicates an incomplete catalog is being transferred — possibly due to one end of the connection being closed before a complete JSON document has been delivered to the agent.
Could you post a complete log of puppet agent -t --debug --trace for one of these failures?
Add Comment
Puppet / PUP-1743
Catalog retrieval problems
Hello, we have some problems with puppet agent catalog retrieval. When I run puppet agent start -t i got error like: {noformat} Error: Could not retrieve catalog from remote server: Could not intern from text/pson: source did not contain any PSON! or Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': C...
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
Jira (PUP-1822) PR (2401): (pup-1821) Bump the facter dependency to 1.7 or greater - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1822 PR (2401): (pup-1821) Bump the facter dependency to 1.7 or greater - kylog Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 28/Feb/14 2:35 PM Labels: github Priority: Normal Reporter: gepetto-bot (pup-1821) Bump the facter dependency to 1.7 or greater Author: Kylo Ginsberg <> Company: Github ID: kylog Pull Request 2401 Discussion Pull Request 2401 File Diff Pull Request Description
Jira (PUP-1743) Catalog retrieval problems
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1743
Catalog retrieval problems
Change By:
Charlie Sharpsteen
Hello,we have some problems with puppet agent catalog retrieval. When I run puppet agent start -t i got error like: {noformat} Error: Could not retrieve catalog from remote server: Could not intern from text/pson: source did not contain any PSON!orError: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': Could not intern_multiple from text/pson: source did not contain any PSON! {noformat} But! If we try to run it more times in a row it works again. For example I run puppet agent start -t 3 times and on third try it works as expected.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-309) Go/no-go meeting
Title: Message Title Adrien Thebo commented on an issue Re: Go/no-go meeting We are go for Facter 2.0.1rc1. \o/ Add Comment Facter / FACT-309 Go/no-go meeting This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1779 "puppet node clean" is hard-coded to use rails/activerecord backend Change By: Eric Sorenson Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend
Title: Message Title
Eric Sorenson commented on an issue
Re: "puppet node clean" is hard-coded to use rails/activerecord backend
Yes all the AR stuff is going away so this should work better in 4... ping Andrew Parker and targeting 4.0.0.
Add Comment
Puppet / PUP-1779
"puppet node clean" is hard-coded to use rails/activerecord backend
See #14721. PuppetDB already has code to remove a node's data ("puppet node deactivate"), but we can't get it to seamlessly work with "puppet node clean" as long as it's hard-coded to assume legacy storeconfigs. This face should use some manner of indirection to allow other storeconfigs backends to participate in node cleanup.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1743) Catalog retrieval problems
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1743 Catalog retrieval problems Change By: Charlie Sharpsteen Assignee: Jakub Bittner Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Mingw gem on Windows 2008R2: ��architecture => x64 domain => corp.puppetlabs.net facterversion => 2.0.1-rc1 fqdn => win2008r2x64.corp.puppetlabs.net hardwareisa => unknown hardwaremodel => x64 hostname => win2008r2x64 id => win2008r2x64\vagrant interfaces => Local_Area_Connection ipaddress => 10.0.2.15 ipaddress_local_area_connection => 10.0.2.15 is_virtual => true kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 macaddress => 08:00:27:53:A9:7C macaddress_local_area_connection => 08:00:27:53:A9:7C manufacturer => innotek GmbH memoryfree => 387.79 MB memoryfree_mb => 387.79 memorysize => 1023.55 MB memorysize_mb => 1023.55 netmask => 255.255.255.0 netmask_local_area_connection => 255.255.255.0 network_local_area_connection => 10.0.2.0 operatingsystem => windows operatingsystemrelease => 2008 R2 osfamily => windows path => %SystemRoot%\system32\WindowsPowerShell\v1.0\;C:\Program Files\ConEmu\ConEmu;C:\Program Files\ConEmu;C:\ruby193\bin;C:\ruby200\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Chocolatey\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\Git\bin;C:\Program Files (x86)\GitExtensions; physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => tasklist.exe rubysitedir => C:/ruby193/lib/ruby/site_ruby/1.9.1 rubyversion => 1.9.3 serialnumber => 0 timezone => Coordinated Universal Time uptime => 0:15 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 909 virtual => virtualbox Add Comment Facter / FACT-308 Smoke test packages Procedure m
Jira (PUP-542) Provide access to all facts in a single structure
Title: Message Title
Andrew Parker commented on an issue
Re: Provide access to all facts in a single structure
Merged the fixed deep_freeze into master in 4d541e
Add Comment
Puppet / PUP-542
Provide access to all facts in a single structure
The facts that are reported by the agent should be accessible via a top-scope {{$facts}} hash. The keys are the fact names and the values are the fact values. If this variable is shadowed in a scope the evaluator should emit a warning.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1791) PR (2394): (maint) Allow arrays, bools, and numerics to be frozen - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (2394): (maint) Allow arrays, bools, and numerics to be frozen - adrienthebo Pull request (maint) Allow arrays, bools, and numerics to be frozen has been closed. Add Comment Puppet / PUP-1791 PR (2394): (maint) Allow arrays, bools, and numerics to be frozen - adrienthebo h2. (maint) Allow arrays, bools, and numerics to be frozen * Author: Adrien Thebo git...@somethingsinistral.net> * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 2394 Discussion|https://github.com/puppetlabs/puppet/pull/2394] * [Pull Request 2394 File Diff|https://github.com/puppetlabs/puppet/pull... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Smoke test packages
Mac OS X 10.9.2:
[1] ~ facter
architecture => x86_64
domain => local
facterversion => 2.0.1-rc1
fqdn => kylo.local
hardwareisa => i386
hardwaremodel => x86_64
hostname => kylo
id => kylo
interfaces => lo0,gif0,stf0,en0,en5,en6,bridge0,p2p0,vmnet1,vmnet8,tun0
ipaddress => 192.168.1.101
ipaddress_en0 => 192.168.1.101
ipaddress_lo0 => 127.0.0.1
ipaddress_tun0 => 10.16.124.14
ipaddress_vmnet1 => 172.16.133.1
ipaddress_vmnet8 => 192.168.149.1
is_virtual => false
kernel => Darwin
kernelmajversion => 13.1
kernelrelease => 13.1.0
kernelversion => 13.1.0
macaddress => 54:26:96:d6:72:6b
macaddress_bridge0 => 56:26:96:6d:4c:00
macaddress_en0 => 54:26:96:d6:72:6b
macaddress_en5 => 32:00:14:66:48:20
macaddress_en6 => 32:00:14:66:48:21
macaddress_p2p0 => 06:26:96:d6:72:6b
macaddress_vmnet1 => 00:50:56:c0:00:01
macaddress_vmnet8 => 00:50:56:c0:00:08
macosx_buildversion => 13C64
macosx_productname => Mac OS X
macosx_productversion => 10.9.2
macosx_productversion_major => 10.9
macosx_productversion_minor => 2
memoryfree => 1.72 GB
memoryfree_mb => 1759.84
memorysize => 8.00 GB
memorysize_mb => 8192.00
mtu_bridge0 => 1500
mtu_en0 => 1500
mtu_en5 => 1500
mtu_en6 => 1500
mtu_gif0 => 1280
mtu_lo0 => 16384
mtu_p2p0 => 2304
mtu_stf0 => 1280
mtu_tun0 => 1500
mtu_vmnet1 => 1500
mtu_vmnet8 => 1500
netmask => 255.255.255.0
netmask_en0 => 255.255.255.0
netmask_lo0 => 255.0.0.0
netmask_tun0 => 255.255.255.0
netmask_vmnet1 => 255.255.255.0
netmask_vmnet8 => 255.255.255.0
network_en0 => 192.168.1.0
network_lo0 => 127.0.0.0
network_tun0 => 10.16.124.0
network_vmnet1 => 172.16.133.0
network_vmnet8 => 192.168.149.0
operatingsystem => Darwin
operatingsystemrelease => 13.1.0
osfamily => Darwin
path => /usr/local/opt/rbenv/shims:/usr/local/opt/rbenv/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Applications/VMware Fusion.app/Contents/Library
processorcount => 4
productname => MacBookPro10,2
ps => ps auxwww
rubysitedir => /Library/Ruby/Site/2.0.0
rubyversion => 2.0.0
sp_boot_mode => normal_boot
sp_boot_rom_version => MBP102.0106.B03
sp_boot_volume => Puppet HD
sp_cpu_type => Intel Core i5
sp_current_processor_speed => 2.6 GHz
sp_kernel_version => Darwin 13.1.0
sp_l2_cache_core => 256 KB
sp_l3_cache => 3 MB
sp_local_host_name => kylo
sp_machine_model => MacBookPro10,2
sp_machine_name => MacBook Pro
sp_mmm_entry => {"MMM_state"=>"MMM_enabled"}
sp_number_processors => 2
sp_os_version => OS X 10.9.2 (13C64)
sp_packages => 1
sp_physical_memory => 8 GB
sp_platform_uuid => 7235F8EF-D7A5-570F-91F9-0E45BCB8A69D
sp_secure_vm => secure_vm_enabled
sp_serial_number => C02KQ10BFFRP
sp_smc_version_system => 2.6f59
sp_uptime => up 2:15:58:20
sp_user_name => Kylo (kylo)
sshdsakey => B3NzaC1kc3MAAACBAJiiGi26dUGeMTK9y92XhJ8x8xe8Ack1EOkVyW3rsfhe4vjJGTqiJa9YbW0T7QxYjEelpZa3Dn24ylhNg5TDfBnsRhQTyOpTA4mB7u8SX2/ghvwjdOuqF3DtmuIwXfltjyMEDXoZNaoW2wduNdgvT3M53RbPBMDn7Us7a47ZyvAzFQDyuxHpWauQ67EW4IvTUWKr5zPIbQAAAIBJFvbVRswA0O7s3dRxQig/QseBtCPn3YxycD5YRqt3SeGCycER8XmadREHQ5CSNRXBi0qruajwA0HSG/R/FhPIVlxpV1c9OAKo3vFTlM2FKfU857aPvRtANhGMiI+lkLS9zoQlFFZDmH/YbB9pFSBWtA3+KNEMbTvzXCZSan5yHwAAAIA3e0chBEBIfhFOwIkmVBTyPzwxExHLXsVNWXEIrZIQWC20tmpvfGtP4zWWBH3XZnel6IXt/7fs/JJlnlasOAsDyfKbJ/4h86NKQwZK06hChAuzxAQ70/F/g/nwU/aRKduf9049EbAbd+iWS0EKwIynoksS9drP3BTRMPtXKNHlbQ==
sshecdsakey => E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBEEC475zvVHGHBWHlZrGTjX9Y4Yw9g87z0usixoKjTPX37iaUqCeyXS5WZnEVscx5gEfVzq0MEMFAnvySRJhc0M=
sshfp_dsa => SSHFP 2 1 535b799bad0e5a46d2d8171864cd2fc91fcd25b4
SSHFP 2 2 6b4f00c303bc0cb20837f0d04d9b904c5baac5522f516c4a7d7554c8ba96a761
sshfp_ecdsa => SSHFP 3 1 2052fdb52befedd8a74f09300a2b297d86535789
SSHFP 3 2 35bc5e3a17742a26abe3e3d411f9b5ad558fff591e5ea9a56964d5000d5252e8
sshfp
Jira (PUP-1792) alias for resource can't be used with realize
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1792
alias for resource can't be used with realize
Change By:
Charlie Sharpsteen
It seems a resource alias is only usable in dependencies. Example: {code} @package {"coreutils": alias => "foo", ensure => installed }realize Package["foo"] {code} Result: {noformat} Failed to realize virtual resources Package[foo] on node feh {noformat} I would expect it to work. Testing was done on 0.25.5.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1761) how to terminate an AWS instance without dnsnames under VPC
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1761 how to terminate an AWS instance without dnsnames under VPC Change By: Charlie Sharpsteen Labels: cloud_provisioner Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages Mac OSX 10.7: architecture => x86_64 domain => local facterversion => 1.7.5-rc1 fqdn => melissas-Mac.local hardwareisa => i386 hardwaremodel => x86_64 hostname => melissas-Mac id => melissa interfaces => lo0,gif0,stf0,en0 ipaddress => 172.16.123.203 ipaddress_en0 => 172.16.123.203 ipaddress_lo0 => 127.0.0.1 is_virtual => true kernel => Darwin kernelmajversion => 11.0 kernelrelease => 11.0.0 kernelversion => 11.0.0 macaddress => 00:0c:29:95:0d:fe macaddress_en0 => 00:0c:29:95:0d:fe macosx_buildversion => 11A511 macosx_productname => Mac OS X macosx_productversion => 10.7 macosx_productversion_major => 10.7 macosx_productversion_minor => 0 memoryfree => 1.34 GB memoryfree_mb => 1371.24 memorysize => 2.00 GB memorysize_mb => 2048.00 memorytotal => 2.00 GB mtu_en0 => 1500 mtu_gif0 => 1280 mtu_lo0 => 16384 mtu_stf0 => 1280 netmask => 255.255.255.0 netmask_en0 => 255.255.255.0 netmask_lo0 => 255.0.0.0 network_en0 => 172.16.123.0 network_lo0 => 127.0.0.0 operatingsystem => Darwin operatingsystemrelease => 11.0.0 osfamily => Darwin path => /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin processorcount => 1 productname => VMware7,1 ps => ps auxwww rubysitedir => /Library/Ruby/Site/1.8 rubyversion => 1.8.7 sp_64bit_kernel_and_kexts => yes sp_boot_mode => normal_boot sp_boot_rom_version => VMW71.00V.0.B64.1206270404 sp_boot_volume => Macintosh HD sp_current_processor_speed => 2.19 GHz sp_kernel_version => Darwin 11.0.0 sp_l2_cache => 256 KB sp_l3_cache => 3 MB sp_local_host_name => melissa’s Mac sp_machine_model => VMware7,1 sp_machine_name => Mac sp_number_processors => 1 sp_os_version => Mac OS X 10.7 (11A511) sp_packages => 1 sp_physical_memory => 2 GB sp_platform_uuid => --1000-8000-000C29950DFE sp_secure_vm => secure_vm_enabled sp_serial_number => VMWVk0+6ZBwUv4MdAJAw5UN/g sp_smc_version_system => 1.16f8 sp_uptime => up 0:5:21:55 sp_user_name => melissa (melissa) sshdsakey => B3NzaC1kc3MAAACBAPRzkc2OK8RSWWzBecrGyu+So3Qr8pZpfB9rwj1dVG/IASjfsxkJvE4O9o3iPGVk2TS5HwuLej7eGfyRvbFZQ95pplbxkwWF5RURNJ+FuLNaLQC4baHOzAc5AC2me4Ch/O8i8UJynCx+iVoMI+6tH7BUk5zew4fXLrv4CBB4zHxhFQDR5bnfjYYR3puuE8NE4zw2X0xitwAAAIBOfjhYBhJCusn54vVp2DPIKbEOcKyWgfy7Gjblc0z4vn59tnm2byKDehgya2r6poSehNeTb/es/KtKimNsLqfVDUPRkmx0bxPjmJqCZknugCO71u0mtdiZXfpVCt4UkdYBuu/f/Iz98Vol3HDrWjyu23ZvalTu23AuuQCfIi86FIEA0Y0khFAa2IolypzkaDq7ddQXZmt5y0kxM040g2M5FvPgfi69ks/Ra7cURfu5FIkNKsWfjWmA+9wHa1pqChv9T5hbaDtiiFJaYdq+bJmabmtho26QFxnWaaQzWHUPOXAR3S4+dZG0m8GuBmz4Fo+mQSI7U68dcOU+cZYpb/YzJMs= sshfp_dsa => SSHFP 2 1 d8028368a05d3a14dcbd2093488aade69d1e3a90 SSHFP 2 2 80deb15c91f4a570d66527507f1ba8e845e2c09e328eaaf537c49ea1aa32327d sshfp_rsa => SSHFP 1 1 a39a386a3cfa5d3ab4441e8a2e2e1a9225fec38d SSHFP 1 2 c351604ef9cac5e0ca072420029ff646ca43b87215e50fad271cd171466af352 sshrsakey => B3NzaC1yc2EDAQABAAABAQDYVlGR1xripOAxYHPFT1M5cUocr4T4v3mS8WaYKI1NXaDp3z6wazi5HEMExdTcZW7kkdoPT//0+1nfHGfvjK5oninnQZ9wcl9X5APqgltu0YShfS4ffvTL+8/GhvKcW7i8cjaNqdDThGf8dZknwfm9UQml840rRtP9x4rXEZfhhq0Inwh957tsnBjJQcqmr36btH0J1cS0uqCxy6lEyll9KX2CWVNfIHABPIygWv6es15m2EEMUSqDFu0aWGy1V/L/RpyIhcyZR64rd+veh7YB7FZ14bAhY12dO5F7mLBJVxo4AenLYmUHziya9KK1LTFyC8fW/hmb6NBNPnigNU/H swapencrypted => true swapfree => 64.00 MB swapfree_mb => 64.00 swapsize => 64.00 MB swapsize_mb => 64.00 timezone => PST uptime => 5:21 hours uptime_days => 0 uptime_hours => 5 uptime_seconds => 19285 virtual => vmware
Jira (PUP-1761) how to terminate an AWS instance without dnsnames under VPC
Title: Message Title Charlie Sharpsteen commented on an issue Re: how to terminate an AWS instance without dnsnames under VPC Moving to ENTERPRISE project as that is where cloud-provisioner tickets ended up after the Great Redmine Migration. Add Comment Puppet / PUP-1761 how to terminate an AWS instance without dnsnames under VPC We are trying to evaluate the puppt and having trouble terminating an instance created by puppet puppet node_aws terminate dns-name but the instance that I am creating doesn't have an dns name and it is inside vpc. when use instance-id instead it does not work This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Gem install on Debian 6: root@debian-6:~# facter --version 2.0.1-rc1 root@debian-6:~# facter architecture => i386 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 facterversion => 2.0.1-rc1 filesystems => ext2,ext3 hardwareisa => unknown hardwaremodel => i686 hostname => debian-6 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.134 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.32-5-686 kernelversion => 2.6.32 lsbdistcodename => squeeze lsbdistdescription => Debian GNU/Linux 6.0.7 (squeeze) lsbdistid => Debian lsbdistrelease => 6.0.7 lsbmajdistrelease => 6 lsbrelease => macaddress => 08:00:27:3a:9d:d7 macaddress_eth0 => 08:00:27:3a:9d:d7 macaddress_eth1 => 08:00:27:31:c0:a9 manufacturer => innotek GmbH memoryfree => 340.09 MB memoryfree_mb => 340.09 memorysize => 375.61 MB memorysize_mb => 375.61 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => Debian operatingsystemmajrelease => 6 operatingsystemrelease => 6.0.7 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/local/lib/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBAMao58AjusuEma6TzpnF8h/lN7g0A3wWmAOyO8VuikEH4eCpE59AflF+z+c+jzhQa/oHl7fpf5XohTAkrY6W4Y/YQnOCkfrRKSa9NliRl+hYf+Y0lDTFr7Cdk8NE5aAWflNrVHxXrrSS+4x/D52BG5WnNG+psezosW6UuvciVMjLFQD3kZRXLhGZklygKctBIDY7Vb5TwQAAAIEAjMaroVHtoTu/3txJ/EeE6WJn4f37U/8j0harBF19KuJb8ult4sTlxg2FPGmdZBecPcMDbIxcuINzr2Jviyg9ZnzjbR44f106ZQgIFIjElO79XE3PsHJa0vfKpRuTmChnfcWgVH+T7tMLSRa9BO1kwy+Uj4bhqjpYpfpa/sWv+E8AAACBAKu4uMlXgwLDuqEfNZ5htQuIty6xkQRvPo1ziE06ppSj4Vy2NZy80OIFppwumkqKqxbS9j3SCxPj1M01Jsysx2HuJaWq0mTi/plMGxY3yN+YIbOpNGcOkOu1/JSlHMBjRwqEUy07Opo9SvhiBl5etWXw1V1Wg61VF0EOIp1xnV5b sshfp_dsa => SSHFP 2 1 e2dec8bb4349c557cab7111cdeece9060ee65b1c SSHFP 2 2 1505077ddefd207792093b808c0d247a7d1710df50a46910f02955769efc06ab sshfp_rsa => SSHFP 1 1 a03ec0d9ca479337890f4323309c810b293cb9b8 SSHFP 1 2 664da055eb8ae3e2cabc0cb465a5e2115295c659489adcde95c825e8a49d4a2d sshrsakey => B3NzaC1yc2EDAQABAAABAQCiKOi7C4mkdFzKbEugMDXZWE8aKwyJgakDarZdSrg7/Fmg7ihlprgv4pw3r1WNBmWFduvAEF1clQ/8aOcA2S9332FemzGVyvTSpoM2GtyLo5b2E07y2sPgLMEwtPZJSdOYjfBQZDTKYJlo003PVX5G2EKvkj30Ocqh1BI15QwJTJF6yhPw+9nlMJw1wlN9Z7oGKeeWPGW7c6d3GZceaAMlRFvyY30fb5Ip68m1f87lYA7tddEYPjY03NC9TbgDPJyzX2eLKH9mwzm6UCnIFGFkb7mwGsrEoILyvsjguJFSWHtubRCCOyGI5Aj5TSCf87Bw6sdomEq5QbTpGryWDac9 swapfree => 455.99 MB swapfree_mb => 455.99 swapsize => 455.99 MB swapsize_mb => 455.99 timezone => UTC type => Other uniqueid => 007f0101 uptime => 0:03 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 211 uuid => 40BBC28B-01B8-4D14-BBA1-97CE0537010C virtual => virtualbox vlans =>
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Henrik Lindberg commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
This will only be fixed in the --parser future branch of puppet as the change may cause breakage. The fix will be standard behavior in Puppet 4.0.
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlab...
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
Jira (PUP-1821) Bump facter dependency to 1.7 or greater
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1821 Bump facter dependency to 1.7 or greater Change By: Kylo Ginsberg Sprint: Week 2014-2-26 to 2014-3-5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1821) Bump facter dependency to 1.7 or greater
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1821 Bump facter dependency to 1.7 or greater Change By: Kylo Ginsberg Facter 1.7 has been out since April 2013 and we don't test against facter 1.6, so really can't make any guarantees about behavior with facter 1.6. In addition this is apparently a recurring issue for the modules team, where users manage to update puppet without ever updating facter. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Fix Version/s: 3.6.0 Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 6: architecture => i386 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 facterversion => 2.0.1-rc1 filesystems => ext2,ext3 hardwareisa => unknown hardwaremodel => i686 hostname => debian-6 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.134 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.32-5-686 kernelversion => 2.6.32 lsbdistcodename => squeeze lsbdistdescription => Debian GNU/Linux 6.0.7 (squeeze) lsbdistid => Debian lsbdistrelease => 6.0.7 lsbmajdistrelease => 6 lsbrelease => macaddress => 08:00:27:3a:9d:d7 macaddress_eth0 => 08:00:27:3a:9d:d7 macaddress_eth1 => 08:00:27:31:c0:a9 manufacturer => innotek GmbH memoryfree => 340.39 MB memoryfree_mb => 340.39 memorysize => 375.61 MB memorysize_mb => 375.61 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => Debian operatingsystemmajrelease => 6 operatingsystemrelease => 6.0.7 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/local/lib/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBAMao58AjusuEma6TzpnF8h/lN7g0A3wWmAOyO8VuikEH4eCpE59AflF+z+c+jzhQa/oHl7fpf5XohTAkrY6W4Y/YQnOCkfrRKSa9NliRl+hYf+Y0lDTFr7Cdk8NE5aAWflNrVHxXrrSS+4x/D52BG5WnNG+psezosW6UuvciVMjLFQD3kZRXLhGZklygKctBIDY7Vb5TwQAAAIEAjMaroVHtoTu/3txJ/EeE6WJn4f37U/8j0harBF19KuJb8ult4sTlxg2FPGmdZBecPcMDbIxcuINzr2Jviyg9ZnzjbR44f106ZQgIFIjElO79XE3PsHJa0vfKpRuTmChnfcWgVH+T7tMLSRa9BO1kwy+Uj4bhqjpYpfpa/sWv+E8AAACBAKu4uMlXgwLDuqEfNZ5htQuIty6xkQRvPo1ziE06ppSj4Vy2NZy80OIFppwumkqKqxbS9j3SCxPj1M01Jsysx2HuJaWq0mTi/plMGxY3yN+YIbOpNGcOkOu1/JSlHMBjRwqEUy07Opo9SvhiBl5etWXw1V1Wg61VF0EOIp1xnV5b sshfp_dsa => SSHFP 2 1 e2dec8bb4349c557cab7111cdeece9060ee65b1c SSHFP 2 2 1505077ddefd207792093b808c0d247a7d1710df50a46910f02955769efc06ab sshfp_rsa => SSHFP 1 1 a03ec0d9ca479337890f4323309c810b293cb9b8 SSHFP 1 2 664da055eb8ae3e2cabc0cb465a5e2115295c659489adcde95c825e8a49d4a2d sshrsakey => B3NzaC1yc2EDAQABAAABAQCiKOi7C4mkdFzKbEugMDXZWE8aKwyJgakDarZdSrg7/Fmg7ihlprgv4pw3r1WNBmWFduvAEF1clQ/8aOcA2S9332FemzGVyvTSpoM2GtyLo5b2E07y2sPgLMEwtPZJSdOYjfBQZDTKYJlo003PVX5G2EKvkj30Ocqh1BI15QwJTJF6yhPw+9nlMJw1wlN9Z7oGKeeWPGW7c6d3GZceaAMlRFvyY30fb5Ip68m1f87lYA7tddEYPjY03NC9TbgDPJyzX2eLKH9mwzm6UCnIFGFkb7mwGsrEoILyvsjguJFSWHtubRCCOyGI5Aj5TSCf87Bw6sdomEq5QbTpGryWDac9 swapfree => 455.99 MB swapfree_mb => 455.99 swapsize => 455.99 MB swapsize_mb => 455.99 timezone => UTC type => Other uniqueid => 007f0101 uptime => 0:01 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 87 uuid => 40BBC28B-01B8-4D14-BBA1-97CE0537010C virtual => virtualbox vlans =>
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1814 Double backslashes in single quote strings should be interpreted as single Change By: Henrik Lindberg Labels: DSL redmine Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1821) Bump facter dependency to 1.7 or greater
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-1821 Bump facter dependency to 1.7 or greater Issue Type: Improvement Assignee: Unassigned Created: 28/Feb/14 1:51 PM Fix Versions: 3.5.0 Priority: Normal Reporter: Kylo Ginsberg 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, s
Jira (PUP-1779) "puppet node clean" is hard-coded to use rails/activerecord backend
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: "puppet node clean" is hard-coded to use rails/activerecord backend
Eric Sorenson Is this something we still need to fix for Puppet 4?
Add Comment
Puppet / PUP-1779
"puppet node clean" is hard-coded to use rails/activerecord backend
See #14721. PuppetDB already has code to remove a node's data ("puppet node deactivate"), but we can't get it to seamlessly work with "puppet node clean" as long as it's hard-coded to assume legacy storeconfigs. This face should use some manner of indirection to allow other storeconfigs backends to participate in node cleanup.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Ubuntu 12.04: architecture => amd64 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 domain => 04-x64 facterversion => 2.0.1-rc1 filesystems => ext2,ext3,ext4,vfat fqdn => ubuntu-12.04-x64 hardwareisa => x86_64 hardwaremodel => x86_64 hostname => ubuntu-12 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.137 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 3.5 kernelrelease => 3.5.0-23-generic kernelversion => 3.5.0 lsbdistcodename => precise lsbdistdescription => Ubuntu 12.04.2 LTS lsbdistid => Ubuntu lsbdistrelease => 12.04 lsbmajdistrelease => 12 lsbrelease => macaddress => 08:00:27:0f:67:ea macaddress_eth0 => 08:00:27:0f:67:ea macaddress_eth1 => 08:00:27:ed:12:7d manufacturer => innotek GmbH memoryfree => 425.56 MB memoryfree_mb => 425.56 memorysize => 491.21 MB memorysize_mb => 491.21 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => Ubuntu operatingsystemrelease => 12.04 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/local/lib/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBAM7xkV/4Q+vcuK0a6af7qVEoc6eSM6GbvFuzoTBV5op14wl0ajkxUlrOdXG0gQDsA+2j+5TyyKkdhD2Wdkkji1cagA1mUJFDcVSVeXipFibBtd7wmGNdbEbCjByL8ZM71AS3y6JywygpoX3k9l+qhuJdc01wwNRV937Md1+zmNF/FQCPEqcFfYRS0J9qxTkotkDb0ObF8wAAAIEAjteqq8MGXAejpufCbR5BF7992wo/naz6WOi1e5hcE53rQ/3GEBQhN7qEu+79wA1jZs2433xOoK9aA76pXIZs682pf022wDIN/RRa/8pjoH603asbY30NookmyD7CdRKGu1NJW2XgEYHHvypa3d2TEf1/B/zZCEG0Sf0x+MTFwuMAAACBAI3VHzREuRjdt+Pjv2UrXVtbuQYlAuXTzL5k3LPoCJX6bZWxB8ZkBH5TUVY0dm8+Z5jT8uyfOlez8rx6dSb5yCU/xtCYv6od9qvn1bRQGqwME9uRSKUuobu8lDD0sAaeHEhBskPbYQTiFImG51uW5K9uutTR7+sqs1TqWB/czPsw sshecdsakey => E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLBtSpI6A01NXAodidU0F2aFYsKsZS/w3TQC79BSBiIX7jkr61Sk5U9ui98DJ75yI1cu40m0U1UYyx6ic8YrmCw= sshfp_dsa => SSHFP 2 1 50660f826759a12fe1a9a798418936739b1e41cf SSHFP 2 2 d88a5eee3ca9e8c68f668ad7fd21f5feb8b324bd2efaa35b78fcdcf415496279 sshfp_ecdsa => SSHFP 3 1 5ac9d8a3d8d21350da19cd71d21b1cb4ddcd32e1 SSHFP 3 2 31425eee47ed3ae3e968f6bc48ab5a645f899744848d81d768b2ad38b43c289b sshfp_rsa => SSHFP 1 1 ff2e5147dbd06309221334e95182a2578376b99c SSHFP 1 2 a4fa733c8b80d653e1f7bde1a62aa32e7d3b011681ee59bfd014642d8900f744 sshrsakey => B3NzaC1yc2EDAQABAAABAQCXu5RlDOqQ9yghl+U0dkglhOQD6maadTZ34t8KlEwjFnhOx1jpbKVRG2vIJCDusHcIxYPS+uN4owEFbz7l9MtEwCMkzf9fg1imlzRnItAkFtcDZx/jV/PDWcESnTXhc2DRW51IM3pzyHoYThj/cQF4rRDlif1S0H6uj9soJRQi/ftoB62Zkme4j6/GMhY6iJzH3KifTAd3gxaRdp/28/Ym+Q1YZNXAq/BpnNSTEhg9kyHX6M9aTOfZ1K4jqtQaJSiJxZvVZMcWP2lbwIy3NR2uX6D27LK0vd57XOj49R6RjhAnFEKq1Hxa1qOdQrYEeGLuFqMEVwVT6NNuRgFIpyyx swapfree => 512.00 MB swapfree_mb => 512.00 swapsize => 512.00 MB swapsize_mb => 512.00 timezone => UTC type => Other uniqueid => 007f0101 uptime => 0:01 hours uptime_d
Jira (PUP-1794) Resource Alias and Relationship Chaining Error
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1794
Resource Alias and Relationship Chaining Error
Change By:
Charlie Sharpsteen
OverviewResource chaining does not function with aliased namevarsExample {code} class aliased_mysql_gem { Package['libmysqlclient-dev'] -> Package['mysql_gem'] package { 'mysql': ensure =>; '2.8.1', provider => gem, alias => 'mysql_gem', }} {code} Expected behaviorThe given manifest aliases the mysql gem to 'mysql_gem', and adds a relationship between it and libmysqlclient-dev via resource chaining.Actual behaviorApplying the given manifest produces the following error: {noformat} Could not find resource 'Package[mysql_gem]' for relationship from 'Package[libmysqlclient-dev]' on node bappelt-vbox.gateway.2wire.net {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1794) Resource Alias and Relationship Chaining Error
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-1794 Resource Alias and Relationship Chaining Error Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Henrik Lindberg commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
And I forget, this behavior prevents a single quoted string from ending with a backslash
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlab...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1796
File resource fails for root(/) directory.
Re-verified with Puppet 3.4.3. Setting to Accepted as per the Redmine ticket.
Change By:
Charlie Sharpsteen
Affects Version/s:
3.4.3
Labels:
redmine type_file
I know this is probably an extreme edge case, but I recently noticed that this fails: {code} file { '/': ensure => directory }with the error: Parameter path failed: File paths must be fully qualified, not '' at /tmp/test.pp:1 {code} A little background, This comes from a larger module that I have which uses the lvm module to create additional or grow existing filesystems on a server. The file resource is used to make sure the mount point exists before using the mount resource to manage /etc/fstab and mount the filesystem. I noticed that if I tried to use my custom module to grow the root(/) filesystem that I got the error above. Is the / being removed to make it an empty path as a result of some code to try and remove trailing slashes from paths?
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Henrik Lindberg commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
notice 'a single \ and a double backslash \\ and then escaped garbage \g'
notice "a single \ and a double backslash \\ and then escaped garbage \g"
produces the same output for both existing and future parsers
Warning: Unrecognised escape sequence '\ ' in file /Users/henrik/git/puppet/foo.pp at line 2
Warning: Unrecognised escape sequence '\g' in file /Users/henrik/git/puppet/foo.pp at line 2
Notice: Scope(Class[main]): a single \ and a double backslash \\ and then escaped garbage \g
Notice: Scope(Class[main]): a single \ and a double backslash \ and then escaped garbage \g
It has worked this way for quite some time.
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlab...
Jira (PUP-1797) puppet node clean does not remove records from inventory_nodes
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1797 puppet node clean does not remove records from inventory_nodes Change By: Charlie Sharpsteen Assignee: Jason A. Smith Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1639) Some modules fail to install into target_dir
Title: Message Title Andrew Parker commented on an issue Re: Some modules fail to install into target_dir Eric Veiras Galisson, I think NFS was too specific. I believe it will happen any time the location that the module tool works (/var/lib/puppet, I think) is a different filesystem mount from the place the module is being installed into. This changes it from being a simple move to a copy of the module directory. Add Comment Puppet / PUP-1639 Some modules fail to install into target_dir puppet module install puppetlabs/apache -i puppet/forge-modules Notice: Preparing to install into /home/www/puppet/forge-modules ... Notice: Created target directory /home/www/puppet/forge-modules Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file or directory - /home/www/puppet/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-1797) puppet node clean does not remove records from inventory_nodes
Title: Message Title Charlie Sharpsteen commented on an issue Re: puppet node clean does not remove records from inventory_nodes Jason A. Smith, are you experiencing this issue when using the ActiveRecord based inventory service or PuppetDB? Add Comment Puppet / PUP-1797 puppet node clean does not remove records from inventory_nodes I'm working with the Puppet inventory REST API, and noticed that several old node records remain in the inventory_nodes table that I have previously cleaned using `puppet node clean` I would expect that along with exported resources, the inventory data would also be cleaned by using `puppet node clean` This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Andrew Parker commented on an issue Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Yes, I think the gem topic is different from this. I've changed the status to "Designing" since this is a problem that we've known about for a long time and we've had a lot of ideas about how it needs to proceed. Felix's comment about note-8 in 12173 being the most complete and accurate writeup is right. The current plan to move this forward is to work toward running puppet using JRuby and then we can ensure that each environment is fully separate. Add Comment Puppet / PUP-731 Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Quoted from a previous ticket, #4409 The key problem is that a master can’t reliably distinguish between two versions of the same native type that are used in different environments (or between an environment which uses a native type and an environment which doesn’t). This is due to the fact that native types are defined using ruby code, which the mast... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1813) Ubuntu 12.04: The upstart provider can not handle attribute enable
Title: Message Title Charlie Sharpsteen commented on an issue Re: Ubuntu 12.04: The upstart provider can not handle attribute enable It looks like the upstart provider should be deferring back to the debian provider in the case of sysV init scripts. This manages enable/disable using update-rc.d. Matthew Barr: Is this the behavior you are seeing when managing sysV services? If not, could you provide an example of a service that is being mismanaged? Add Comment Puppet / PUP-1813 Ubuntu 12.04: The upstart provider can not handle attribute enable Seems like puppet doesn't support the enable/disable parameter on Ubuntu (12.04) One easy way would be to use the manual option: echo manual >> /etc/init/.override (as root) Even though Ubuntu is scheduled to move to systemd, it will still use upstart on 14.04, and probably beyond. 14.04 will be around for a long time, as an LTS release. 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 ema
Jira (PUP-1813) Ubuntu 12.04: The upstart provider can not handle attribute enable
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1813 Ubuntu 12.04: The upstart provider can not handle attribute enable Change By: Charlie Sharpsteen Assignee: Matthew Barr Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Change By:
Henrik Lindberg
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't.The following manifest: {code} notice('foo\\bar') {code} Gives: {code} notice: Scope(Class[main]): foo\\bar {code} This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlabs.com/guides/language_guide.html#quoting)
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1814) Double backslashes in single quote strings should be interpreted as single
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Double backslashes in single quote strings should be interpreted as single
Marking as accepted as per the Redmine ticket.
Add Comment
Puppet / PUP-1814
Double backslashes in single quote strings should be interpreted as single
Double backslashes in single quoted strings should be interpreted as single backslashes but aren't. The following manifest: notice('foo\\bar') Gives: notice: Scope(Class[main]): foo\\bar This is not the behavior described at [http://docs.puppetlabs.com/guides/language_guide.html#quoting](http://docs.puppetlabs.com/guides/language_guide
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo kylog commented: I'm (thumbsup). Add Comment Puppet / PUP-1781 PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo h2. Issue/master/pup 876 redhat 6 upstart * Author: Adrien Thebo git...@somethingsinistral.net> * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392] * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files] h2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1784) Unable to remove Cron environment
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1784 Unable to remove Cron environment Change By: Charlie Sharpsteen Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1784) Unable to remove Cron environment
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1784
Unable to remove Cron environment
According to the validation code, this should be supported by setting the environment property to absent:
cron { 'test':
command => '/bin/echo',
environment => absent,
}
Thanks for reporting this issue!
However, there are two issues that prevent this from working correctly:
environment has no munge method to convert the string "absent" into the symbol :absent that the rest of the type/provider code watches for when making decisions about environments.
The methods around should for the environment property needs to be extended such that :absent is returned as a singleton value — as this is what the rest of the code is expecting.
Change By:
Charlie Sharpsteen
Affects Version/s:
3.4.2
Affects Version/s:
3.4.3
Labels:
cron environmen environment
Add Comment
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Issues on CentOS 5 with selinux: [root@centos-5 yum.repos.d]# facter Could not retrieve fact='selinux', resolution='': no block given Could not retrieve fact='selinux', resolution='': no block given Could not retrieve fact='selinux', resolution='': no block given Could not retrieve fact='selinux', resolution='': no block given Could not retrieve fact='selinux', resolution='': no block given Could not retrieve fact='selinux', resolution='': no block given architecture => i386 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_hda_size => 4294965248 blockdevice_hdc_size => 4294965248 blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevices => hda,hdc,sda boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 facterversion => 2.0.1-rc1 filesystems => ext2,ext3,iso9660 hardwareisa => i686 hardwaremodel => i686 hostname => centos-5 id => root interfaces => eth0,eth1,lo,sit0 ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.132 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.18-348.el5 kernelversion => 2.6.18 lsbdistcodename => lsbdistdescription => lsbdistid => lsbdistrelease => lsbmajdistrelease => lsbrelease => macaddress => 08:00:27:14:DC:79 macaddress_eth0 => 08:00:27:14:DC:79 macaddress_eth1 => 08:00:27:27:37:41 manufacturer => innotek GmbH memoryfree => 296.32 MB memoryfree_mb => 296.32 memorysize => 375.80 MB memorysize_mb => 375.80 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 mtu_sit0 => 1480 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => CentOS operatingsystemmajrelease => 5 operatingsystemrelease => 5.9 osfamily => RedHat path => /usr/kerberos/sbin:/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/vagrant/bin:/root/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.5 serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBAKKhiPVK4t/rviwOHlRJglVybmwqmX710PsNh0/GjSj1Xl7i9WXBAUSyH01gTF70cmYDVlBsYK97n+yH4tBysavWJCweSYsCmoWAoIAnAxy0PkxfnvbdC8r1r7TIjqzYDctBFJlxDQJJbxP3pzPbiwoFQMuWYPg4ecWJCbAK1N2xFQChUyFqqu5EmmExX96rJSygMyDAtQAAAIEAliPF89Nmc10RGr8JMSPfiudEYJqkNRyWtEFXuS/7N9F8AWT4pWBQ0O/Tv5c6xPPFXoLaa/yl9Ht5v2ojmjhFyZzkgZt8BTKkd8PMUIDrTZteHGNC+p+XlWJsdVx1qmWAziqPx2ZqEQI7J5tmEc/qtpESO4GXPYbNlsCFpa/yy8gAAACAUCFlM7PurckeAee02QvJdxpDt/Za6AsHjn5IPwHLcujbFs0gD/fzjahTeVemv5upXqqVzqScbDkCTUyHlsjlYjWQZo9J+Vm0r81D6SxpGoseX3LoZmzllkWFVa2Oa/V9XqhxNcIbc3k065nXGwII5AxGQu5RZcmcqmwEL4oo5f4= sshfp_dsa => SSHFP 2 1 d1efc678ce197de277448223eece233ddab1af2c SSHFP 2 2 3f0a524896a8321895ca0e2d720081b407f42215d1784132502c9cdd8067fc22 sshfp_rsa => SSHFP 1 1 64ad22ccadfe518d06e9ed5ddcc99b958b153c8d SSHFP 1 2 7de57c080e5ff6e0686283e5894fd9c11b85eea68d3ce0c359d64121d2a072ad sshrsakey => B3NzaC1yc2EBIwAAAQEAnIJGJqJJbLnH7Lo4vNsRzasgyHOTeEfQPn7hdCq8RLt/R239VQe/P/82F2o0VWC5JgxzqsJjSFU/jzeP/ZA8UTSM8VXtwy7dwxdwp5XcAQfOthX8BParoEgKYoZ5DPs7B7ytiO91Em5euTT2L8Xz1Sum6HPTft4BxqJ4FD1VIOKwwMb6+gLT2gsbrDKx+IYyu9iJtbrm145q+3iLGPMFXdf+sdYb5nCu1E61R7dKyk5P/wqkco8ttxar3sTDqhZhvEsjF/Q216DpNzzmF139e+l0VotCd0dyepJBPXp0m/2qpNilNx8blSQ1d8Wkh+7O4HlxoiElDBkj+WrFuHJiFw== swapfree => 1.03 GB swapfree_mb => 1055.99 swapsize => 1.03 GB swapsize_mb => 1055.99 timezone => PST type => Other uniqueid => 007f0101
Jira (FACT-308) Smoke test packages
Title: Message Title
Adrien Thebo commented on an issue
Re: Smoke test packages
Given this:
$x = ""
if $x {
notice "empty is true"
} else {
notice "empty is false"
}
Notice: Scope(Class[main]): empty is false
I don't think this is mega critical.
Add Comment
Facter / FACT-308
Smoke test packages
Procedure may vary by project and point in the release cycle. Ask around.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Ubuntu 10.04 x86_64: architecture => amd64 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 domain => 04-x64 facterversion => 2.0.1-rc1 filesystems => ext2,ext3,ext4 fqdn => ubuntu-10.04-x64 hardwareisa => unknown hardwaremodel => x86_64 hostname => ubuntu-10 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.134 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.32-46-server kernelversion => 2.6.32 lsbdistcodename => lucid lsbdistdescription => Ubuntu 10.04.4 LTS lsbdistid => Ubuntu lsbdistrelease => 10.04 lsbmajdistrelease => 10 lsbrelease => macaddress => 08:00:27:35:10:7d macaddress_eth0 => 08:00:27:35:10:7d macaddress_eth1 => 08:00:27:1c:c3:88 manufacturer => innotek GmbH memoryfree => 313.37 MB memoryfree_mb => 313.37 memorysize => 367.41 MB memorysize_mb => 367.41 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => Ubuntu operatingsystemrelease => 10.04 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/local/lib/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBALgXGkqVE6srvj0+++yhW6jn5mFqiK65SPHOpVok5VKwb2Xh61QshNRa/E5JVkc3PrM81tQwHxseLWWgLO0jhWsrQk6fW5PFid4SBgRxumuC4Eb2wjCtQkBXtCDO/YmhN5dC1Y1s3hmVMci4gISqI8aMsiMz1VPldQJC9DTTwNGLFQCIintMfOw0Uk+Zovzyd6fzhcQn5wAAAIAGgIjtHoj6czvnC9pdSI18lr3PJj89GsEK/FGkAEcl8UaaI+pjElw60DVVOgBiDbigZFEzyntxTRvsjdLM7gGuLc7TEKNcrozrcScJ8CSSCYIc4cty3/4TBMjbDD8ra5bsbAl9Jts6fTnD/pPiQf95H4cfCpp19+XQ5fQzBAQcfgAAAIBMRqT6jZwsaIextRhm2Ezt2hrPPd4n8MpERHrItXsn5GiAbNXMf62Rhb76JQy/DzT0uSJDweUC4cazaRSUNDgxJjvX0xXuFv49Sf0yiibFYzmnJCvzISe+9AZe2eBWvm5sMKwzxz1cydyPUV8svvG79CapZlnWIPRrntKgDAOUtA== sshfp_dsa => SSHFP 2 1 356ca8ba949767942789cd6141c20244bfcbef70 SSHFP 2 2 ea0724f96bbf52c15d806ca3759e3cbc346bc9db0363d0cac700261c4bbfc03c sshfp_rsa => SSHFP 1 1 34e00d0846b32174b75c7f0b91443c4cc6e5604f SSHFP 1 2 9293219b21656b6647a7fdf19bf61aebe591b3c153b16017e69c440f7b885443 sshrsakey => B3NzaC1yc2EBIwAAAQEA0b1qlpz3m+Ul39u+sgzIdiQErIP7SOe6lr/FTKQyrGQMVaJq5uFx/OSQrLp4OPa62whDdqOW5HoLlHde4L2UclRHiz/PIMVi9b7h8MzysTlhZxu41GZLqwsmfHs0imILrSDOxDtbM0EhZfaQ/49r6QgMwiktTbOqUiQd1A4/Uu48Bfpkk1dRLKxZ/GyZxnVfGtIJrXsR1yfPkFYfkOiVwxG8ws85OjOPJPGI/Crug9Z9YDHEMWYmjMaMdTiybsb6DMITpMGXQjV1cDAQdaTDjhkdrj0OmeK25JRo40xe2M2c1X/uKhZLBTAtUmibLdTr0tXfGSwhREi5+r4tXpo8ZQ== swapfree => 471.99 MB swapfree_mb => 471.99 swapsize => 471.99 MB swapsize_mb => 471.99 timezone => CET type => Other uniqueid => 007f0101 uptime => 0:01 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 75 uuid => 582AB91D-6DBF-4E9F-83C3-2F8902B03544 virtual => virtualbox vlans => vlans and lsb facts
Jira (PDB-24) Support for Puppet Environments
Title: Message Title Deepak Giridharagopal commented on an issue Re: Support for Puppet Environments See PDB-47 for the epic encapsulating this work. Add Comment PuppetDB / PDB-24 Support for Puppet Environments PuppetDB doesn't currently have any support for Puppet "environments". It needs to. :) I expect that this won't be tremendously difficult on the storage side of things (although it may conceivably require changes to puppet itself to make sure the environment name is exposed to the fact & catalog termini, and to the report processor, if it's not alrea... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-24) Support for Puppet Environments
Title: Message Title Deepak Giridharagopal updated an issue PuppetDB / PDB-24 Support for Puppet Environments Change By: Deepak Giridharagopal Story Points: 13 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages CentOS 6 i386: [root@centos-6 yum.repos.d]# facter architecture => i386 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 facterversion => 2.0.1-rc1 filesystems => ext4,iso9660 hardwareisa => i686 hardwaremodel => i686 hostname => centos-6 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.132 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.32-358.el6.i686 kernelversion => 2.6.32 lsbdistcodename => lsbdistdescription => lsbdistid => lsbdistrelease => lsbmajdistrelease => lsbrelease => macaddress => 08:00:27:5A:A7:BF macaddress_eth0 => 08:00:27:5A:A7:BF macaddress_eth1 => 08:00:27:91:1A:F4 manufacturer => innotek GmbH memoryfree => 431.60 MB memoryfree_mb => 431.60 memorysize => 467.01 MB memorysize_mb => 467.01 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => CentOS operatingsystemmajrelease => 6 operatingsystemrelease => 6.4 osfamily => RedHat path => /usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.7 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBANMQ3RN4DipyndspoCfX/Tyf5f1jMk6ChGnw7cpElrgZEa/qL1jZXCjTY7uJ9fkYW5vmWZniL9GkDSpypBYslycK92FczGDx61UVGF6QNYvaMpRoYyfruBBrR3kVaje89vzr2/JH18IlyfaOwFo/rHawGQfnknyavxIMPQyD+cdlFQCihVec1bguOTV1CX8rNvvyuDQRkQAAAIBdGVvpqueZoBnOGnz19EAbytgB0indR1+r0As5YIDfXprw4YAze+4UGAXEWDjRFzImwawSe4BrDDXxUYY3+MBK8cwxuLSwal5hropJy2V5kPL1vqnEYIJHcIU0fvas+cPdqikem+hMDib3+NgcqdfKCuHgdMvmWtVmVvaaTrTGBQAAAIBu5t0ZSw/bGSc/DFOGHU93eabaikilsMgx6sln31gnwQhgK/E7y2FV8MmWVv1t+Hnt6jOAaz61XxKxVzsmnSfIkJkeQ+K5aD4GUcCU2STj61rFOl4JPk3VBTjVnAryY/cw6xL2moWnDtBZdiHgz2TBZpQjQewW2cCKwt8aWYEYqw== sshfp_dsa => SSHFP 2 1 281581c44145ee674cc68ac8ca1298b3894e04bc SSHFP 2 2 7044190f754885c3874726cdb81e22f781a124bd151d253f1a95cb540d35d7f8 sshfp_rsa => SSHFP 1 1 98adf757db1b7e6e8b82e13f682dba1190c2787f SSHFP 1 2 60f8106db3c69cb0a1b18193f46009b32cc54f03dfc234ff30929377457d20e2 sshrsakey => B3NzaC1yc2EBIwAAAQEAyMga7AhTA85iE2s2ZbWHwHdCtOiduxt7HYJsyNTyAfTtTOaF4Xu5cr15fnm0D1KbyWhTRy2E+/91Q1awmfibVPyRh7tLeQ/ICOyloKFg/ca1bAEmoX9v/GCHT3zB0WE0CGwO3mCLwffJZXXkCXGnopRLtqG1zOedZFSQhd3GKpGxDW5jkfsZeiqUKjv0m695bh1Yog06pLZCv0WlelvwZBd+TW7CG4PRxYh1NroYWe0WQRevpECW2BOFeccHJo/UfF2qWff7BLd5+7/6h+aGsiF4ChOkAq3yihoHggE4cjmQemN59CbPYXCLxzW9IlXVQ/HS3QVe8USTmJNJRRjsNw== swapfree => 959.99 MB swapfree_mb => 959.99 swapsize => 959.99 MB swapsize_mb => 959.99 timezone => UTC type => Other uniqueid => 007f0101 uptime => 0:02 hours uptime_days => 0 uptime_hours => 0 uptime_seconds => 165 uuid => 0B74D5B7-FF01-4B5F-96C6-3A61D84E9E27 virtual => virtualbox vlans =>
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 7 i386: root@debian-7:~# facter architecture => i386 bios_release_date => 12/01/2006 bios_vendor => innotek GmbH bios_version => VirtualBox blockdevice_sda_model => VBOX HARDDISK blockdevice_sda_size => 10632560640 blockdevice_sda_vendor => ATA blockdevice_sr0_model => CD-ROM blockdevice_sr0_size => 1073741312 blockdevice_sr0_vendor => VBOX blockdevice_sr1_model => CD-ROM blockdevice_sr1_size => 1073741312 blockdevice_sr1_vendor => VBOX blockdevices => sda,sr0,sr1 boardmanufacturer => Oracle Corporation boardproductname => VirtualBox boardserialnumber => 0 facterversion => 2.0.1-rc1 filesystems => ext2,ext3 hardwareisa => unknown hardwaremodel => i686 hostname => debian-7 id => root interfaces => eth0,eth1,lo ipaddress => 10.0.2.15 ipaddress_eth0 => 10.0.2.15 ipaddress_eth1 => 10.20.1.133 ipaddress_lo => 127.0.0.1 is_virtual => true kernel => Linux kernelmajversion => 3.2 kernelrelease => 3.2.0-4-686-pae kernelversion => 3.2.0 lsbdistcodename => wheezy lsbdistdescription => Debian GNU/Linux 7.0 (wheezy) lsbdistid => Debian lsbdistrelease => 7.0 lsbmajdistrelease => 7 lsbrelease => macaddress => 08:00:27:7c:ea:12 macaddress_eth0 => 08:00:27:7c:ea:12 macaddress_eth1 => 08:00:27:b5:0b:ce manufacturer => innotek GmbH memoryfree => 341.29 MB memoryfree_mb => 341.29 memorysize => 375.34 MB memorysize_mb => 375.34 mtu_eth0 => 1500 mtu_eth1 => 1500 mtu_lo => 16436 netmask => 255.255.255.0 netmask_eth0 => 255.255.255.0 netmask_eth1 => 255.255.255.0 netmask_lo => 255.0.0.0 network_eth0 => 10.0.2.0 network_eth1 => 10.20.1.0 network_lo => 127.0.0.0 operatingsystem => Debian operatingsystemmajrelease => 7 operatingsystemrelease => 7.0 osfamily => Debian path => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin physicalprocessorcount => 1 processor0 => Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount => 1 productname => VirtualBox ps => ps -ef rubysitedir => /usr/local/lib/site_ruby/1.9.1 rubyversion => 1.9.3 selinux => false serialnumber => 0 sshdsakey => B3NzaC1kc3MAAACBAI2OsI8BNQK2qMDbuVZjiPRlIjh5I5DZWcV2Z05bS8Q+ni5GD/ZDa1SANaQecrNVo6y3RIpL8Uo7Prhl8mR8+uWh+kvGRPu0lhTpWhptiiAeqti0ch9WmhD+tjVczrAV6m3Tt7xiYN3Nq0e4sVHmZi0GWqT6bxEWTC0ZAm5WoJQRFQCJrPr3aIOQDABg/wbQOfZ4eZlziwAAAIAOgpGUgAWBjeT/KfHHNvB8leBlcMemWccx9VaUE32+5olWe4apPbZXKqyEnNvR9dgoK7r5HlgbKqnP4u0PYV+PS47uEMy7IwVB+b2c3kWc3AiBryeWMxb4uQLvYvpxu4/mVkIWix0G8xgo6DnueMks6OF03Tw5zzKkO0QmPE6IHgAAAIAeIjtBDcckLCRlNrQ36VwpJvUYd+zVe/4FsMecU6FN6J8wQ61MCnNbwB2UGVqNcR0AWSMCeJwYosSTMkEWeBV+/cs4yWteAee/slGBudC+HJxMYBHvbfjNSwJs9m/Z1WS517Lf8tWaSwbfFahdrVTWxYpLfAZt2QzxFKGpLESEKw== sshecdsakey => E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBJgtJl/IlHw74EqnSFT2xQRMZv2SHUogpIXN96GxxHfsx2x4TuZPHNrmmccp9u2MW3kpcWZzjLT552WPOiiQEW8= sshfp_dsa => SSHFP 2 1 204b51330d83ec15c3ed522692ac10f70a7c072f SSHFP 2 2 0920fe3e886fa5703969635615e117ebdaed21624d3d402956161337b722ed33 sshfp_ecdsa => SSHFP 3 1 2a365770ea6fd069c3c1f8b0b4b86c88b6b6b92a SSHFP 3 2 9a1dc83a76acef199fb765f24b194aecb8f6fc00e1ab7075d1562e119bed49b3 sshfp_rsa => SSHFP 1 1 6b2284770b39a525d6021b4a2b30e332762f115d SSHFP 1 2 26e33eabe0e8bcfdb538a99b9fba436fece8324f6a1e9f807c4d2a6bbd0e3da0 sshrsakey => B3NzaC1yc2EDAQABAAABAQCpRpNCshDHQoTYCv0azEdzpPoVVNqb44WJKtqs8WY75p+bp7hdmWRhKLN1a/ySsb1iObBTMO/w5wkBRg6UNUhfdsdYs4dg/hhjQGLRT9aXSNCCkDkgdSKO6PtRo+5WiMxIjnw2J4g9FLKh/M5rR+J58Mqd7jYGCdqUwhYw6ymfNk+B64mdd/CS9H/WqSpNl9eSLPUjteKgcMdm+o8V9u0iIC55/7eC6HSbJ824hNSv0JHaN3TFohbGddKAkFhZSS1igh3iKHGtXEwzrRkUYRdvTdEGKJgJiWvQylL/dDyc7qI5//h1uY2sU454KaEHJmq4FI5DJNCLEXTJwsVx9nTf swapfree => 456.00 MB swapfree_mb => 456.00 swapsize => 456.00 MB swapsize_mb => 456.00 timezone => UTC type => Other uniqueid => 007f0101 uptime => 0:10 hours u
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Joshua Cooper The [build process ]( | https://github.com/puppetlabs/puppet_for_the_win ) ] needs to be able to package x86 and x64 versions of ruby with the appropriate set of gems (some containing native code), which is then packaged up into two puppet MSI installers. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby Change By: Joshua Cooper Story Points: 5 6 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-835) FFI native windows code
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-835 FFI native windows code Change By: Joshua Cooper Story Points: 5 10 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-391) Update native windows code to support x64
Title: Message Title Joshua Cooper commented on an issue Re: Update native windows code to support x64 Most of this should be handled by the FFI conversion. But there may be some additional cases where do we do things like 0.chr * 4 or ' ' * 4 Add Comment Puppet / PUP-391 Update native windows code to support x64 Puppet makes some x86 assumptions in win32 native code. It needs to be able to support x64. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Joshua Cooper 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/groups/opt_out.
Jira (PUP-839) FFI Puppet::Util::Windows::Security module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-839 FFI Puppet::Util::Windows::Security module Change By: Joshua Cooper Story Points: 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/groups/opt_out.
Jira (PUP-840) FFI Puppet::Util::Colors module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-840 FFI Puppet::Util::Colors module Change By: Joshua Cooper 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/groups/opt_out.
Jira (PUP-837) FFI Puppet::Util::Windows::SID module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-837 FFI Puppet::Util::Windows::SID module Change By: Joshua Cooper 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/groups/opt_out.
Jira (PUP-840) FFI Puppet::Util::Colors module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-840 FFI Puppet::Util::Colors module Change By: Joshua Cooper Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-836) FFI Puppet::Util::Windows::User module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-836 FFI Puppet::Util::Windows::User module Change By: Joshua Cooper 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/groups/opt_out.
Jira (PUP-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Joshua Cooper commented on an issue Re: FFI Puppet::Util::Windows::Process module Some of this was done in 1320519c and 1320519c though some more work is required. Add Comment Puppet / PUP-838 FFI Puppet::Util::Windows::Process module This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-469) Anonymize should support facts
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-469 Anonymize should support facts Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-308) Smoke test packages
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-308 Smoke test packages Change By: Adrien Thebo Assignee: Kylo Ginsberg Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. Change By: Zachary Stern Labels: customer redmine support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-560) Yum provider handles errors while processing a batch
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-560 Yum provider handles errors while processing a batch Change By: Kylo Ginsberg Story Points: 2 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/groups/opt_out.
Jira (PUP-556) Define report schema change for batch processing
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-556 Define report schema change for batch processing Change By: Kylo Ginsberg Story Points: 1 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/groups/opt_out.
Jira (PUP-1781) PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo adrienthebo commented: Updated comment in confiner.rb and improved messages. How much do we want to fix up how confines emit messages in this PR? Add Comment Puppet / PUP-1781 PR (2392): Issue/master/pup 876 redhat 6 upstart - adrienthebo h2. Issue/master/pup 876 redhat 6 upstart * Author: Adrien Thebo git...@somethingsinistral.net> * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 2392 Discussion|https://github.com/puppetlabs/puppet/pull/2392] * [Pull Request 2392 File Diff|https://github.com/puppetlabs/puppet/pull/2392/files] h2 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
Jira (PUP-146) Install multiple packages with one call to the underlying package manager
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-146 Install multiple packages with one call to the underlying package manager Change By: Kylo Ginsberg Story Points: 8 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-234) Add Facts showing the UUID of partitions
Title: Message Title Adrien Thebo commented on an issue Re: Add Facts showing the UUID of partitions This had to be reverted (3c3ef4cfec2dd7b57aa17ad29f9cb602ab617e96) for the 2.0 release, I'm retargeting this at 2.1. Add Comment Facter / FACT-234 Add Facts showing the UUID of partitions Add facts 'blockdevice__uuid' that show the partitions UUID. It ignores swap and iso9660 (CD/DVD devices). PR: https://github.com/puppetlabs/facter/pull/560 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-339) Pull in backwards incompatible fact changes for Facter 2
Title: Message Title Adrien Thebo commented on an issue Re: Pull in backwards incompatible fact changes for Facter 2 Merged in d0f5c3c. Add Comment Facter / FACT-339 Pull in backwards incompatible fact changes for Facter 2 A number of facts in master have backwards incompatible changes that we would like to release in Facter 2. We need to backport those changes onto the Facter 2 branch so that we can unleash^Wrelease those changes in accordance with SemVer. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-93) Facter Solaris is outputting to stderr
Title: Message Title Adrien Thebo assigned an issue to Unassigned Facter / FACT-93 Facter Solaris is outputting to stderr Change By: Adrien Thebo Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-93) Facter Solaris is outputting to stderr
Title: Message Title Adrien Thebo updated an issue Facter / FACT-93 Facter Solaris is outputting to stderr Change By: Adrien Thebo Fix Version/s: 2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-93) Facter Solaris is outputting to stderr
Title: Message Title Adrien Thebo commented on an issue Re: Facter Solaris is outputting to stderr This was targeted at 2.0 but only affected and was released into master, I'm untargeting it. Add Comment Facter / FACT-93 Facter Solaris is outputting to stderr Also note that we're disabling the Facter Acceptance solaris job pending resolution of this issue. So please re-enable that job as part of fixing this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-132) Backport non-behavioral changes from Facter master to Facter stable
Title: Message Title Adrien Thebo commented on an issue Re: Backport non-behavioral changes from Facter master to Facter stable Merged into facter-2 in 786b406. Add Comment Facter / FACT-132 Backport non-behavioral changes from Facter master to Facter stable Facter master and Facter stable diverged about a year ago and there's a pretty healthy diff between the two, with about 200 commits that are in master and not in stable. There are a number of changes in master like documentation commits and spec improvements that could be backported to stable. Performing these backports will make it easier to determine wh... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-154) PR (574): Backport non-functional changes from master to facter-2 - adrienthebo
Title: Message Title Adrien Thebo commented on an issue Re: PR (574): Backport non-functional changes from master to facter-2 - adrienthebo Merged into facter-2 in 786b406. Add Comment Facter / FACT-154 PR (574): Backport non-functional changes from master to facter-2 - adrienthebo h2. Backport non-functional changes from master to facter-2 * Author: Adrien Thebo git...@somethingsinistral.net> * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 574 Discussion|https://github.com/puppetlabs/facter/pull/574] * [Pull Request 574 File Diff|https://github.com/puppetlabs/facter/pull/5... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-178) PR (588): (doc) Update to point to the new Jira instance - zaphod42
Title: Message Title Adrien Thebo commented on an issue Re: PR (588): (doc) Update to point to the new Jira instance - zaphod42 Merged in 9629eda. Add Comment Facter / FACT-178 PR (588): (doc) Update to point to the new Jira instance - zaphod42 h2. (doc) Update to point to the new Jira instance * Author: Andrew Parker <> * Company: Puppet Labs * Github ID: [zaphod42|https://github.com/zaphod42] * [Pull Request 588 Discussion|https://github.com/puppetlabs/facter/pull/588] * [Pull Request 588 File Diff|https://github.com/puppetlabs/facter/pull/588/files] h2. Pull Request Description W... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-161) PR (577): Facter 2 output formatting - adrienthebo
Title: Message Title Adrien Thebo commented on an issue Re: PR (577): Facter 2 output formatting - adrienthebo Merged in 65eba06. Add Comment Facter / FACT-161 PR (577): Facter 2 output formatting - adrienthebo h2. Facter 2 output formatting * Author: Adrien Thebo git...@somethingsinistral.net> * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 577 Discussion|https://github.com/puppetlabs/facter/pull/577] * [Pull Request 577 File Diff|https://github.com/puppetlabs/facter/pull/577/files] h2. Pull Request D... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
