Jira (PUP-1477) provider command throws exception on unicode
Title: Message Title
cristi falcas created an issue
Puppet / PUP-1477
provider command throws exception on unicode
Issue Type:
Bug
Affects Versions:
3.4.1
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
21/Jan/14 2:50 AM
Priority:
Normal
Reporter:
cristi falcas
I have a provider for pbis configuration (linux and ad integration) and a command for '/opt/pbis/bin/config':
commands :pbis_config = '/opt/pbis/bin/config'
which I use it like so:
output = pbis_config(setting, value)
Sometimes the command from pbis returns a string that has a unicode character inside (a zero-width space). If this happens an exception is thrown with the following message:
Debug: Executing '/opt/pbis/bin/config --show LoginShellTemplate' Debug: Joindomain[join_domain](provider=pbis): Execution of '/opt/pbis/bin/config --show LoginShellTemplate' returned 1: Error: Out of memory
I tested the output of the command from the console and used perl to decode the strings:
perl -e 'print sprintf(x {%x}
, $_) foreach (unpack(C*, /bin/bash));print\n' \x {2f}\x{62}\x{69}\x{6e}\x{2f}
\x {62}
Jira (PUP-1477) provider command throws exception on unicode
Title: Message Title
cristi falcas updated an issue
Puppet / PUP-1477
provider command throws exception on unicode
Change By:
cristi falcas
Ihaveaproviderforpbisconfiguration(linuxandadintegration)andacommandfor'/opt/pbis/bin/config':commands:pbis_config='/opt/pbis/bin/config'whichIuseitlikeso:output=pbis_config(setting,value)Sometimesthecommandfrompbisreturnsastringthathasaunicodecharacterinside(azero-widthspace).Ifthishappensanexceptionisthrownwiththefollowingmessage:Debug:Executing'/opt/pbis/bin/config--showLoginShellTemplate'Debug:Joindomain[join_domain](provider=pbis):Executionof'/opt/pbis/bin/config--showLoginShellTemplate'returned1:Error:OutofmemoryItestedtheoutputofthecommandfromtheconsoleandusedperltodecodethestrings: perl-e'printsprintf(\\x{%x},$_)foreach(unpack(C*,/bin/bash));print\n'\x{2f}\x{62}\x{69}\x{6e}\x{2f}\x{62}\x{61}\x{73}\x{68}\x{e2}\x{80}\x{8b}Thelast3bytesaretheunicodecharactersforzero-widthspace.
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-1477) provider command throws exception on unicode
Title: Message Title
cristi falcas updated an issue
Puppet / PUP-1477
provider command throws exception on unicode
Change By:
cristi falcas
Ihaveaproviderforpbisconfiguration(linuxandadintegration)andacommandfor'/opt/pbis/bin/config':commands:pbis_config='/opt/pbis/bin/config'whichIuseitlikeso:output=pbis_config(setting,value)Sometimesthecommandfrompbisreturnsastringthathasaunicodecharacterinside(azero-widthspace).Ifthishappensanexceptionisthrownwiththefollowingmessage:Debug:Executing'/opt/pbis/bin/config--showLoginShellTemplate'Debug:Joindomain[join_domain](provider=pbis):Executionof'/opt/pbis/bin/config--showLoginShellTemplate'returned1:Error:OutofmemoryItestedtheoutputofthecommandfromtheconsoleandusedperltodecodethestrings:perl-e'printsprintf(\\x{%x},$_)foreach(unpack(C*,/bin/bash));print\n'\x{2f}\x{62}\x{69}\x{6e}\x{2f}\x{62}\x{61}\x{73}\x{68}\x{e2}\x{80}\x{8b}Thelast3bytesaretheunicodecharactersforzero-widthspace.
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-1477) provider command throws exception on unicode
Title: Message Title
cristi falcas updated an issue
Puppet / PUP-1477
provider command throws exception on unicode
Change By:
cristi falcas
Ihaveaproviderforpbisconfiguration(linuxandadintegration)andacommandfor'/opt/pbis/bin/config':commands:pbis_config='/opt/pbis/bin/config'whichIuseitlikeso:output=pbis_config(setting,value)Sometimesthecommandfrompbisreturnsastringthathasaunicodecharacterinside(azero-widthspace).Ifthishappensanexceptionisthrownwiththefollowingmessage: {noformat} Debug:Executing'/opt/pbis/bin/config--showLoginShellTemplate'Debug:Joindomain[join_domain](provider=pbis):Executionof'/opt/pbis/bin/config--showLoginShellTemplate'returned1:Error:Outofmemory {noformat} Itestedtheoutputofthecommandfromtheconsoleandusedperltodecodethestrings: {noformat} perl-e'printsprintf(\\x{%x},$_)foreach(unpack(C*,/bin/bash));print\n'\x{2f}\x{62}\x{69}\x{6e}\x{2f}\x{62}\x{61}\x{73}\x{68}\x{e2}\x{80}\x{8b} {noformat} Thelast3bytesaretheunicodecharactersforzero-widthspace.
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-1477) provider command throws exception on unicode
Title: Message Title
cristi falcas updated an issue
Puppet / PUP-1477
provider command throws exception on unicode
Change By:
cristi falcas
Ihaveaproviderforpbisconfiguration(linuxandadintegration)andacommandfor'/opt/pbis/bin/config':commands:pbis_config='/opt/pbis/bin/config'whichIuseitlikeso:output=pbis_config(setting,value)Sometimesthecommandfrompbisreturnsastringthathasaunicodecharacterinside(azero-widthspace).Ifthishappensanexceptionisthrownwiththefollowingmessage:{noformat}Debug:Executing'/opt/pbis/bin/config--showLoginShellTemplate'Debug:Joindomain[join_domain](provider=pbis):Executionof'/opt/pbis/bin/config--showLoginShellTemplate'returned1:Error:Outofmemory{noformat}Itestedtheoutputofthecommandfromtheconsoleandusedperltodecodethestrings:{noformat}perl-e'printsprintf(\\x{%x},$_)foreach(unpack(C*,/bin/bash));print\n'\x{2f}\x{62}\x{69}\x{6e}\x{2f}\x{62}\x{61}\x{73}\x{68}\x{e2}\x{80}\x{8b}{noformat}Thelast3bytesaretheunicodecharactersforzero-widthspace. Fulloutputofthecommand:{noformat}/opt/pbis/bin/config--showLoginShellTemplatestring/bin/bashlocalpolicy{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-1478) PR (2279): Fix serialization of TagSet - dalen
Title: Message Title gepetto-bot created an issue Puppet / PUP-1478 PR (2279): Fix serialization of TagSet - dalen Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 21/Jan/14 4:43 AM Labels: github Priority: Normal Reporter: gepetto-bot Fix serialization of TagSet Author: Erik Daln erik.gustav.da...@gmail.com Company: Spotify Github ID: dalen Pull Request 2279 Discussion Pull Request 2279 File Diff Pull Request Description The TagSet class didn't include FormatSupport and didn't have a
Jira (PUP-1478) PR (2279): Fix serialization of TagSet - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2279): Fix serialization of TagSet - dalen puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1478 PR (2279): Fix serialization of TagSet - dalen h2. Fix serialization of TagSet * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2279 Discussion|https://github.com/puppetlabs/puppet/pull/2279] * [Pull Request 2279 File Diff|https://github.com/puppetlabs/puppet/pull/2279/files] h2. Pull Request Description Th... 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-1468) PR (2275): Making sure you can use `making_sure` instead of `ensure` - MaxMartinPDX
Title: Message Title gepetto-bot commented on an issue Re: PR (2275): Making sure you can use `making_sure` instead of `ensure` - MaxMartinPDX Pull request Making sure you can use `making_sure` instead of `ensure` has been closed. Add Comment Puppet / PUP-1468 PR (2275): Making sure you can use `making_sure` instead of `ensure` - MaxMartinPDX h2. Making sure you can use `making_sure` instead of `ensure` * Author: Max Martin PDX * Company: * Github ID: [MaxMartinPDX|https://github.com/MaxMartinPDX] * [Pull Request 2275 Discussion|https://github.com/puppetlabs/puppet/pull/2275] * [Pull Request 2275 File Diff|https://github.com/puppetlabs/puppet/pull/2275/files] h2. Pull Request Descri... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (FACT-236) Facter RPM should not require virt-what
Title: Message Title Glenn created an issue Facter / FACT-236 Facter RPM should not require virt-what Issue Type: Bug Assignee: Eric Sorenson Created: 21/Jan/14 6:16 AM Fix Versions: 1.7.4 Priority: Normal Reporter: Glenn There is a bug in virt-what that causes facter to behave incorrectly. https://bugzilla.redhat.com/show_bug.cgi?id=973663 http://projects.puppetlabs.com/issues/7559#note-71 I'm currently in the process of updating my automation to install facter (and thus puppet) as gems instead of RPM's due to the fact that the RPM (after v1.6.10) requires the virt-what package which causes the bug mentioned here to manifest. When this bug manifests, facter does not resolve ec2 facts. http://projects.puppetlabs.com/issues/7559#note-70 It appears that there is no 'hard' requirement on the virt-what package as facter appears (to me) to behave correctly without this package installed. Please remove the dependency so that we can continue to use RPM's for package installation. Add Comment
Jira (PUP-1479) resources using parsedfile providers quietly move resources from default file to target with 'puppet resource'
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1479
resources using parsedfile providers quietly move resources from default file to target with 'puppet resource'
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
21/Jan/14 6:40 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
use the host resource and puppet resource:
I expect the following to fail:
pre
puppet resource host test1 ensure=present target=/tmp/host host_aliases=alias1 notice: /Host[test1]/ensure: created err: /Host[test1]: Could not evaluate: ip is a required attribute for hosts host { 'test1': host_aliases = ['alias1'], target = '/tmp/host', ensure = 'present' }
/pre
If there is already an entry for this host in /etc/hosts (the default target), puppet will use the ip address of that host and move it to the new target location.
pre
echo '127.0.0.2 test1' /etc/hosts [root@puppet2 puppet_spec]# puppet resource host test1 ensure=present target=/tmp/host host_aliases=alias1 notice: /Host[test1]/host_aliases: host_aliases changed '' to 'alias1' notice: /Host[test1]/target: target changed '/etc/hosts' to '/tmp/host' host { 'test1': host_aliases = ['alias1'], target = '/tmp/host', ensure =
Jira (FACT-235) PR (610): Enable fash finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (610): Enable fash finish in Travis - ghoneycutt jhoblitt commented: :+1: Add Comment Facter / FACT-235 PR (610): Enable fash finish in Travis - ghoneycutt h2. Enable fash finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 610 Discussion|https://github.com/puppetlabs/facter/pull/610] * [Pull Request 610 File Diff|https://github.com/puppetlabs/facter/pull/610/files] h2. Pull Request Description -... 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-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 Not exactly sure this is the same as Justin was reporting but I noticed a difference on my Amazon Linux hosts between EC2-Classic and EC2-VPC run server instances that appears to be related to the Facter::Util::EC2.has_ec2_arp? function which attempts to match the ARP entry. On an EC2-Classic the ARP will return and match 'fe:ff:ff:ff:ff:ff' as shown: [root@ip-10-71-144-239 ~]# arp -an ? (10.71.144.193) at fe:ff:ff:ff:ff:ff [ether] on eth0 ? (169.254.169.254) at fe:ff:ff:ff:ff:ff [ether] on eth0 On an EC2-VPC instance the ARP for me returns: [root@ip-10-0-2-166 ~]# arp -an ? (169.254.169.254) at 0e:5e:c5:10:1a:ba [ether] on eth0 ? (10.0.2.1) at 0e:5e:c5:10:1a:ba [ether] on eth0 Furthermore I believe in this case that matching on the ARP is really poor design as EC2-VPC server instances you have a Network Interface configuration giving a unique MAC per interface that are attached to the EC2 instances. By only executing this check based on MAC it ensures that any EC2-VPC server instance does not get the EC2 facts provided when configuration catalog runs are executed. Add Comment Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host `facter|grep ec2` yields only the 'domain' and 'fqdn' facts for me, not a gaggle of them including stuff like 'ec2_profile'. The same versions on another host are working fine. Any tips on troubleshooting? An strace isn't showing anything promising to me, although it confirms that it's firing up the ec2.rb library.
Jira (PDB-305) PR (796): Update supported packages for distros - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (796): Update supported packages for distros - kbarber Pull request Update supported packages for distros has been closed. Add Comment PuppetDB / PDB-305 PR (796): Update supported packages for distros - kbarber h2. Update supported packages for distros * Author: Ken Barber k...@bob.sh * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 796 Discussion|https://github.com/puppetlabs/puppetdb/pull/796] * [Pull Request 796 File Diff|https://github.com/puppetlabs/puppetdb/pull/796/files] h2. Pull Request Description ---... 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-127) Latest docs have broken links
Title: Message Title Kenneth Barber commented on an issue Re: Latest docs have broken links Merged here: https://github.com/puppetlabs/puppetdb/commit/2f9f1a8123abb091478716111a86e8b96e07038c Add Comment PuppetDB / PDB-127 Latest docs have broken links On: http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html#edit-puppetconf It talks about the experimental (they no longer are, afaik) reports, event endpoints. The links also link to latest/api/query/experimental which for 1.5 return 404's 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-1480) put puppet ruby libs in ruby version neutral folder
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-1480 put puppet ruby libs in ruby version neutral folder Issue Type: New Feature Assignee: Eric Sorenson Created: 21/Jan/14 7:41 AM Priority: Normal Reporter: Klavs Klavsen since puppet 3.4.2 should work fine with ruby 1.9 - should libs be put in version neutral folder.. so the few poor slobs, who happen to have a CentOS (or other el6) server that must have /usr/bin/ruby point to ruby 1.9.. can still have a functioning puppet.. in my setup - that would be: /usr/lib64/ruby/site_ruby (vendor_ruby isn't in el6's default search path). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title Brandon created an issue Puppet / PUP-1481 Incorrect PID on first start after installation on Ubuntu Issue Type: Bug Affects Versions: 3.4.2 Assignee: Eric Sorenson Components: Community Created: 21/Jan/14 7:45 AM Environment: Ubuntu 12.04.03 x64 Priority: Normal Reporter: Brandon Puppet's pidfile contains the incorrect PID when you first install the puppetmaster service on Ubuntu. Steps to reproduce: wget http://apt.puppetlabs.com/puppetlabs-release-precise.deb sudo dpkg -i puppetlabs-release-precise.deb sudo apt-get update sudo apt-get install y -o Dpkg::Options::= -force-confold --force-yes puppet puppetmaster The pidfile /var/run/puppet/master.pid does not exist, and the pidfile /var/lib/puppet/run/master.pid contains the incorrect PID.
Jira (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title
Brandon updated an issue
Puppet / PUP-1481
Incorrect PID on first start after installation on Ubuntu
Change By:
Brandon
Puppet'spidfilecontainstheincorrectPIDwhenyoufirstinstallthepuppetmasterserviceonUbuntu.Stepstoreproduce:{code}wgethttp://apt.puppetlabs.com/puppetlabs-release-precise.debsudodpkg-ipuppetlabs-release-precise.debsudoapt-getupdatesudoapt-getinstall-y-oDpkg::Options::=--force-confold--force-yespuppetpuppetmaster{code}Thepidfile {{ /var/run/puppet/master.pid }} doesnotexist,andthepidfile {{ /var/lib/puppet/run/master.pid }} containstheincorrectPID.
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-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title
Brandon updated an issue
Puppet / PUP-1481
Incorrect PID on first start after installation on Ubuntu
Change By:
Brandon
Puppet'spidfilecontainstheincorrectPIDwhenyoufirstinstallthepuppetmasterserviceonUbuntu.Stepstoreproduce: {code} wgethttp://apt.puppetlabs.com/puppetlabs-release-precise.debsudodpkg-ipuppetlabs-release-precise.debsudoapt-getupdatesudoapt-getinstall-y-oDpkg::Options::=--force-confold--force-yespuppetpuppetmaster {code} Thepidfile/var/run/puppet/master.piddoesnotexist,andthepidfile/var/lib/puppet/run/master.pidcontainstheincorrectPID.
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-1482) PR (2280): Fixed a bug in package/package_settings (super called without exlpicit parameter) - ptomulik
Title: Message Title gepetto-bot created an issue Puppet / PUP-1482 PR (2280): Fixed a bug in package/package_settings (super called without exlpicit parameter) - ptomulik Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 21/Jan/14 7:47 AM Labels: github Priority: Normal Reporter: gepetto-bot Fixed a bug in package/package_settings (super called without exlpicit parameter) Author: Paweł Tomulik ptomu...@meil.pw.edu.pl Company: Warsaw University of Technology Github ID: ptomulik Pull Request 2280 Discussion Pull Request 2280 File Diff Pull Request Description
Jira (MCO-3) CLONE - A single malformed fact can break mcollective fact filtering in PE
Title: Message Title John Duarte commented on an issue Re: CLONE - A single malformed fact can break mcollective fact filtering in PE Pieter Loubser yes the spec tests in this PR are sufficient for testing the expectations of the YAML_facts. cc: Kenn Hussey Add Comment MCollective / MCO-3 CLONE - A single malformed fact can break mcollective fact filtering in PE We have a cron job that dumps facter output as a yaml file to /etc/puppetlabs/mcollective/facts.yaml. If this file gets corrupted, or bad yaml is written, or debug output ends up in it, fact filtering no longer works. If a fact is bad or not returning the right parseable output, then not being able to filter by it could be expected. But a single bad / m... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-271) Deprecate JDK 1.6. in docs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-271 Deprecate JDK 1.6. in docs Change By: Kenneth Barber Fix Version/s: 1.5.X Summary: Update DeprecateJDK 1. 5.xand1. 6. x in docs JDK1.6shouldsayit'sdeprecated:https://docs.puppetlabs.com/puppetdb/latest/#nix-server-with-jdk-16 Reportdocsstillsayexperimental:http://docs.puppetlabs.com/puppetdb/1.5/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.5/api/commands.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/commands.html 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-1465) PR (2273): (doc) Updating README.md, LICENSE - highb
Title: Message Title gepetto-bot commented on an issue Re: PR (2273): (doc) Updating README.md, LICENSE - highb highb commented: This is a trivial docs-only update. Add Comment Puppet / PUP-1465 PR (2273): (doc) Updating README.md, LICENSE - highb h2. (doc) Updating README.md, LICENSE * Author: Brandon High * Company: * Github ID: [highb|https://github.com/highb] * [Pull Request 2273 Discussion|https://github.com/puppetlabs/puppet/pull/2273] * [Pull Request 2273 File Diff|https://github.com/puppetlabs/puppet/pull/2273/files] h2. Pull Request Description Fixing link to HTTP API docs... 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-1465) PR (2273): (doc) Updating README.md, LICENSE - highb
Title: Message Title gepetto-bot commented on an issue Re: PR (2273): (doc) Updating README.md, LICENSE - highb Pull request (doc) Updating README.md, LICENSE has been closed. Add Comment Puppet / PUP-1465 PR (2273): (doc) Updating README.md, LICENSE - highb h2. (doc) Updating README.md, LICENSE * Author: Brandon High * Company: * Github ID: [highb|https://github.com/highb] * [Pull Request 2273 Discussion|https://github.com/puppetlabs/puppet/pull/2273] * [Pull Request 2273 File Diff|https://github.com/puppetlabs/puppet/pull/2273/files] h2. Pull Request Description Fixing link to HTTP API docs... 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-1318) Provide a logoutput for service like exec
Title: Message Title Peter Souter assigned an issue to Peter Souter Puppet / PUP-1318 Provide a logoutput for service like exec Change By: Peter Souter Assignee: PeterSouter 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-1318) Provide a logoutput for service like exec
Title: Message Title Peter Souter commented on an issue Re: Provide a logoutput for service like exec Been meaning to fix this for ages (I was having similar weird issues with services failing in puppet but not on the command-line) Basic PR here: https://github.com/puppetlabs/puppet/pull/2281 Add Comment Puppet / PUP-1318 Provide a logoutput for service like exec If I have a service defined that fails, and the service does not log anywhere, it becomes near impossible to troubleshoot the issue. I have this case for memcached, which at least on Centos does not have a way of logging. Even for those services that do have logging, this would be extremely helpful. Example of current output: Sep 6 15:38:18 domU-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-320) Tag the release
Title: Message Title Melissa Stone assigned an issue to Melissa Stone PuppetDB / PDB-320 Tag the release Change By: Melissa Stone Assignee: MelissaStone 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-1483) PR (2282): (FORGE-141) Add Basic Travis file for Module generation - petems
Title: Message Title gepetto-bot created an issue Puppet / PUP-1483 PR (2282): (FORGE-141) Add Basic Travis file for Module generation - petems Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 21/Jan/14 9:53 AM Labels: github Priority: Normal Reporter: gepetto-bot (FORGE-141) Add Basic Travis file for Module generation Author: Peter Souter Company: Github ID: petems Pull Request 2282 Discussion Pull Request 2282 File Diff Pull Request Description Basic Travis file added for module
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Joshua Cooper commented on an issue Re: Puppet REST API always fails if there's at least one broken manifest Merged to pe-puppet/3.2.x in c75488e Add Comment Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Steps to reproduce: 1. Install several puppet modules 2. Make a syntax error in one or more installed manifests 3. Query host/production/resource_types/*?kind=class 4. Query the same url again Expected result: Step #3 and #4 returns the same result, containing parseable all classes *) Actual result: Step #3 fails with an error reporting the ... 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-1465) PR (2273): (doc) Updating README.md, LICENSE - highb
Title: Message Title gepetto-bot commented on an issue Re: PR (2273): (doc) Updating README.md, LICENSE - highb puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1465 PR (2273): (doc) Updating README.md, LICENSE - highb h2. (doc) Updating README.md, LICENSE * Author: Brandon High * Company: * Github ID: [highb|https://github.com/highb] * [Pull Request 2273 Discussion|https://github.com/puppetlabs/puppet/pull/2273] * [Pull Request 2273 File Diff|https://github.com/puppetlabs/puppet/pull/2273/files] h2. Pull Request Description Fixing link to HTTP API docs... 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-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title
Joshua Cooper commented on an issue
Re: Encoding mis-matches cause package prefetching to fail
Merged to pe-puppet/3.2.x in c75488e
Add Comment
Puppet / PUP-736
Encoding mis-matches cause package prefetching to fail
One of our RPM packages has some UTF-8 characters in its description, leading to an exception (Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII) in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error. Priority=High because it breaks file { ensure = latest; }.
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-591) Command for setting config entries in puppet.conf
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-591 Command for setting config entries in puppet.conf Change By: Michelle Johansen Epic Status: Done 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-1211) Puppet Resource Package fails
Title: Message Title
Joshua Cooper commented on an issue
Re: Puppet Resource Package fails
Merged to pe-puppet/3.2.x in c75488e
Add Comment
Puppet / PUP-1211
Puppet Resource Package fails
Trying to get all windows package resources i get the following error {code} ruby 1.9.3p448 (2013-06-27) [i386-mingw32] C:\Windows\system32puppet resource package Error: Could not run: invalid byte sequence in US-ASCII {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1389) Windows File resources generating 0 byte files and not populating file via content or source when title has -
Title: Message Title
Joshua Cooper commented on an issue
Re: Windows File resources generating 0 byte files and not populating file via content or source when title has -
Merged to pe-puppet/3.2.x in c75488e
Add Comment
Puppet / PUP-1389
Windows File resources generating 0 byte files and not populating file via content or source when title has -
Module to reproduce the issue is here: https://github.com/openstack-hyper-v/puppet-jenkins/ Specifically the slave.pp file and the windows file components found in it. {noformat} Notice: /Stage[main]/Jenkins::Slave/File[C:\ProgramData\jenkins-slave\jenkins-slave.xml]/content: Info: FileBucket got a duplicate file {md5}d41d8cd98f00b204e9800998e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (HI-131) Hiera 1.3.1 Release - January 21st, 2014
Title: Message Title Melissa Stone updated an issue Hiera / HI-131 Hiera 1.3.1 Release - January 21st, 2014 Change By: Melissa Stone Seehttps://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process foramoredetaileddescriptionofwhatneedstobedoneforeachsub-task 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-751) Measure stat() callls
Title: Message Title Erik Daln commented on an issue Re: Measure stat() callls For defined types puppet tries to load the .rb files from every possible location for that (every module with a lib directory, the libdir and around 10 system locations) before trying to load the .pp file from a much shorter list of possible loactions. This is even true for types that contain a :: Also it seems to try loading them for every usage of the type, not just the first time it encounters it. See this gist for a trucated example strace: https://gist.github.com/dalen/8545009 Add Comment Puppet / PUP-751 Measure stat() callls Better understanding of wasted filesystem access 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 (HI-126) Build windows specific gem
Title: Message Title Rob Reynolds commented on an issue Re: Build windows specific gem This is targeted against stable, but shouldn't it be targeted against master? Add Comment Hiera / HI-126 Build windows specific gem See PUP-1282 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-221) Smoke test packages
Title: Message Title Ethan Brown commented on an issue Re: Smoke test packages I was able to install the DMG on OSX Mavericks. facter and facter --version worked no problem. No output from 'man facter', but unsure if this is a known issue or not. Add Comment Facter / FACT-221 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 (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Erik Daln commented on an issue Re: msgpack serialization of TagSet broken https://github.com/puppetlabs/puppet/pull/2279 Add Comment Puppet / PUP-1484 msgpack serialization of TagSet broken 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-1484) msgpack serialization of TagSet broken
Title: Message Title Erik Daln created an issue Puppet / PUP-1484 msgpack serialization of TagSet broken Issue Type: Bug Affects Versions: 3.4.2 Assignee: Eric Sorenson Created: 21/Jan/14 10:50 AM Priority: Normal Reporter: Erik Daln 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.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Rob Reynolds assigned an issue to Unassigned Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-536) Create endpoint for enumerating environments
Title: Message Title Andrew Parker commented on an issue Re: Create endpoint for enumerating environments Sean Millichamp thanks for the comments. For 1) I wasn't planning on it, but it should be an easy extension. Joshua Partlow and I were working through that aspect right now. I think all it would take is to have an environmentspath instead of the environmentsdir. For 2) that wasn't in the plans. However, I was thinking that every environment should have some way of having a configuration file. That file would be able to control the environment more fine grained and something like this, where it can specify what the module directories are would fit into it. Another way of handling this would be to incorporate Puppetfiles into the environment. I think that is the right direction, but it is a much larger change. Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node Classifier and Continuous Delivery work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-237) Allow fact resolutions to be built up piece-wise.
Title: Message Title Adrien Thebo created an issue Facter / FACT-237 Allow fact resolutions to be built up piece-wise. Issue Type: New Feature Assignee: Eric Sorenson Created: 21/Jan/14 11:11 AM Priority: Normal Reporter: Adrien Thebo Some facts (like network facts) are complex data structures that are composed in a number of different parts. In cases like this users may want to append information to these structures instead of creating a new fact. FACT-65 outlined the original problem and allowing one resolution to access another resolution makes this easier, but doesn't directly tackle the issue of resolving information in parts, allowing resolutions to be appended later on, and defining a mechanism for aggregating all of the created data into a single structure. We should define a new type of resolution that is built for composing data in the described way. These resolutions should be able to be defined in parts, and can be aggregated into a final value. These resolutions should be able to be reopened so that users can extend core facts with their own data, but it should not be possible to unintentionally overwrite existing facts. Add Comment
Jira (FACT-65) Facts need to be able to retrieve the value of another resolution of the same fact.
Title: Message Title Adrien Thebo commented on an issue Re: Facts need to be able to retrieve the value of another resolution of the same fact. Working on this ticket has revealed that we need a first class method of creating resolutions that are designed to be assembled out of different parts. PR/600 adds the behavior requested in this issue, but I'm going to split out new issues for creating aggregate resolutions. Add Comment Facter / FACT-65 Facts need to be able to retrieve the value of another resolution of the same fact. h2. Story - As an author of structured facts in facter - I sometimes need to be able to augment the structure of an existing fact - So that I do not need to rewrite the entire fact nor issue the augmented structure under a new fact name h2. Example The existing `interfaces` fact contains information about all of the network interfaces on the s... 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 (PUP-1476) Puppet agent should supply an informative user agent
Title: Message Title Andrew Parker commented on an issue Re: Puppet agent should supply an informative user agent The puppet module subcommand sends a user agent when it connects to the forge. It should probably same one for other HTTP communication. Add Comment Puppet / PUP-1476 Puppet agent should supply an informative user agent Puppet agents currently report a user agent of Ruby when contacting the puppet master over https. It would be much more useful for log analysis and (potentially) debugging, if they could set something like: puppet agent $(version)/$(ruby https module) $(ruby version) Similar behaviour is desirable from the puppetmaster itself, when it contacts eg ... 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-1212) runtime errors in future evaluator has uninformative backtrace
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1212 runtime errors in future evaluator has uninformative backtrace Change By: Kurt Wall Assignee: KurtWall 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-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default
Title: Message Title Branan Purvine-Riley created an issue Puppet / PUP-1485 test agent/fallback_to_cached_catalog.rb assumes no master is running by default Issue Type: Bug Assignee: Aaron Armstrong Components: PE Created: 21/Jan/14 11:52 AM Priority: Normal Reporter: Branan Purvine-Riley When running the puppet tests against pe, the master is running even outside of a with_puppet_running_on block. Do we need a without_puppet_running_on block in beaker? Add Comment This message was sent by Atlassian JIRA
Jira (PUP-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default
Title: Message Title Joshua Cooper commented on an issue Re: test agent/fallback_to_cached_catalog.rb assumes no master is running by default how about updating the test to use a bogus server or port instead? Add Comment Puppet / PUP-1485 test agent/fallback_to_cached_catalog.rb assumes no master is running by default When running the puppet tests against pe, the master is running even outside of a with_puppet_running_on block. Do we need a without_puppet_running_on block in beaker? 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-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default
Title: Message Title Branan Purvine-Riley commented on an issue Re: test agent/fallback_to_cached_catalog.rb assumes no master is running by default Joshua Cooper That sounds like an even simpler and easier solution. I am all for it Add Comment Puppet / PUP-1485 test agent/fallback_to_cached_catalog.rb assumes no master is running by default When running the puppet tests against pe, the master is running even outside of a with_puppet_running_on block. Do we need a without_puppet_running_on block in beaker? 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-238) Extract common behaviors in aggregate and simple resolutions
Title: Message Title Adrien Thebo created an issue Facter / FACT-238 Extract common behaviors in aggregate and simple resolutions Issue Type: New Feature Assignee: Eric Sorenson Created: 21/Jan/14 12:30 PM Priority: Normal Reporter: Adrien Thebo FACT-237 outlined the need for creating resolutions in a piece-wise fashion, which means that Facter will have two separate resolution types. Both will need to expose the same functionality for determining suitability and resolving to a value. The behavior needed by both resolution types should be extracted into independent classes/mixins so that the different resolution types can behave in the same fashion. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1048) PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti
Title: Message Title gepetto-bot commented on an issue Re: PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti Pull request (#21641) Windows puppet service should log to the eventlog has been closed. Add Comment Puppet / PUP-1048 PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti h2. (#21641) Windows puppet service should log to the eventlog * Author: * Company: * Github ID: [glennsarti|https://github.com/glennsarti] * [Pull Request 2161 Discussion|https://github.com/puppetlabs/puppet/pull/2161] * [Pull Request 2161 File Diff|https://github.com/puppetlabs/puppet/pull/2161/files] h2. Pull Request Description (#21... 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-239) Expose different resolution types in DSL
Title: Message Title Adrien Thebo created an issue Facter / FACT-239 Expose different resolution types in DSL Issue Type: New Feature Assignee: Eric Sorenson Created: 21/Jan/14 12:46 PM Priority: Normal Reporter: Adrien Thebo Adding multiple resolution types to Facter means that the DSL will have to take this into account. The DSL needs to take the following into account: Resolutions need to be able to declare their type upon creation. This should just be a simple matter of taking :type = :something when the resolution is initially created. Resolutions may also need to be reopened, depending on the type. It's expected that users will reopen aggregate resolutions, but reopening simple resolutions is ill defined. If a resolution is reopened, the reopened type should match the type specified in the reopen call. If there's a mismatch an error should be raised; if no type was specified we should possibly emit a warning. Alternately, we can implement something different besides allowing resolutions to be reopened. Add Comment
Jira (FACT-239) Expose different resolution types in DSL
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-239 Expose different resolution types in DSL Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-238) Extract common behaviors in aggregate and simple resolutions
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-238 Extract common behaviors in aggregate and simple resolutions Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-237) Allow fact resolutions to be built up piece-wise.
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-237 Allow fact resolutions to be built up piece-wise. Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-238) Extract common behaviors in aggregate and simple resolutions
Title: Message Title Adrien Thebo updated an issue Facter / FACT-238 Extract common behaviors in aggregate and simple resolutions Change By: Adrien Thebo 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 (FACT-239) Expose different resolution types in DSL
Title: Message Title Adrien Thebo updated an issue Facter / FACT-239 Expose different resolution types in DSL Change By: Adrien Thebo 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-1048) PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti
Title: Message Title gepetto-bot commented on an issue Re: PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti peterhuene commented: Your commits have been merged into master. I squashed the last five given their nature as small fixes. Thanks again for the contribution. Add Comment Puppet / PUP-1048 PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti h2. (#21641) Windows puppet service should log to the eventlog * Author: * Company: * Github ID: [glennsarti|https://github.com/glennsarti] * [Pull Request 2161 Discussion|https://github.com/puppetlabs/puppet/pull/2161] * [Pull Request 2161 File Diff|https://github.com/puppetlabs/puppet/pull/2161/files] h2. Pull Request Description (#21... 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
Jira (PUP-1482) PR (2280): Fixed a bug in package/package_settings (super called without exlpicit parameter) - ptomulik
Title: Message Title gepetto-bot commented on an issue Re: PR (2280): Fixed a bug in package/package_settings (super called without exlpicit parameter) - ptomulik puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1482 PR (2280): Fixed a bug in package/package_settings (super called without exlpicit parameter) - ptomulik h2. Fixed a bug in package/package_settings (super called without exlpicit parameter) * Author: Paweł Tomulik ptomu...@meil.pw.edu.pl * Company: Warsaw University of Technology * Github ID: [ptomulik|https://github.com/ptomulik] * [Pull Request 2280 Discussion|https://github.com/puppetlabs/puppet/pull/2280] * [Pull Request 2280 File Diff|https://g... 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-1483) PR (2282): (FORGE-141) Add Basic Travis file for Module generation - petems
Title: Message Title gepetto-bot commented on an issue Re: PR (2282): (FORGE-141) Add Basic Travis file for Module generation - petems puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1483 PR (2282): (FORGE-141) Add Basic Travis file for Module generation - petems h2. (FORGE-141) Add Basic Travis file for Module generation * Author: Peter Souter * Company: * Github ID: [petems|https://github.com/petems] * [Pull Request 2282 Discussion|https://github.com/puppetlabs/puppet/pull/2282] * [Pull Request 2282 File Diff|https://github.com/puppetlabs/puppet/pull/2282/files] h2. Pull Request Description Basi... 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-229) PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo adrienthebo commented: I broke out https://tickets.puppetlabs.com/browse/FACT-238 and https://tickets.puppetlabs.com/browse/FACT-237 to cover the changes made in this pull request; I'm closing this and will submit two separate PRs for the behavior provided here. Add Comment Facter / FACT-229 PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo h2. Feature/facter 2/fact 65 aggregate resolutions * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 605 Discussion|https://github.com/puppetlabs/facter/pull/605] * [Pull Request 605 File Diff|https://github.com/puppetlabs/facter/pull/605/files]... 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.
Jira (FACT-229) PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo Pull request Feature/facter 2/fact 65 aggregate resolutions has been closed. Add Comment Facter / FACT-229 PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo h2. Feature/facter 2/fact 65 aggregate resolutions * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 605 Discussion|https://github.com/puppetlabs/facter/pull/605] * [Pull Request 605 File Diff|https://github.com/puppetlabs/facter/pull/605/files]... 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-240) PR (611): Feature/facter 2/fact 238 extract resolution mixins - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-240 PR (611): Feature/facter 2/fact 238 extract resolution mixins - adrienthebo Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 21/Jan/14 1:05 PM Labels: github Priority: Normal Reporter: gepetto-bot Feature/facter 2/fact 238 extract resolution mixins Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 611 Discussion Pull Request 611 File Diff Pull Request Description
Jira (PDB-322) Smoke test packages
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-322 Smoke test packages Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-338) PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-338 PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior Issue Type: Task Assignee: Unassigned Created: 21/Jan/14 1:06 PM Labels: github Priority: Normal Reporter: gepetto-bot Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 809 Discussion Pull Request 809 File Diff Pull Request Description Fixes the current issues running acceptance tests with the RPM packages on EL 5 (webhooks-id: d87e32dfade901dcfe8a0a28fa7f3ae8)
Jira (PDB-338) PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-338 PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior Change By: Kenneth Barber Sprint: 20140115to20140122 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-241) PR (612): Feature/facter 2/fact 237 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-241 PR (612): Feature/facter 2/fact 237 aggregate resolutions - adrienthebo Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 21/Jan/14 1:10 PM Labels: github Priority: Normal Reporter: gepetto-bot Feature/facter 2/fact 237 aggregate resolutions Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 612 Discussion Pull Request 612 File Diff Pull Request Description This
Jira (HI-142) Docs pushed
Title: Message Title Justin Holguin updated an issue Hiera / HI-142 Docs pushed Change By: Justin Holguin Assignee: JustinHolguin NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-338) PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-338 PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior Change By: Kenneth Barber Story Points: 1 Affects Version/s: 2.0.0 Fix Version/s: 2.0.0 Issue Type: Task Bug 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-134) Perform basic sanity checks on Facter output
Title: Message Title Adrien Thebo commented on an issue Re: Perform basic sanity checks on Facter output ☃! Add Comment Facter / FACT-134 Perform basic sanity checks on Facter output Facter should ensure that facts can only generate and return valid data. When a fact is requested and evaluated, the generated data should be checked to make sure that it is restricted to the output described by FACT-107. 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-238) Extract common behaviors in aggregate and simple resolutions
Title: Message Title Adrien Thebo updated an issue Facter / FACT-238 Extract common behaviors in aggregate and simple resolutions 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 (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Erik Daln updated an issue Puppet / PUP-1484 msgpack serialization of TagSet broken Change By: Erik Daln 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 (FACT-239) Expose different resolution types in DSL
Title: Message Title Adrien Thebo updated an issue Facter / FACT-239 Expose different resolution types in DSL 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-237) Allow fact resolutions to be built up piece-wise.
Title: Message Title Adrien Thebo updated an issue Facter / FACT-237 Allow fact resolutions to be built up piece-wise. 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 (HI-133) Ensure tests are passing
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-133 Ensure tests are passing Change By: Henrik Lindberg Assignee: AndrewParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-133) Ensure tests are passing
Title: Message Title Henrik Lindberg commented on an issue Re: Ensure tests are passing All Hiera Jenkins Jobs green at the time this comment was entered. Marking as done. Add Comment Hiera / HI-133 Ensure tests are passing All tests (spec, acceptance) should be passing on all platforms. 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-1466) incorrect error message You need rubygems to use Hiera
Title: Message Title
Tim Mooney updated an issue
Puppet / PUP-1466
incorrect error message You need rubygems to use Hiera
updated formatting using Jira markup
Change By:
Tim Mooney
I'veattemptedtofollowthedocumentationhere:http://docs.puppetlabs.com/guides/upgrading.htmltotestpromotingoneofourexistingpuppet2.7.14clientsystemstobea(test)3.4.2puppetmaster.I'vealsotriednotpromotingtheclient,andinsteadjustinstalling3.4.2fromscratch.Bothattemptedinstallationmethodsresultinthesameerror.Istarttheserverusingtheargumentsrecommendedintheupgradedocument: {noformat} $sudopuppetmaster--no-daemonize--verboseNotice:StartingPuppetmasterversion3.4.2 {noformat} WhenIconnectwithaclientsystem,theclientgetsthemessage: {noformat} Error:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:YouneedrubygemstouseHieraat/etc/puppet/manifests/users.pp:243onnoderh6client.example.comWarning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrun {noformat} Meanwhile,theserverconsolehasoutput: {noformat} Info:access[^/catalog/([^/]+)$]:allowing'method'findInfo:access[^/catalog/([^/]+)$]:allowing$1accessInfo:access[^/node/([^/]+)$]:allowing'method'findInfo:access[^/node/([^/]+)$]:allowing$1accessInfo:access[/certificate_revocation_list/ca]:allowing'method'findInfo:access[/certificate_revocation_list/ca]:allowing*accessInfo:access[^/report/([^/]+)$]:allowing'method'saveInfo:access[^/report/([^/]+)$]:allowing$1accessInfo:access[^/file_(metadata|content)/secure/]:addingauthenticationyesInfo:access[^/file_(metadata|content)/secure/]:allowingIP10.1.1.0/24accessInfo:access[/file]:allowing*accessInfo:access[/facts]:addingauthenticationanyInfo:access[/facts]:allowing'method'findInfo:access[/facts]:allowing'method'searchInfo:access[/facts]:allowingconfig-tmp.example.comaccessInfo:access[/facts]:allowingconfig.example.comaccessInfo:access[/certificate/ca]:addingauthenticationanyInfo:access[/certificate/ca]:allowing'method'findInfo:access[/certificate/ca]:allowing*accessInfo:access[/certificate/]:addingauthenticationanyInfo:access[/certificate/]:allowing'method'findInfo:access[/certificate/]:allowing*accessInfo:access[/certificate_request]:addingauthenticationanyInfo:access[/certificate_request]:allowing'method'findInfo:access[/certificate_request]:allowing'method'saveInfo:access[/certificate_request]:allowing*accessInfo:access[/]:addingauthenticationanyInfo:Insertingdefault'/status'(authtrue)ACLInfo:Cachingnodeforrh6client.example.comInfo:Cachingnodeforrh6client.example.comWarning:Puppet.features.rubygems?isdeprecated.Requirerubygemsinyourapplication'sentrypointifyouneedit.(at/usr/lib/ruby/site_ruby/1.8/puppet/util/feature.rb:17:in`add')Error:YouneedrubygemstouseHieraat/etc/puppet/manifests/users.pp:243onnoderh6client.example.comError:YouneedrubygemstouseHieraat/etc/puppet/manifests/users.pp:243onnoderh6client.example.comError:YouneedrubygemstouseHieraat/etc/puppet/manifests/users.pp:243onnoderh6client.example.com {noformat}
Jira (FACT-230) PR (606): Feature/facter 2/fact 65 add default aggregate, freeze chunks - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (606): Feature/facter 2/fact 65 add default aggregate, freeze chunks - adrienthebo Pull request Feature/facter 2/fact 65 add default aggregate, freeze chunks has been closed. Add Comment Facter / FACT-230 PR (606): Feature/facter 2/fact 65 add default aggregate, freeze chunks - adrienthebo h2. Feature/facter 2/fact 65 add default aggregate, freeze chunks * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 606 Discussion|https://github.com/puppetlabs/facter/pull/606] * [Pull Request 606 File Diff|https://github.com/puppetlabs/facter/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-338) PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior puppetlabs-jenkins commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/164/ Add Comment PuppetDB / PDB-338 PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior h2. Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 809 Discussion|https://github.com/puppetlabs/puppetdb/pull/809] * [Pull Request 809 File Diff|https://github.com/puppetlabs/puppetdb/pul... 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
Jira (PDB-338) PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior Pull request Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code has been closed. Add Comment PuppetDB / PDB-338 PR (809): Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code - senior h2. Added Postgres 8.4 declaration to the acceptance test PuppetDB package installation code * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 809 Discussion|https://github.com/puppetlabs/puppetdb/pull/809] * [Pull Request 809 File Diff|https://github.com/puppetlabs/puppetdb/pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (HI-134) Is there a bug targeted at the release for every commit?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a bug targeted at the release for every commit? Redmine issues #22142, and #22273 mentioned in commits between 1.3.0, and 1.3.1-rc1. Other commits are (maint), (packaging), or no tag at all (but seems to be about infrastructure for building / testing). Add Comment Hiera / HI-134 Is there a bug targeted at the release for every commit? 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-134) Is there a bug targeted at the release for every commit?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a bug targeted at the release for every commit? #22142 retargeted from 1.4.0 to 1.3.1 http://projects.puppetlabs.com/issues/22142 Add Comment Hiera / HI-134 Is there a bug targeted at the release for every commit? 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-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Issue Type: Task Assignee: Unassigned Created: 21/Jan/14 2:04 PM Labels: github Priority: Normal Reporter: gepetto-bot Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 810 Discussion Pull Request 810 File Diff Pull Request Description (webhooks-id: 9690f18569001b1e0916ba99aac35a83)
Jira (HI-134) Is there a bug targeted at the release for every commit?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a bug targeted at the release for every commit? #22273 already targeted at 1.3.1 since 1 month Add Comment Hiera / HI-134 Is there a bug targeted at the release for every commit? 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-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Change By: Kenneth Barber Sprint: 20140115to20140122 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Change By: Kenneth Barber Story Points: 1 Affects Version/s: 1.5.0 Fix Version/s: 1.5.X Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Pull request Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox has been closed. Add Comment PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior h2. Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 810 Discussion|https://github.com/puppetlabs/puppetdb/pull/810] * [Pull Request 810 File Diff|https://github.com/puppetla... 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.
Jira (HI-29) Pull Request (159): (#22142) Substantial speed increase in lookups
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-29 Pull Request (159): (#22142) Substantial speed increase in lookups Change By: Henrik Lindberg Fix Version/s: 1.4.0 Fix Version/s: 1.3.1RC Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior senior commented: Closing to target 1.5.x Add Comment PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior h2. Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 810 Discussion|https://github.com/puppetlabs/puppetdb/pull/810] * [Pull Request 810 File Diff|https://github.com/puppetla... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (FACT-228) Close all resolved tickets in Jira
Title: Message Title Melissa Stone assigned an issue to Kylo Ginsberg Facter / FACT-228 Close all resolved tickets in Jira Change By: Melissa Stone Assignee: MelissaStone KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-135) Is there a commit for every bug targeted at the release?
Title: Message Title Henrik Lindberg commented on an issue Re: Is there a commit for every bug targeted at the release? yes, there are commits - there is however multiple book-keeping; a redmine issue that is targeting the release is fixed on master, and backported to stable. There is a redmine ticket for 23273, and several Jira tickets. Looks ok though. Add Comment Hiera / HI-135 Is there a commit for every bug targeted at the 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 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-340) PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-340 PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Change By: Kenneth Barber Story Points: 1 Affects Version/s: 1.5.0 Fix Version/s: 1.5.X Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-134) Is there a bug targeted at the release for every commit?
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-134 Is there a bug targeted at the release for every commit? Change By: Henrik Lindberg Assignee: AndrewParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-340) PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-340 PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Change By: Kenneth Barber Sprint: 20140115to20140122 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-136) Is a new version created for the next version in the series?
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-136 Is a new version created for the next version in the series? Change By: Henrik Lindberg Assignee: AndrewParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-135) Is there a commit for every bug targeted at the release?
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-135 Is there a commit for every bug targeted at the release? Change By: Henrik Lindberg Assignee: AndrewParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-340) PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-340 PR (811): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior Issue Type: Task Assignee: Unassigned Created: 21/Jan/14 2:20 PM Labels: github Priority: Normal Reporter: gepetto-bot Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 811 Discussion Pull Request 811 File Diff Pull Request Description (webhooks-id: a3b3f67a95bfd1d7d9b341ea49a6dd77)
Jira (PDB-336) PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB won't start: OutOfMemoryError: Java heap space So trying to get an OOM out of that KahaDB content, however I'm unable to replicate in my development setup Simon Croome ... what exact version of PE is this, and what distro and version did you run it on? Add Comment PuppetDB / PDB-336 PuppetDB won't start: OutOfMemoryError: Java heap space Every attempt, PuppetDB was failing to start with: java.lang.OutOfMemoryError: Java heap space Dumping heap to /var/log/pe-puppetdb/puppetdb-oom.hprof ... Heap dump file created [62635185 bytes in 0.552 secs] java.lang.OutOfMemoryError: Java heap space at org.apache.kahadb.journal.DataFileAccessor.readRecord (DataFileAccessor.java:87) org.apa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-339) PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior puppetlabs-jenkins commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/165/ Add Comment PuppetDB / PDB-339 PR (810): Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox - senior h2. Explicitly drop an /etc/hosts file (rather than relying on DCHP) which is wrong sometimes in VirtualBox * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 810 Discussion|https://github.com/puppetlabs/puppetdb/pull/810] * [Pull Request 810 File Diff|https://github.com/puppetla... 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
Jira (HI-136) Is a new version created for the next version in the series?
Title: Message Title Henrik Lindberg commented on an issue Re: Is a new version created for the next version in the series? We have a 1.4.0 tag Add Comment Hiera / HI-136 Is a new version created for the next version in the series? 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-140) Smoke test packages
Title: Message Title Henrik Lindberg commented on an issue Re: Smoke test packages Centos 5/6 Debian Squeeze/Wheezy Ubuntu Lucid/Precise Gem Check that hiera is available. *man hiera (except for gems) Add Comment Hiera / HI-140 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)
