Jira (PUP-2896) purge_ssh_keys wouldn't remove entries without comments
Title: Message Title
Muhammad Hallaj bin Subery created an issue
Puppet / PUP-2896
purge_ssh_keys wouldn't remove entries without comments
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
07/Jul/14 1:23 AM
Environment:
Ubuntu 12.04 Puppet 3.6.2-1puppetlabs1
Priority:
Normal
Reporter:
Muhammad Hallaj bin Subery
Puppet's purge_ssh_keys is unable to purge existing keys without comments in them:
Steps to reproduce:
content of /home/h2/.ssh/authorized_keys:
ssh-dss some_key
{/code}
user.pp
user { hallaj: ensure = present, home = /home/h2, managehome = true, purge_ssh_keys = true } {/code} Result of execution with --debug:
Debug: /Stage[main]/Main/Ssh_authorized_key[some_odd_key]: Nothing to manage: no ensure and the resource doesn't exist{/code}
– Edit the
Jira (PUP-2896) purge_ssh_keys wouldn't remove entries without comments
Title: Message Title
Muhammad Hallaj bin Subery updated an issue
Puppet / PUP-2896
purge_ssh_keys wouldn't remove entries without comments
Change By:
Muhammad Hallaj bin Subery
Puppet'spurge_ssh_keysisunabletopurgeexistingkeyswithoutcommentsinthem:Stepstoreproduce:contentof/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_key{ / code}user.pp:{code}user{hallaj:ensure=present,home=/home/h2,managehome=true,purge_ssh_keys=true}{ / code}Resultofexecutionwith--debug:{noformat}Debug:/Stage[main]/Main/Ssh_authorized_key[some_odd_key]:Nothingtomanage:noensureandtheresourcedoesn'texist{ / noformat}--Editthe/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_keycomment{ / code}Resultofexecutionwith--debug:{code}Notice:/Stage[main]/Main/Ssh_authorized_key[comment]/ensure:removedDebug:Flushingssh_authorized_keyprovidertarget/home/h2/.ssh/authorized_key{ / code}Finalresultof/home/h2/.ssh/authorized_keys:{noformat}#HEADER:ThisfilewasautogeneratedatMonJul0708:21:40+2014#HEADER:bypuppet.Whileitcanstillbemanagedmanually,it#HEADER:isdefinitelynotrecommended.{ / noformat}Ibelievethebehaviorofpurge_ssh_keysshouldnotbelimitedtokeyswithcommentsincluded.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2896) purge_ssh_keys wouldn't remove entries without comments
Title: Message Title
Muhammad Hallaj bin Subery updated an issue
Puppet / PUP-2896
purge_ssh_keys wouldn't remove entries without comments
Change By:
Muhammad Hallaj bin Subery
Puppet'spurge_ssh_keysisunabletopurgeexistingkeyswithoutcommentsinthem:Stepstoreproduce:contentof/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_key{/code}user.pp{code}user{hallaj:ensure=present,home=/home/h2,managehome=true,purge_ssh_keys=true}{/code}Resultofexecutionwith--debug:{ code noformat }Debug:/Stage[main]/Main/Ssh_authorized_key[some_odd_key]:Nothingtomanage:noensureandtheresourcedoesn'texist{/ code noformat }--Editthe/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_keycomment{/code}Resultofexecutionwith--debug:{code}Notice:/Stage[main]/Main/Ssh_authorized_key[comment]/ensure:removedDebug:Flushingssh_authorized_keyprovidertarget/home/h2/.ssh/authorized_key{/code}Finalresultof/home/h2/.ssh/authorized_keys:{code}#HEADER:ThisfilewasautogeneratedatMonJul0708:21:40+2014#HEADER:bypuppet.Whileitcanstillbemanagedmanually,it#HEADER:isdefinitelynotrecommended.{/code}Ibelievethebehaviorofpurge_ssh_keysshouldnotbelimitedtokeyswithcommentsincluded.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2896) purge_ssh_keys wouldn't remove entries without comments
Title: Message Title
Muhammad Hallaj bin Subery updated an issue
Puppet / PUP-2896
purge_ssh_keys wouldn't remove entries without comments
Change By:
Muhammad Hallaj bin Subery
Puppet'spurge_ssh_keysisunabletopurgeexistingkeyswithoutcommentsinthem:Stepstoreproduce:contentof/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_key{/code}user.pp : {code}user{hallaj:ensure=present,home=/home/h2,managehome=true,purge_ssh_keys=true}{/code}Resultofexecutionwith--debug:{noformat}Debug:/Stage[main]/Main/Ssh_authorized_key[some_odd_key]:Nothingtomanage:noensureandtheresourcedoesn'texist{/noformat}--Editthe/home/h2/.ssh/authorized_keys:{code}ssh-dsssome_keycomment{/code}Resultofexecutionwith--debug:{code}Notice:/Stage[main]/Main/Ssh_authorized_key[comment]/ensure:removedDebug:Flushingssh_authorized_keyprovidertarget/home/h2/.ssh/authorized_key{/code}Finalresultof/home/h2/.ssh/authorized_keys:{ code noformat }#HEADER:ThisfilewasautogeneratedatMonJul0708:21:40+2014#HEADER:bypuppet.Whileitcanstillbemanagedmanually,it#HEADER:isdefinitelynotrecommended.{/ code noformat }Ibelievethebehaviorofpurge_ssh_keysshouldnotbelimitedtokeyswithcommentsincluded.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2707) Puppet loads ZFS module on FreeBSD when ZFS is not enabled
Title: Message Title Remko Catersels updated an issue Puppet / PUP-2707 Puppet loads ZFS module on FreeBSD when ZFS is not enabled Change By: Remko Catersels Assignee: RemkoCatersels Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2897) undefined method `exist?' for Puppet::FileSystem:Module
Title: Message Title Taylor Leese created an issue Puppet / PUP-2897 undefined method `exist?' for Puppet::FileSystem:Module Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Created: 07/Jul/14 3:10 AM Environment: Mac OSX 10.9.3, Vagrant 1.6.3, Puppet 3.6.2, Facter 1.7.5, ubuntu/trusty64 Priority: Normal Reporter: Taylor Leese I attempted to upgrade Puppet from 3.4.3 to 3.6.2, but I receive the errors below. 1) undefined method `exist?' for Puppet::FileSystem:Module 2) Unsupported checksum type md5 Note, the errors only occur when I use the Vagrant apply provisioner. If I run the puppet agent manually from the ubuntu instance then all is fine. I'm wondering if this is related to OSX or Vagrant. Also note, everything works fine with Puppet 3.4.3 even with the Vagrant apply provisioner. Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults Error: Could not back up /etc/puppet/auth.conf.dpkg-dist: Unsupported checksum type md5 Error: Could not back up /etc/puppet/auth.conf.dpkg-dist: Unsupported checksum type md5 Error: /Stage[main]/Puppet::Config/File[/etc/puppet/auth.conf.dpkg-dist]/ensure: change from file to absent failed: Could not back up /etc/puppet/auth.conf.dpkg-dist: Unsupported checksum type md5 Error: Could not back up /etc/puppet/puppet.conf:
Jira (PDB-730) Ensure tests are passing
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-730 Ensure tests are passing Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-731) Is there a bug targeted at the release for every commit?
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-731 Is there a bug targeted at the release for every commit? Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-732) Is there a commit for every bug targeted at the release?
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-732 Is there a commit for every bug targeted at the release? Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Boyan Tabakov commented on an issue
Re: Server-set global variables like $::environment get overwritten by client facts
Andy Parker Having facts inside the $facts hash doesn't seem to be enough to solve this at least as of puppet 3.6.x. Client facts still appear as global variables, even though the $facts has is enabled. For example, both of these work:
notify {from global: ${::osfamily}:} notify {from facts hash: $ {facts[osfamily]}
:}
As a result the server-set variables are still overridden by client facts with the same name.
Add Comment
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2898) Long form Resource Type reference fools future parser this is an override
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-2898
Long form Resource Type reference fools future parser this is an override
Issue Type:
Bug
Assignee:
Andy Parker
Components:
DSL
Created:
07/Jul/14 6:35 AM
Fix Versions:
3.7.0
Priority:
Normal
Reporter:
Henrik Lindberg
When setting defaults for a resource type R, the short form works:
R { attr = value }
but not the long form:
Resource[R] { attr = value }
Resource['r'] { attr = value }
This problem is due to the static transformation of a resource _expression_ since the two forms (override and default) have different rules than a regular resource _expression_.
Ideally I would like to only have one form and require that defaults have a title of literal default, and that overrides specify the title of the resource that is being overridden. This would alleviate much grammar pain.
Jira (PDB-753) PR (1006): Include documentation for 'store report' version 4 - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1006): Include documentation for 'store report' version 4 - kbarber pljenkinsro commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/508/ Add Comment PuppetDB / PDB-753 PR (1006): Include documentation for 'store report' version 4 - kbarber h2. Include documentation for 'store report' version 4 * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1006 Discussion|https://github.com/puppetlabs/puppetdb/pull/1006] * [Pull Request 1006 File Diff|https://github.com/puppetlabs/puppetdb/pull/1006/files] h2. Pull Reque... 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-753) PR (1006): Include documentation for 'store report' version 4 - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1006): Include documentation for 'store report' version 4 - kbarber Pull request Include documentation for 'store report' version 4 (and other minor doc fixes) has been closed. Add Comment PuppetDB / PDB-753 PR (1006): Include documentation for 'store report' version 4 - kbarber h2. Include documentation for 'store report' version 4 * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1006 Discussion|https://github.com/puppetlabs/puppetdb/pull/1006] * [Pull Request 1006 File Diff|https://github.com/puppetlabs/puppetdb/pull/1006/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-753) PR (1006): Include documentation for 'store report' version 4 - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1006): Include documentation for 'store report' version 4 - kbarber pljenkinsro commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/509/ Add Comment PuppetDB / PDB-753 PR (1006): Include documentation for 'store report' version 4 - kbarber h2. Include documentation for 'store report' version 4 * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1006 Discussion|https://github.com/puppetlabs/puppetdb/pull/1006] * [Pull Request 1006 File Diff|https://github.com/puppetlabs/puppetdb/pull/1006/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2899) adding stat() functionality to filebucket function
Title: Message Title daniel pecka created an issue Puppet / PUP-2899 adding stat() functionality to filebucket function Issue Type: Improvement Assignee: Unassigned Created: 07/Jul/14 6:53 AM Priority: Normal Reporter: daniel pecka Hello, We need to enhance a filebucket function that it contains also `meta' file (along with contents and paths files) which will store a stat() information for file per path .. We'd also add there an additional field tag which would store some custom tag (string) if specified .. Should we write this adjustment or do any of YOU want to add this capability ? just something like this (used ; as separator, might be something else): perl -e 'my $file = qq@/etc/hosts@; my $tag = foobar, my @fstat = stat $file; print join(qq/;/, $file, @fstat, $tag), \n' /etc/hosts;64768;8242;33188;1;0;0;0;231;1404654233;1404481396;1404481396;4096;8;foobar would be great for items in filebucket in ``meta'' file .. eg in output below: find $_bd -type f | grep 7fda24f62b1c7ae951db0f746dc6e0cc ./var/bucket/7/f/d/a/2/4/f/6/7fda24f62b1c7ae951db0f746dc6e0cc/paths ./var/bucket/7/f/d/a/2/4/f/6/7fda24f62b1c7ae951db0f746dc6e0cc/contents would be additionally ``./var/bucket/7/f/d/a/2/4/f/6/7fda24f62b1c7ae951db0f746dc6e0cc/meta'' file with that content .. what do you think about that please ?
Jira (PUP-2899) adding stat() functionality to filebucket function
Title: Message Title daniel pecka commented on an issue Re: adding stat() functionality to filebucket function okay, I was discussing that in #puppet channel on freenode and guys there are requesting some more background info, so here it comes: we have some our framework helping us to generate a puppet .pp manifest files and we have to maintain separate db for storing files stat()s externally because we store files in filebucket and it just lacks this capability .. regards, daniel ps. please correct me if I am re-inventing the wheel pps. important part in our (my) request is additional last filed with custom $tag string .. we use it for real magic things and the only requirement for $tag field is that it holds some string which we parse/postprocess additionally Add Comment Puppet / PUP-2899 adding stat() functionality to filebucket function Hello, We need to enhance a filebucket function that it contains also `meta' file (along with contents and paths files) which will store a stat() information for file per path .. We'd also add there an additional field tag which would store some custom tag (string) if specified .. Should we write this adjustment or do any of YOU want to add this c... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg commented on an issue Re: Server-set global variables like $::environment get overwritten by client facts Boyan Tabakov Are you saying that they are overridden both in the $facts hash as well as the global variable? Add Comment Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2899) storing stat() info in filebucket for items
Title: Message Title daniel pecka updated an issue Puppet / PUP-2899 storing stat() info in filebucket for items Change By: daniel pecka Summary: adding storing stat() functionalityto infoin filebucket function foritems Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2900) sshkey resource created /etc/ssh/ssh_known_hosts mode 0600
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2900
sshkey resource created /etc/ssh/ssh_known_hosts mode 0600
Issue Type:
Bug
Assignee:
Unassigned
Created:
07/Jul/14 7:40 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
I used an sshkey resource like this:
pre sshkey { host.domain.example: ensure = present, type = ssh-rsa, key = AAAblahblahblah==, }
/pre
and puppet created the /etc/ssh/ssh_known_hosts file with sensible contents, but with mode 0600.
This file is supposed to be world readable. Of course I can use a file resource to fix it, but I'd prefer it if puppet created it with a sensible mode.
Add Comment
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Henrik Lindberg commented on an issue Re: parameter lookup produces screwy result for default values The discussion of what to do is still ongoing. There are several proposals and ideas. Several of these are more radical (remove defaults and change syntax and semantics). meanwhile, the implementation of default lookup for parameter access is just plain wrong (in any scenario) and should be corrected. PR-2844 contains a fix that will lookup the default value from the correct scope (the resource's closure) as opposed to the calling scope. With that PR in effect, the default lookup will: lookup the default value for a parameter if the value is nil the default value is the value in effect as a default at that point in the evaluation order (it is possible to affect it after this point, but only though semi-magical things like reopening the class Any looked up value may be changed by lazy evaluation of overrides (resource override / collection with override) anyway, and is thus only a prediction of what the value may be. IMO, it is better to allow looking up the default value since the language has mutating operations. Add Comment Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2894) lvalue comma asignment should splat* an array
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2894 lvalue comma asignment should splat* an array Change By: Henrik Lindberg Fix Version/s: 4.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Peter Huene commented on an issue Re: Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. For FR, I recommend a Debian-based distro like Ubuntu or even Archlinux, which also has a UID_MIN of 1000. Add Comment Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-743) Report retrieval fails on JSON::ParserError
Title: Message Title Andy Parker updated an issue PuppetDB / PDB-743 Report retrieval fails on JSON::ParserError Change By: Andy Parker Summary: Report submission retrieval failsonJSON::ParserError Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-611) Create structured versions of flattened facts
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-611 Create structured versions of flattened facts Change By: William Hopper Assignee: EricSorenson WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-611) Create structured versions of flattened facts
Title: Message Title William Hopper created an issue Facter / FACT-611 Create structured versions of flattened facts Issue Type: Epic Assignee: Eric Sorenson Created: 07/Jul/14 9:45 AM Fix Versions: 2.2.0 Priority: Normal Reporter: William Hopper With Facter 2 and the addition of support for structured facts, we'd like to create nested facts which allow for better organization of related data. There are a number of existing flat facts which are good candidates for such structuring. The functionality of these original flat facts should also be left intact for the sake of backwards compatibility. Add Comment
Jira (PDB-743) Report retrieval fails on JSON::ParserError
Title: Message Title Andy Parker commented on an issue Re: Report retrieval fails on JSON::ParserError I just updated the title of this issue. The problem isn't on report submission, it is on report retrieval. The test is performing a puppet agent run and then fetching the report that should be available. Periodically the response on the retrieval request is returning no body, which then doesn't parse as JSON and the test fails. Add Comment PuppetDB / PDB-743 Report retrieval fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... 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,
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Sprint: Week2014- 7 6 - 23 25 to2014- 8 7 - 6 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker 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/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Sprint: Week2014-7-23to2014-8-6 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker commented on an issue Re: Periodic timeouts when reading from master I think the correct fix for this will involve: Audit that the timeout that Josh identified isn't needed Remove the timeout if it turns out that it truly is redundant Push the timeout down closer to where it is needed if it turns out there are other issues the timeout could have been covering. Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
This can't be verified by CI until CI is setup.
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Rob Reynolds Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-612) Create structured uptime fact
Title: Message Title
William Hopper created an issue
Facter / FACT-612
Create structured uptime fact
Issue Type:
New Feature
Assignee:
William Hopper
Created:
07/Jul/14 10:01 AM
Fix Versions:
2.2.0
Priority:
Normal
Reporter:
William Hopper
Currently, there are four flat facts for uptime: uptime_seconds, uptime_hours, uptime_days and uptime. Merging these facts into a simple structured fact would be a good kick-off for structured fact work.
The output for this fact could appear as follows: {seconds=609351, hours=169, days=7, uptime=7 days}
To maintain backwards compatibility, the original flat uptime facts should remain intact. However, this presents a possible problem in terms of keeping the flat and structured versions of a fact in sync with each other.
One possible solution is to centralize the resolutions of the facts within the structured fact itself, and then simply refactor the flat facts to use values generated from their structured counterparts.
Another consideration is the naming of this structured fact. Since the obvious choice 'uptime' is already claimed by the flat fact version, we can't just use that. As per several discussions with the platform team, one possible name is 'system_uptime,' which doesn't set a hard precedent for structured fact names.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
Guessing it was part of Ethan Brown's original work on the acceptance selector.
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-612) Create structured uptime fact
Title: Message Title
William Hopper commented on an issue
Re: Create structured uptime fact
I've got a pull request up for this at: https://github.com/puppetlabs/facter/pull/712
Add Comment
Facter / FACT-612
Create structured uptime fact
Currently, there are four flat facts for uptime: uptime_seconds, uptime_hours, uptime_days and uptime. Merging these facts into a simple structured fact would be a good kick-off for structured fact work. The output for this fact could appear as follows: {seconds=609351, hours=169, days=7, uptime=7 days} To maintain backwards compatibi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-611) Create structured versions of flattened facts
Title: Message Title William Hopper updated an issue Facter / FACT-611 Create structured versions of flattened facts Change By: William Hopper WithFacter2andtheadditionofsupportforstructuredfacts,we'dliketocreatenestedfactswhichallowforbetterorganizationofrelateddata.Thereareanumberofexistingflatfactswhicharegoodcandidatesforsuchstructuring. Thefunctionalityofthese Tomaintainbackwardscompatibility,the originalflatfactsshould alsobeleft remain intact .However,thispresentsapossibleproblemintermsofkeepingtheflatandstructuredversionsofafactinsyncwitheachother.Onepossiblesolutionistocentralizetheresolutionsofthefactswithinthestructuredfactitself,andthensimplyrefactortheflatfactstousevaluesgeneratedfromtheirstructuredcounterparts.Otherconsiderationsunderdiscussionincludenaming for structuredfactswhichcollidewith the sake names of backwardscompatibility theirflatfactcounterparts . Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1108) Class inheritance and stages act weirdly
Title: Message Title
Lucas Yamanishi updated an issue
Puppet / PUP-1108
Class inheritance and stages act weirdly
Change By:
Lucas Yamanishi
Giventhecode: pre {code} stage{first:before=Stage[main]}classfoo{package{zsh:ensure=present}}classbarinheritsfoo{notify{/usr/bin/cowsay'helloworld':require=Package[zsh]}}class{bar:stage=first} /pre {code} Thisproduce pre {code} err:Couldnotapplycompletecatalog:Founddependencycyclesinthefollowingrelationships:Package[zsh]=Notify[/usr/bin/cowsay'helloworld'],Notify[/usr/bin/cowsay'helloworld']=Package[zsh],Notify[/usr/bin/cowsay'helloworld']=Class[main];tryusingthe'--graph'optionandopenthe'.dot'filesinOmniGraffleorGraphViz /pre {code} IfIadd: pre {code} class{foo:stage=first} /pre {code} Itsortsitselfout.Iamnotsurewhatthecorrectbehaviorwouldbe,atfirstIthinkweshouldjustpulltheinheritedclassintothe'first'stageaswellbutIcanimaginethatcausingweirdissuestoo?
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title
Andy Parker commented on an issue
Re: The manifests directory should be recursively loaded when using directory environments
Merged into master in bb4608.
Add Comment
Puppet / PUP-2711
The manifests directory should be recursively loaded when using directory environments
We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-480 Complete handling of undef/nil 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/d/optout.
Jira (FACT-613) Create structured processor fact
Title: Message Title
William Hopper updated an issue
Facter / FACT-613
Create structured processor fact
Change By:
William Hopper
Currently,therearefiveprocessorbasedfacts:Processor,ProcessorCount,PhysicalProcessorCount,ProcessorSpeedanddynamicProcessorXfacts,whichareresolveddependingonoperatingsystem.Theseareagoodcandidateformergingintoasinglestructuredfact.Theoutputforthisfactcouldappearasfollows(simulatedforasystemthatresolveseachprocessorfact):{ {noformat}}{ processorlist={Processor0=Intel(R)Xeon(R)CPUE5-26090@2.40GHz,Processor1=Intel(R)Xeon(R)CPUE5-26090@2.40GHz},processorcount=2,physicalprocessorcount=2,processorspeed=2.40GHz,processor=Intel(R)XeonCPUE5-2609} {{noformat}} Tomaintainbackwardscompatibility,theoriginalflatprocessorfactsshouldremainintact.Asstatedinthisissue'sEpic,synchronizationbetweenflatandstructuredfactsisaconcern.Thefinalnameforthisstructuredfactisalsounderconsideration.Onecurrentcandidateis'processors,'whichdoesnotcollidewithanyexistingfacts.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-613) Create structured processor fact
Title: Message Title
William Hopper created an issue
Facter / FACT-613
Create structured processor fact
Issue Type:
New Feature
Assignee:
William Hopper
Created:
07/Jul/14 10:33 AM
Fix Versions:
2.2.0
Priority:
Normal
Reporter:
William Hopper
Currently, there are five processor based facts: Processor, ProcessorCount, PhysicalProcessorCount, ProcessorSpeed and dynamic ProcessorX facts, which are resolved depending on operating system. These are a good candidate for merging into a single structured fact.
The output for this fact could appear as follows (simulated for a system that resolves each processor fact):
{processorlist= {Processor0=Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz, Processor1=Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz}
, processorcount=2, physicalprocessorcount=2, processorspeed=2.40 GHz, processor=Intel(R) Xeon CPU E5-2609}
To maintain backwards compatibility, the original flat processor facts should remain intact. As stated in this issue's Epic, synchronization between flat and structured facts is a concern.
The final name for this structured fact is also under consideration. One current candidate is 'processors,' which does not collide with any existing facts.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker updated an issue Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
This is blocked by PUP-2388
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-613) Create structured processor fact
Title: Message Title
William Hopper updated an issue
Facter / FACT-613
Create structured processor fact
Change By:
William Hopper
Currently,therearefiveprocessorbasedfacts:Processor,ProcessorCount,PhysicalProcessorCount,ProcessorSpeedanddynamicProcessorXfacts,whichareresolveddependingonoperatingsystem.Theseareagoodcandidateformergingintoasinglestructuredfact.Theoutputforthisfactcouldappearasfollows(simulatedforasystemthatresolveseachprocessorfact):{ { noformat} } {processorlist={Processor0=Intel(R)Xeon(R)CPUE5-26090@2.40GHz,Processor1=Intel(R)Xeon(R)CPUE5-26090@2.40GHz},processorcount=2,physicalprocessorcount=2,processorspeed=2.40GHz,processor=Intel(R)XeonCPUE5-2609}{ { noformat} } Tomaintainbackwardscompatibility,theoriginalflatprocessorfactsshouldremainintact.Asstatedinthisissue'sEpic,synchronizationbetweenflatandstructuredfactsisaconcern.Thefinalnameforthisstructuredfactisalsounderconsideration.Onecurrentcandidateis'processors,'whichdoesnotcollidewithanyexistingfacts.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-612) Create structured uptime fact
Title: Message Title
William Hopper updated an issue
Facter / FACT-612
Create structured uptime fact
Change By:
William Hopper
Currently,therearefourflatfactsforuptime:uptime_seconds,uptime_hours,uptime_daysanduptime.Mergingthesefactsintoasimplestructuredfactwouldbeagoodkick-offforstructuredfactwork.Theoutputforthisfactcouldappearasfollows:{ noformat}{ seconds=609351,hours=169,days=7,uptime=7days} {noformat} Tomaintainbackwardscompatibility,theoriginalflatuptimefactsshouldremainintact.However,thispresentsapossibleproblemintermsofkeepingtheflatandstructuredversionsofafactinsyncwitheachother.Onepossiblesolutionistocentralizetheresolutionsofthefactswithinthestructuredfactitself,andthensimplyrefactortheflatfactstousevaluesgeneratedfromtheirstructuredcounterparts.Anotherconsiderationisthenamingofthisstructuredfact.Sincetheobviouschoice'uptime'isalreadyclaimedbytheflatfactversion,wecan'tjustusethat.Asperseveraldiscussionswiththeplatformteam,onepossiblenameis'system_uptime,'whichdoesn'tsetahardprecedentforstructuredfactnames.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker commented on an issue Re: parameter lookup produces screwy result for default values Merged into master in 13186f Add Comment Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the lookup resource parameter scope/context, and not the context... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-734) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages packages available at http://builds.puppetlabs.lan/puppetdb/2.1.0/ Add Comment PuppetDB / PDB-734 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/d/optout.
Jira (PUP-1970) regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Title: Message Title Andy Parker updated an issue Puppet / PUP-1970 regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2888) invalid parameter 'mode' when using nagios_host
Title: Message Title Krystle Bennett updated an issue Puppet / PUP-2888 invalid parameter 'mode' when using nagios_host Change By: Krystle Bennett Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-613) Create structured processor fact
Title: Message Title
William Hopper updated an issue
Facter / FACT-613
Create structured processor fact
Change By:
William Hopper
Currently,therearefiveprocessorbasedfacts:Processor,ProcessorCount,PhysicalProcessorCount,ProcessorSpeedanddynamicProcessorXfacts,whichareresolveddependingonoperatingsystem.Theseareagoodcandidateformergingintoasinglestructuredfact.Theoutputforthisfactcouldappearasfollows(simulatedforasystemthatresolveseachprocessorfact):{noformat}{processorlist={Processor0=Intel(R)Xeon(R)CPUE5-26090@2.40GHz, Processor1=Intel(R)Xeon(R)CPUE5-26090@2.40GHz}, processorcount=2, physicalprocessorcount=2, processorspeed=2.40GHz, processor=Intel(R)XeonCPUE5-2609}{noformat}Tomaintainbackwardscompatibility,theoriginalflatprocessorfactsshouldremainintact.Asstatedinthisissue'sEpic,synchronizationbetweenflatandstructuredfactsisaconcern.Thefinalnameforthisstructuredfactisalsounderconsideration.Onecurrentcandidateis'processors,'whichdoesnotcollidewithanyexistingfacts.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-614) Create structured operating system fact
Title: Message Title
William Hopper created an issue
Facter / FACT-614
Create structured operating system fact
Issue Type:
New Feature
Assignee:
William Hopper
Created:
07/Jul/14 11:01 AM
Priority:
Normal
Reporter:
William Hopper
Currently, there are several facts related to operating system based data, including:
operatingsystem
operatingsystemmajrelease
operatingsystemrelease
osfamily
Also, there are a handful of lsb* facts for Linux systems, including:
lsbdistcodename
lsbdistdescription
lsbdistid
lsbdistrelease
lsbmajdistrelease
lsbrelease
These combined are a good candidate for a structured fact.
Output for this fact could appear as follows (on a Linux system):
{ osfamily = Debian,
operatingsystem = Debian,
release = {
operatingsystemrelease = 7.4,
operatingsystemmajrelease = 7 },
lsb = {
lsbdistid = Debian,
lsbdistcodename = wheezy,
lsbdistdescription = Debian GNU/Linux 7.4 (wheezy),
lsbdistrelease = 7.4,
lsbmajdistrelease = 7 }
}
Backwards compatibility with existing flat facts should be maintained. The naming of this structured fact is also under consideration.
Jira (FACT-615) Create structured networking fact
Title: Message Title
William Hopper created an issue
Facter / FACT-615
Create structured networking fact
Issue Type:
New Feature
Assignee:
William Hopper
Created:
07/Jul/14 11:13 AM
Priority:
Normal
Reporter:
William Hopper
Currently, there are several networking based flat facts which are good candidates for merging into a structured fact.
These flat facts include:
interfaces
netmask
ip_address
mac_address
Sample output for this fact could look as follows:
network_interfaces = {eth0=
{type=physical,
ip_address=192.168.1.1,
netmask=255.255.255.0,
mac_address=00:10:24:f4:ab:ce},
eth1=
{type=physical,
ip_address=192.168.1.2,
netmask=255.255.255.0,
mac_address=00:10:24:f4:ab:cb},
bond0=
{type=bonding,
ip_address=192.168.1.3,
netmask=255.255.255.0,
mac_address=00:10:24:f4:ab:cd,
interfaces=[eth0, eth1]}}
As with other structured fact work, the original flat fact functionality should be maintained.
A possible name for this structured fact is 'network_interfaces.'
Jira (PUP-1970) regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Title: Message Title Andy Parker updated an issue Puppet / PUP-1970 regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user Change By: Andy Parker Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Moses Mendoza commented on an issue Re: Upgrade win32-taskscheduler (or replace) To summarize conversation in hipchat earlier: To be able to ship puppet for windows using the correct FFI, as well as be able to run specs and develop (run from source), we need: a - an updated gem that we're going to have to ship under a new name like puppetlabs-win32-taskscheduler b - the code from this source file brought into the Puppet repo to be able to run specs and develop on c - vendor it initially (b), so we can develop, run specs, then prior to release, do (a) and update the Gemfile to point to the newly released gem Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. 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 (PDB-734) Smoke test packages
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test packages This includes: Debian 7 Ubuntu 14.04 A good vagrantfile for this is: # -*- mode: ruby -*- # vi: set ft=ruby : # Vagrantfile API/syntax version. Don't touch unless you know what you're doing! VAGRANTFILE_API_VERSION = 2 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.provider vmware_fusion do |v| v.vmx[memsize] = 2048 v.vmx[numvcpus] = 2 end config.vm.define debian-7.4-64-nocm do |vm| vm.vm.box = puppetlabs/debian-7.4-64-nocm end config.vm.define ubuntu-14.04-64-nocm do |vm| vm.vm.box = puppetlabs/ubuntu-14.04-64-nocm end end Add Comment PuppetDB / PDB-734 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)
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Moses Mendoza commented on an issue Re: Upgrade win32-taskscheduler (or replace) note, the win32-taskscheduler gem is licensed under the Artistic 2.0 license. http://rubygems.org/gems/win32-taskscheduler http://opensource.org/licenses/Artistic-2.0 Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Moses Mendoza commented on an issue Re: Upgrade win32-taskscheduler (or replace) Michael Stahnke We currently ship an un-modified version of the library via puppet-win32-ruby. However, can you review the license of win32-taskscheduler above with the context of shipping a modified version? Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-taskscheduler (or replace) After further discovery, it turns on that version 0.3.x of the win32-taskscheduler gem is no longer compatible with Windows 2003 as it uses Scheduler.Service which is a Task Scheduler 2.0 scripting object (based on IDispatch) Unfortunately this means that we're going to need to heavily modify the 0.2.2 branch of the original gem. There is some question about what the appropriate shipping vehicle will be given timelines on the 3.7 release. We already vendor and modify the gem version of the code in the puppet-win32-ruby repository, which satisfies our requirements around acceptance testing. We can make modifications to the gem code there for what we ship. However, we still need some sort of source / gem version to be used by: Developers (including 3rd parties which rules out shipping something to only our local gem mirror) For spec tests Our options are Move the taskscheduler.rb file from the 0.2.2 tag into the Puppet repo – https://github.com/djberg96/win32-taskscheduler/blob/win32-taskscheduler-0.2.2/lib/win32/taskscheduler.rb and remove the usage of the gem altogether in the gemspec. This is the simplest approach at this point in time, but does require inclusion of code that was previously maintained by an external third party via gem. Fork the original repo to a Puppetlabs repo, make modifications there and release a new gem with a new name like puppetlabs-win32-taskscheduler. Update the local gemspec accordingly. This will require release engineering to introduce new jobs, etc. I believe this would generally be the preferred approach, but given timelines around this release might not be feasible right now? Perform a combination of the two approaches. Move the code into the Puppet repo for now, but make those changes concurrently in the forked repo, so that RE may release a gem at some point in time. Once the release pipeline is established, remove the temporarily vendored taskscheduler.rb and add the puppetlabs-win32-taskscheduler gem back into the Puppet gemspec. Note that the original win32-taskscheduler gem code uses Artistic License 2.0 and any decision should reflect any requirements around maintaining license compatibility: http://opensource.org/licenses/Artistic-2.0 /cc Moses Mendoza Melissa Stone
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title
Josh Cooper commented on an issue
Re: Upgrade win32-eventlog
I have modified puppet to reference the eventlog constants directly, and added specs for existing functionality here: https://github.com/joshcooper/puppet/tree/ticket/master/PUP2889-eventlog
I am seeing a problem when running on win2008r2 with ruby 1.9.3p545, but it is a preexisting issue, reproducible as far back as commit 338db55
C:\work\puppet [ticket/master/PUP2889-eventlog +11 ~0 -0 !] bundle exec rspec spec/unit/util/execution_spec.rb
Run options: exclude {:broken=true, :benchmark=true}
...F.
Failures:
1) Puppet::Util::Execution#execpipe should fail if asked to fail, and the child does
Failure/Error: expect { Puppet::Util::Execution.execpipe('echo hello') }.
Mocha::ExpectationError:
unexpected invocation: nil.==(/error message/)
satisfied expectations:
- allowed any number of times, not yet invoked: Signal.trap(any_parameters)
- allowed any number of times, invoked once: Puppet::Util::Execution.open(any_parameters)
- expected exactly once, invoked once: nil.==(0)
# ./spec/unit/util/execution_spec.rb:627:in `block (3 levels) in top (required)'
Add Comment
Puppet / PUP-2889
Upgrade win32-eventlog
We need to either upgrade or replace the use of win32-eventlog. During some upgrading we found issues, which lead to this particular ticket out of PUP-392.
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Josh Cooper assigned an issue to Rob Reynolds Puppet / PUP-2889 Upgrade win32-eventlog Change By: Josh Cooper Assignee: JoshCooper RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-597) facter needs a package dependency on net-tools on rhel7 for ifconfig
Title: Message Title Trevor Vaughan commented on an issue Re: facter needs a package dependency on net-tools on rhel7 for ifconfig I'd like to confirm this. There is some chatter about using nmcli on the Internet, but I think FACT-184 has it right. Add Comment Facter / FACT-597 facter needs a package dependency on net-tools on rhel7 for ifconfig With RHEL 7, a minimal install doesn't even include an ifconfig binary. It's still available as /sbin/ifconfig if you install the net-tools package, but it's no longer required and guaranteed to be there. I've tried both facter 1.7.6 and facter 2.0.2, both from the PuppetLabs repo, and because neither package records a dependency on net-tools fo... 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,
Jira (FACT-211) Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp
Title: Message Title
Trevor Vaughan commented on an issue
Re: Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp
I cannot reproduce either on physical systems or VMs running Cent6 with ruby-1.8.7.352-13.el6.x86_64.
Add Comment
Facter / FACT-211
Facter 1.7.x crashes on CentOS 6.x VMs with an illegal instruction while looking up sshfp
Support for ssh fingerprints (as merged in https://github.com/puppetlabs/facter/pull/162) breaks facter while running on CentOS 6.x on a VM due to a bug with ruby 1.8.7, which is what CentOS 6 provides. {code} [acompton@] /usr/lib/ruby/site_ruby/1.8/facter facter --debug Relative directory ./facter removed from search path. value fo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2891 creating a resource override for a Class fails (future parser) Change By: Henrik Lindberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2901) Puppet Module Tool should validate dependencies
Title: Message Title Brandon High created an issue Puppet / PUP-2901 Puppet Module Tool should validate dependencies Issue Type: Improvement Assignee: Brandon High Components: PMT Created: 07/Jul/14 1:20 PM Priority: Minor Reporter: Brandon High 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
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr gem as a Windows dependency Follow on commit in c682c5a Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-472 Sync facter-2 code with master Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title
Kurt Wall commented on an issue
Re: Complete handling of undef/nil
Using Andy's code (except that I changed ident4 to identx, here's the output for the current parser
$ bundle exec puppet apply --parser current undef.pp
Notice: Scope(Class[main]): $x == undef
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): undef == undef
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): != undef
Notice: Scope(Class[main]): false
Notice: Scope(Class[main]): erb w/unbound lookupvar
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): erb w/bound but undef lookupvar
Notice: Scope(Class[main]): false
Notice: Scope(Class[main]): match vars without a match ($0 == undef)
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): undef literal passed to function translated to empty string (3x function)
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): unbound variable passed to function translated to empty string (3x function)
Notice: Scope(Class[main]): true
Notice: Scope(Class[main]): variable bound to undef passed to function translated to empty string (3x function)
Notice: Scope(Class[main]): true
Notice: Scope(A[a]): a { a: }
Notice: Scope(A[a]): true
Notice: Scope(A[b]): a { b: value = undef }
Notice: Scope(A[b]): true
Notice: Scope(A[c]): a { c: value = $x }
Notice: Scope(A[c]): true
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.08 seconds
Notice: Finished catalog run in 0.05 seconds
With the future parser:
$ bundle exec puppet apply --parser future undef.pp
Notice: $x == undef
Notice: true
Notice: undef == undef
Notice: true
Notice: != undef
Notice: true
Notice: erb w/unbound lookupvar
Notice: true
Notice: erb w/bound but undef lookupvar
Notice: true
Notice: match vars without a match ($0 == undef)
Notice: true
Notice: undef literal passed to function translated to empty string (3x function)
Notice: true
Notice: unbound variable passed to function translated to empty string (3x function)
Notice: true
Notice: variable bound to undef passed to function translated to empty string (3x function)
Notice: true
Notice: epp w/unbound var
Notice: true
Notice: epp w/bound but undef var
Notice: true
Notice: epp with undef passed as param uses default
Notice: true {value = }
Notice: undef literal passed to function (4x function)
Notice: true
Notice: unbound variable passed to function (4x function)
Notice: true
Notice: variable bound to undef passed to function (4x function)
Notice: true
Notice: a { a: }
Notice: true
Notice: a { b: value = undef }
Notice: true
Notice: a { c: value = $x }
Notice: true
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.34 seconds
Notice: Finished catalog run in 0.05 seconds
Add Comment
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Kurt Wall updated an issue Puppet / PUP-480 Complete handling of undef/nil 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/d/optout.
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API 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/d/optout.
Jira (PUP-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title
Andy Parker commented on an issue
Re: Specify signatures for blocks of block-accepting methods
Merged code changes into master in dc6c81.
Add Comment
Puppet / PUP-2794
Specify signatures for blocks of block-accepting methods
Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-500) Test CollectExpressions
Title: Message Title Andy Parker commented on an issue Re: Test CollectExpressions Merged new tests into master in 651af2 Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker updated an issue Puppet / PUP-2833 All concrete types do not inherit PAnyType Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2825) Change Ruby type to Runtime
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2825 Change Ruby type to Runtime Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2825) Change Ruby type to Runtime
Title: Message Title Andy Parker updated an issue Puppet / PUP-2825 Change Ruby type to Runtime Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2833 All concrete types do not inherit PAnyType Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker commented on an issue Re: All concrete types do not inherit PAnyType Merged into master in b20e46 This change doesn't have any real user-visible changes. It can skip Functional Review Add Comment Puppet / PUP-2833 All concrete types do not inherit PAnyType All concrete types in the type system should inherit from the PAnyType. Now, some types still inherit from the abstract PAbstractType. For some reason this manages to work even if it is wrong. It should be corrected. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-500) Test CollectExpressions
Title: Message Title Andy Parker commented on an issue Re: Test CollectExpressions Spec updated with PR-7 in commit 1bf754 Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2902) collection of classes should raise a meaningful error
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2902 collection of classes should raise a meaningful error Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2902) collection of classes should raise a meaningful error
Title: Message Title Andy Parker updated an issue Puppet / PUP-2902 collection of classes should raise a meaningful error Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title
Josh Cooper commented on an issue
Re: Support Bundler workflow on x64
We are using bundle to execute specs on ruby 2, marking this as resolved: https://jenkins.puppetlabs.com/job/Puppet-Specs-Windows-Master-Ruby2x64/
Add Comment
Puppet / PUP-2777
Support Bundler workflow on x64
Puppet expresses Windows gem dependencies, but it only applies to ruby x86. When running on x64, the gem dependencies do not apply, so you can't use bundler to install gems, and run specs. Currently, puppet's Gemfile uses the bundler `mingw` platform identifier, effectively: {noformat} platform :mingw do gem 'ffi' ... end {noformat} {{Bu...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title
Kurt Wall commented on an issue
Re: Move epp() and inline_epp() to 4x function API
By visual inspection at SHA=13186fdc06decc690c1d6ad6eef3c0ca9672a8e4 in master, I can confirm that epp.rb and inline_epp.rb have been moved to the Puppet v4 API. In addition, EPP templates appear to work in v4 as they did in v3:
%-| $x, $y, $z = 'default value' |-%
x = %= $x %
y = %= $y %
z = %= $z %
$ be puppet apply -e notice epp('x.epp', { x=1, y=2, z=undef }) --templatedir . --parser future --disable_warnings deprecations
Notice: x = 1
y = 2
z = default value
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.35 seconds
Notice: Finished catalog run in 0.03 seconds
$ be puppet apply -e 'with(1,2,3) | Integer *$x | { notice $x }' --parser future --disable_warnings deprecations
Notice: [1, 2, 3]
Notice: Compiled catalog for breve.corp.puppetlabs.net in environment production in 0.34 seconds
Notice: Finished catalog run in 0.04 seconds
Add Comment
Puppet / PUP-2845
Move epp() and inline_epp() to 4x function API
The {{epp()}} and {{inline_epp()}} functions must be moved to the 4x function API in order to work correctly. The 3x function API requires transformation of all undef/nils to empty string, and that catalog entry types are transformed to Resource references. This does not work well when these values again emerge in Puppet logic. This also blocks the wan...
Jira (PUP-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. 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/d/optout.
Jira (PUP-2857) Add a Default type
Title: Message Title Andy Parker updated an issue Puppet / PUP-2857 Add a Default type Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper commented on an issue Re: Validate win32 gems on x86 and x64 Except for win32-eventlog and win32-taskscheduler, all of puppet's win32 gem dependencies have been updated in puppet's Gemfile (via project_data.yaml) and in both the x86 and x64 branches of our vendored ruby. For x86, puppet specs and acceptance are passing. For x64, puppet specs are passing conditionally (due to eventlog and taskscheduler issues covered under PUP-2889 and PUP-2881 respectively), and puppet acceptance will be addressed in PUP-2388 Verified that x86 gem dependencies: ffi: '1.9.3' win32-api: '1.4.8' win32-dir: '~ 0.4.9' win32-eventlog: '~ 0.5.3' win32-process: '~ 0.7.4' win32-security: '~ 0.2.5' win32-service: '~ 0.8.4' win32-taskscheduler: '~ 0.2.2' win32console: '1.3.2' windows-api: '~ 0.4.2' windows-pr: '~ 1.2.2' minitar: '~ 0.5.4' matches https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3-x86/ruby/lib/ruby/gems/1.9.1/gems. Note deep_merge is for hiera, stomp is for mcollective, and rgen is a puppet dependency, not specific to windows. Also note we are vendoring win32-service v0.8.5 because 0.8.4 has a bug. Verified that x64 gem dependencies: ffi: '1.9.3' win32-dir: '~ 0.4.9' win32-eventlog: '~ 0.6.1' win32-process: '~ 0.7.4' win32-security: '~ 0.2.5' win32-service: '~ 0.8.4' win32-taskscheduler: '~ 0.3.0' minitar: '~ 0.5.4' Match https://github.com/puppetlabs/puppet-win32-ruby/tree/2.0.0-x64/ruby/lib/ruby/gems/2.0.0/gems Note win32-api, windows-api, and windows-pr will be removed as part of PUP-2521 Add Comment Puppet / PUP-392 Validate win32 gems on x86 and x64
Jira (PUP-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API 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/d/optout.
Jira (PUP-2902) collection of classes should raise a meaningful error
Title: Message Title
Andy Parker commented on an issue
Re: collection of classes should raise a meaningful error
Merged into master in b119f6
Add Comment
Puppet / PUP-2902
collection of classes should raise a meaningful error
If an attempt is made to collect classes {code} Class | | {code} The 3x runtime issues an error that says: {code} Error: Resource type class doesn't exist {code} Which is misleading. The 4x runtime fails with this message: (essentially the same). {code} Error while evaluating a Virtual Query, Resource type class doesn't exist {code} 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/d/optout.
Jira (PUP-2825) Change Ruby type to Runtime
Title: Message Title
Andy Parker commented on an issue
Re: Change Ruby type to Runtime
Merged into master in f71608
There isn't really anything to FR on this. It is almost entirely an internal item at this point.
Add Comment
Puppet / PUP-2825
Change Ruby type to Runtime
The type system has space in it for referring to types internal the the runtime that implements the puppet language. At the moment this is the word {{Ruby}}, but space has been made in the language specification for other languages as well. Unfortunately, that name sits on a name that is also very likely to be used in describing configurations, since o...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2857) Add a Default type
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2857 Add a Default type Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Verified: x64 Color and unicode box characters correctly drawn: C:\work\puppet [master +11 ~0 -0 !] bundle exec puppet module list DL is deprecated, please use Fiddle DL is deprecated, please use Fiddle C:/ProgramData/PuppetLabs/puppet/etc/modules ├── dprince-qpid (v1.0.2) ├── duritong-sysctl (v0.0.4) Color correctly displayed for debug levels: C:\work\puppet [master] bundle exec puppet resource service --debug DL is deprecated, please use Fiddle DL is deprecated, please use Fiddle Debug: Runtime environment: puppet_version=3.6.2, ruby_version=2.0.0, run_mode=user, default_encoding=IBM437 Debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist and win32console is not a gem dependency: C:\work\puppet [master +11 ~0 -0 !] bundle exec gem list | grep win32console DL is deprecated, please use Fiddle x86 Color and unicode box characters drawn correctly: C:\work\puppet [master +11 ~0 -0 !] bundle exec puppet module list C:/ProgramData/PuppetLabs/puppet/etc/modules ├── dprince-qpid (v1.0.2) ├── duritong-sysctl (v0.0.4) Debug log levels are colorized: C:\work\puppet [master] bundle exec puppet agent --debug Debug: Failed to load library 'syslog' for feature 'syslog' Debug: Failed to load library 'selinux' for feature 'selinux' And win32console is a gem dependency: C:\work\puppet [master] bundle exec gem list | grep win32console win32console (1.3.2 x86-mingw32)
Jira (PUP-1283) Update win32-service gem
Title: Message Title Josh Cooper commented on an issue Re: Update win32-service gem This is blocked while we wait for win32-service v 0.8.6 to be published. Add Comment Puppet / PUP-1283 Update win32-service gem The win32-service gem was patched upstream to resolve #16080. The fix was merged upstream https://github.com/djberg96/win32-service/pull/8. At a minimum we need to update the gem and remove the patch https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3/16080-handle-missing-description.patch. We also need to make sure we can update to the `ffi` b... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-744 Pool HTTPS connections Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Denis Boulas commented on an issue Re: Pool HTTPS connections Thank you Josh for taking ownership over the issue! Could you please tell me, how does it possible to enable that feature? which version required and so on and so force. Add Comment Puppet / PUP-744 Pool HTTPS connections Reduce network traffic and latency This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-472 Sync facter-2 code with master Change By: Kylo Ginsberg Itseemslikeconversationshaveconvergedon Thecurrentplanis :* master syncfacter - zombie(andisn'tupdated) 2tomaster * makemastercarry delete the contentof facter-2 (revertalot branch and mergeup?) jenkinsjobs * remove continue facter - 2 AndthenonlydoCI .2+development on stableand master and , cherry- pick/portfromzombie pickingforward as wego.[~adrien][~peter.huene]pleasecomment. appropriate Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Kylo Ginsberg commented on an issue Re: Sync facter-2 code with master Adrien Thebo can you review the linked pull? I put the steps I took in the commit message so that might bear some review as well. Add Comment Facter / FACT-472 Sync facter-2 code with master The current plan is: * sync facter-2 to master * delete the facter-2 branch and jenkins jobs * continue facter 2.2+ development on master, cherry-picking forward as appropriate This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-743) Report retrieval fails on JSON::ParserError
Title: Message Title Kurt Wall commented on an issue Re: Report retrieval fails on JSON::ParserError Kenneth Barber Is it possible to reduce the amount of debugging info you requested yet still obtain useful information? We've just had another failure, so it reproduces reliablly in our CI environment. Add Comment PuppetDB / PDB-743 Report retrieval fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... 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
