Jira (PUP-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3249) Remove async_storeconfigs and queue service on the master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3249 Remove async_storeconfigs and queue service on the master Change By: Adrien Thebo Sprint: 2014-09-17 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-3245) Function calls no longer showing up in profile data
Title: Message Title
Adrien Thebo commented on an issue
Re: Function calls no longer showing up in profile data
Merged in 5f076ac.
Add Comment
Puppet / PUP-3245
Function calls no longer showing up in profile data
When the {{profile}} setting is enabled, the catalog compilation tracks course grained profiling information. One piece of information tracked is how long it takes it to make function calls. {noformat} Debug: PROFILE [apply] 2.3.1 Called notice: took 0.0001 seconds {noformat} However, this information is missing when the future parser is in effect...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-3214) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages RedHat 6/7. Add Comment Puppet / PUP-3214 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the Tag and create pa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1106 Resource refreshes don't check for failed dependencies Change By: Adrien Thebo Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1106 Resource refreshes don't check for failed dependencies Change By: Adrien Thebo Sprint: 2014-09-17 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-779) Remove deprecated process execution methods in util
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-779 Remove deprecated process execution methods in util Change By: Adrien Thebo Sprint: 2014-09-17 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-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-900 noop = true is ignored when resource is triggered by other resource Change By: Adrien Thebo Component/s: CatalogApplication 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-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-900 noop = true is ignored when resource is triggered by other resource Change By: Adrien Thebo Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Adrien Thebo commented on an issue Re: Too easy to hit CRL not yet valid for host (and not very informative) Merged in 20cf917. Add Comment Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Currently we set the CRL time range to start at 1 second in the past: https://github.com/puppetlabs/puppet/blob/a8311df5438601a3394d38e37f671626969d50db/lib/puppet/ssl/certificate_revocation_list.rb#L85 However, this creates a window where an agent with a small amount of clock skew can hit the `CRL not yet valid for host` message. This affects bo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1489) Missing group should give error in noop
Title: Message Title
Adrien Thebo commented on an issue
Re: Missing group should give error in noop
We can't necessarily presume that there will be a group resource that will create the group in question; it's not implausible that a package postinst could create the group we need. Alternately Puppet could set up LDAP in the same run that it creates local users, so if there was a local user with a GID from LDAP the resource could be actually created but we couldn't determine this when running in noop.
Add Comment
Puppet / PUP-1489
Missing group should give error in noop
Given this manifest: class users { user { 'testing': ensure = present, gid = 'staff', } If group staff is unmanaged and missing from the target node, enforcing the class in noop mode should give some sort of warning that the group is missing. However, no warning is given, and then when enforcing the class without noop, the enforcemen...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you 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-1106) Resource refreshes don't check for failed dependencies
Title: Message Title
Adrien Thebo commented on an issue
Re: Resource refreshes don't check for failed dependencies
The same bug that triggers this can cause unscheduled resources to be refreshed as well:
schedule { AM:
period = daily,
range = 0 - 1,
}
exec{unscheduled:
command = /usr/bin/cowsay 'fail :(',
logoutput = true,
subscribe = Exec[true],
schedule = AM,
}
exec{true: command = /bin/true}
└ bexec puppet apply test-unscheduled.pp --no-ignoreschedules
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.03 seconds
Notice: /Stage[main]/Main/Exec[true]/returns: executed successfully
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: _
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: fail :(
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: -
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: \ ^__^
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: \ (oo)\___
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: (__)\ )\/\
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: ||w |
Notice: /Stage[main]/Main/Exec[unscheduled]/returns: || ||
Notice: /Stage[main]/Main/Exec[unscheduled]: Triggered 'refresh' from 1 events
Notice: Finished catalog run in 0.20 seconds
Add Comment
Puppet / PUP-1106
Resource refreshes don't check for failed dependencies
Given this manifest: {code} exec{moo: command = /usr/bin/cowsay 'fail :(', refreshonly = true, logoutput =
Jira (PUP-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title
Adrien Thebo commented on an issue
Re: noop = true is ignored when resource is triggered by other resource
Jason Antman this has actually been on my hit list for a while; I did the preliminary work to figure out what's going on in https://github.com/puppetlabs/puppet/commit/230667aed533186504cb916e06bae1d6011a4bf6 so this wasn't as hardcore as it may seem. I'm glad we could get this solved for you!
Add Comment
Puppet / PUP-900
noop = true is ignored when resource is triggered by other resource
when running : {code} file {'/tmp/asd': content = generate('/bin/date'), notify = Exec['ttt'], }exec { 'ttt': command ='/bin/date', logoutput = true, noop = true, } {code} exec is still ran even tho it's set to noop, any notify to resource makes it ignore noop parameter: {cod...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title
Adrien Thebo commented on an issue
Re: facter id broken on solaris10 as root
Merged in 3988185.
Add Comment
Facter / FACT-683
facter id broken on solaris10 as root
installed from source at SHA 5994c22 {code} -bash-3.2# which facter /opt/csw/bin/facter -bash-3.2# facter /usr/bin/id: illegal option -- n Usage: id [-ap] [user] architecture = i86pc {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-692) Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Title: Message Title
Adrien Thebo commented on an issue
Re: Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Merged into stable in 99ac35c.
Add Comment
Facter / FACT-692
Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Prior to Facter 2.2.0, the operatingsystemrelease facts in Solaris 10 resolved as follows: {noformat} operatingsystemmajrelease = 10 operatingsystemrelease = 10_u11 {noformat} After the release, the major release resolution changed to: {noformat} operatingsystemmajrelease = 10_u11 operatingsystemrelease = 10_u11 {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2925) Puppet:Module undefined method error `lookup`
Title: Message Title
Adrien Thebo commented on an issue
Re: Puppet:Module undefined method error `lookup`
Could you add {trace=true}
to the master section of puppet.conf on your master and paste the backtrace that occurs on the master when this error is generated?
Add Comment
Puppet / PUP-2925
Puppet:Module undefined method error `lookup`
After upgrading to Debian 7.5 I experience the following error when running Puppet with * puppet agent -t --debug *: {quote} Debug: Finishing transaction 11909740 {color:orange} Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (FACT-656) facter generates error on Solaris kernel zone due to prtdiag
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-656
facter generates error on Solaris kernel zone due to prtdiag
Change By:
Adrien Thebo
facterwhenrunonaSolaris11.2kernelzoneattemptstorunprtdiags.Thiscommandalthoughpresentonlygeneratesanerrormessage#prtdiagprtdiag:failedtoopenSMBIOS:SystemdoesnotexportanSMBIOStableThuswhenfacterisrunthiscommandisoutputtedtothescreen.Simplyredirectingstderrto/dev/nullwhenprtdiagisruncorrectsthisissue {noformat} ---facter-2.0.2/lib/facter/virtual.rb.orig2014-08-1311:15:18.794085126-0600+++facter-2.0.2/lib/facter/virtual.rb2014-08-1311:17:43.465379141-0600@@-60,7+60,7@@setcodedonextzoneifFacter::Util::Virtual.zone?-output=Facter::Core::Execution.exec('prtdiag')+output=Facter::Core::Execution.exec('prtdiag2/dev/null')ifoutputlines=output.split(\n)nextparallelsiflines.any?{|l|l=~/Parallels/} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-654) facter ldom.rb generate virtinfo usage error on Solaris 11.2 x86 boxes
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-654
facter ldom.rb generate virtinfo usage error on Solaris 11.2 x86 boxes
Change By:
Adrien Thebo
OracleSolaris11.2introducedarewriteofvirtinfo.Thenewversionofvirtinfosupportsbothx86andsparc.Thepreviousversiononlysupportedsparc.WhenFacter2.0.2or2.1.0isrunonanx86systemFacterwillgenerateausagemessageinldom.rbsincethecommandvirtinfoispresentbutthatoptionisnotsupportedonx86x86onlysupports {noformat} $virtinfo--helpusage:virtinfo[[-cclass[,...]]subcommand]list[[-H]-ofield[,...]][virtualenvironment]...get[[-H]-ofield[,...]]all|property[,...][virtualenvironment]...helpproperty|environment {noformat} Pointertomanpagehttp://docs.oracle.com/cd/E36784_01/html/E36871/virtinfo-1m.html#REFMAN1Mvirtinfo-1mOnSPARCtheoldformatisstillavailablesothiserrorcanbeeliminatedwiththefollowingminorcorrection. {noformat} ---facter-2.1.0/lib/facter/ldom.rb.orig2014-08-1317:15:34.284330702-0600+++facter-2.1.0/lib/facter/ldom.rb2014-08-1317:16:13.476092829-0600@@-1,4+1,6@@-ifFacter.value(:kernel)=='SunOS'andFacter::Core::Execution.which('virtinfo')+ifFacter.value(:kernel)=='SunOS'and+Facter.value(:hardwareisa)=='sparc'and+Facter::Core::Execution.which('virtinfo')virtinfo=Facter::Core::Execution.exec('virtinfo-ap')#Convertvirtinfoparseableoutputformattoarrayofarrays. {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (FACT-662) Extend ldom.rb to indicate whether ldom creation is supported
Title: Message Title Adrien Thebo updated an issue Facter / FACT-662 Extend ldom.rb to indicate whether ldom creation is supported Change By: Adrien Thebo Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-900 noop = true is ignored when resource is triggered by other resource Change By: Adrien Thebo Sprint: 2014-09-17 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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo commented on an issue Re: Puppet should be able to use authenticated proxies Alyce Fowler you can try installing Puppet from the nightly repos (http://puppetlabs.com/blog/new-package-repositories-open-source-puppet) to test this feature out; in addition we hope to ship Puppet 3.7.0 in the next 24 hours so you should be able to install from the standard repositories then and pick up this feature. Add Comment Puppet / PUP-2869 Puppet should be able to use authenticated proxies Currently Puppet has the ability to use proxies when performing network communications. The current settings allow for a host and a port, but not for a username or a password. This limitation prevents tools such as PMT from being utilised from a Puppet master that is behind an authenticated proxy. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-3153) Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks
Title: Message Title Adrien Thebo commented on an issue Re: Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks Since Chris Price has verified this I think we can call that suitable FR. Add Comment Puppet / PUP-3153 Need to guard against `nil` when calling `Uniquefile#close!` in `ensure` blocks in `util.rb#replace_file`, there is an `ensure` block that calls `close!` on the `Uniquefile` object. However, if an exception is thrown during the call to the constructor for `Uniquefile` (e.g., if the user does not have write permissions to the specified directory), then this attempt to call `close!` will result in a NilClass exception, which will mask... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Adrien Thebo Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-617) Facter README.md should express semver/support
Title: Message Title Adrien Thebo updated an issue Facter / FACT-617 Facter README.md should express semver/support Change By: Adrien Thebo Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Facter 2.3.0 version already exists: https://tickets.puppetlabs.com/browse/FACT/fixforversion/11855 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Facter 2.2.1: https://tickets.puppetlabs.com/browse/FACT/fixforversion/11910 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? 2.2.0 version marked as released. Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Introduced in 2.2.0: https://tickets.puppetlabs.com/issues/?filter=12623 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-669) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Fixed in 2.2.0: https://tickets.puppetlabs.com/issues/?filter=12624 Add Comment Facter / FACT-669 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 6 looks good: root@debian-6-i386:/home/vagrant# facter -y --- kernelmajversion: 2.6 productname: VirtualBox ipaddress_eth0: 10.0.2.15 sshfp_rsa: |- SSHFP 1 1 a03ec0d9ca479337890f4323309c810b293cb9b8 SSHFP 1 2 664da055eb8ae3e2cabc0cb465a5e2115295c659489adcde95c825e8a49d4a2d kernelversion: 2.6.32 operatingsystemmajrelease: 6 lsbminordistrelease: 0 rubysitedir: /usr/local/lib/site_ruby/1.8 memorysize_mb: 375.61 blockdevice_sr0_vendor: VBOX bios_version: VirtualBox ps: ps -ef filesystems: ext2,ext3 lsbdistcodename: squeeze hardwareisa: unknown lsbdistrelease: 6.0.7 blockdevice_sda_size: 10632560640 uniqueid: 007f0101 blockdevice_sr0_size: 1073741312 kernel: Linux hostname: debian-6-i386 serialnumber: 0 osfamily: Debian kernelrelease: 2.6.32-5-686 network_eth0: 10.0.2.0 uptime_seconds: 72 facterversion: 2.2.0 sshfp_dsa: |- SSHFP 2 1 e2dec8bb4349c557cab7111cdeece9060ee65b1c SSHFP 2 2 1505077ddefd207792093b808c0d247a7d1710df50a46910f02955769efc06ab blockdevices: sda,sr0,sr1 boardserialnumber: 0 netmask_eth0: 255.255.255.0 swapsize_mb: 455.99 uuid: 3B9946D9-F532-4B93-AA8B-FFE4D227DF31 interfaces: eth0,lo macaddress_eth0: 08:00:27:3a:9d:d7 is_virtual: true manufacturer: innotek GmbH sshdsakey: B3NzaC1kc3MAAACBAMao58AjusuEma6TzpnF8h/lN7g0A3wWmAOyO8VuikEH4eCpE59AflF+z+c+jzhQa/oHl7fpf5XohTAkrY6W4Y/YQnOCkfrRKSa9NliRl+hYf+Y0lDTFr7Cdk8NE5aAWflNrVHxXrrSS+4x/D52BG5WnNG+psezosW6UuvciVMjLFQD3kZRXLhGZklygKctBIDY7Vb5TwQAAAIEAjMaroVHtoTu/3txJ/EeE6WJn4f37U/8j0harBF19KuJb8ult4sTlxg2FPGmdZBecPcMDbIxcuINzr2Jviyg9ZnzjbR44f106ZQgIFIjElO79XE3PsHJa0vfKpRuTmChnfcWgVH+T7tMLSRa9BO1kwy+Uj4bhqjpYpfpa/sWv+E8AAACBAKu4uMlXgwLDuqEfNZ5htQuIty6xkQRvPo1ziE06ppSj4Vy2NZy80OIFppwumkqKqxbS9j3SCxPj1M01Jsysx2HuJaWq0mTi/plMGxY3yN+YIbOpNGcOkOu1/JSlHMBjRwqEUy07Opo9SvhiBl5etWXw1V1Wg61VF0EOIp1xnV5b macaddress: 08:00:27:3a:9d:d7 uptime: 0:01 hours timezone: UTC mtu_lo: 16436 fqdn: debian-6-i386.dc1.puppetlabs.net boardmanufacturer: Oracle Corporation processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz physicalcount: 1 count: 1 path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin hardwaremodel: i686 netmask_lo: 255.0.0.0 processorcount: 1 uptime_days: 0 virtual: virtualbox blockdevice_sr0_model: CD-ROM operatingsystemrelease: 6.0.7 system_uptime: seconds: 72 days: 0 hours: 0 uptime: 0:01 hours sshrsakey: B3NzaC1yc2EDAQABAAABAQCiKOi7C4mkdFzKbEugMDXZWE8aKwyJgakDarZdSrg7/Fmg7ihlprgv4pw3r1WNBmWFduvAEF1clQ/8aOcA2S9332FemzGVyvTSpoM2GtyLo5b2E07y2sPgLMEwtPZJSdOYjfBQZDTKYJlo003PVX5G2EKvkj30Ocqh1BI15QwJTJF6yhPw+9nlMJw1wlN9Z7oGKeeWPGW7c6d3GZceaAMlRFvyY30fb5Ip68m1f87lYA7tddEYPjY03NC9TbgDPJyzX2eLKH9mwzm6UCnIFGFkb7mwGsrEoILyvsjguJFSWHtubRCCOyGI5Aj5TSCf87Bw6sdomEq5QbTpGryWDac9 memorysize: 375.61 MB gid: root partitions: sda1: size: 497664 filesystem: ext2 uuid: c5e32508-1e4b-4a83-abc8-8f7bf3f9223f mount: /boot sda2: size: 2 sda5: size: 20262912 filesystem: LVM2_member rubyversion: 1.8.7 ipaddress: 10.0.2.15 mtu_eth0: 1500 memoryfree_mb: 341.07 os: name: Debian lsb: minordistrelease: 0 majdistrelease: 6 distdescription: Debian GNU/Linux 6.0.7 (squeeze) distid: Debian distrelease: 6.0.7 distcodename: squeeze family: Debian release: major: 6 full: 6.0.7 minor: 0 network_lo: 127.0.0.0 physicalprocessorcount: 1 bios_release_date: 12/01/2006 boardproductname: VirtualBox lsbdistid: Debian lsbdistdescription: Debian GNU/Linux 6.0.7 (squeeze) swapsize: 455.99 MB processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz blockdevice_sda_vendor: ATA blockdevice_sr1_model: CD-ROM swapfree_mb: 455.99 blockdevice_sda_model: VBOX HARDDISK architecture:
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Debian 7: processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz count: 1 physicalcount: 1 kernel: Linux architecture: i386 hardwaremodel: i686 operatingsystem: Debian os: name: Debian family: Debian release: major: '7' minor: '0' full: '7.0' lsb: distcodename: wheezy distid: Debian distdescription: Debian GNU/Linux 7.0 (wheezy) distrelease: '7.0' majdistrelease: '7' minordistrelease: '0' processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount: '1' kernelrelease: 3.2.0-4-686-pae rubyversion: 1.9.3 hardwareisa: unknown ipaddress: 10.0.2.15 facterversion: 2.2.0 memorysize: 375.34 MB memoryfree: 343.61 MB swapsize: 456.00 MB swapfree: 456.00 MB swapsize_mb: '456.00' swapfree_mb: '456.00' memorysize_mb: '375.34' memoryfree_mb: '343.61' netmask: 255.255.255.0 uniqueid: 007f0101 gid: root lsbdistdescription: Debian GNU/Linux 7.0 (wheezy) selinux: 'false' lsbdistcodename: wheezy ps: ps -ef kernelversion: 3.2.0 lsbdistid: Debian kernelmajversion: '3.2' uptime_seconds: 55 lsbmajdistrelease: '7' operatingsystemrelease: '7.0' fqdn: debian-7-i386.vagrantup.com lsbdistrelease: '7.0' physicalprocessorcount: '1' uptime_hours: 0 interfaces: eth0,lo ipaddress_eth0: 10.0.2.15 macaddress_eth0: 08:00:27:7c:ea:12 netmask_eth0: 255.255.255.0 mtu_eth0: '1500' ipaddress_lo: 127.0.0.1 netmask_lo: 255.0.0.0 mtu_lo: '16436' osfamily: Debian lsbminordistrelease: '0' domain: vagrantup.com hostname: debian-7-i386 uptime: 0:00 hours path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin system_uptime: seconds: 55 hours: 0 days: 0 uptime: 0:00 hours sshdsakey: B3NzaC1kc3MAAACBAI2OsI8BNQK2qMDbuVZjiPRlIjh5I5DZWcV2Z05bS8Q+ni5GD/ZDa1SANaQecrNVo6y3RIpL8Uo7Prhl8mR8+uWh+kvGRPu0lhTpWhptiiAeqti0ch9WmhD+tjVczrAV6m3Tt7xiYN3Nq0e4sVHmZi0GWqT6bxEWTC0ZAm5WoJQRFQCJrPr3aIOQDABg/wbQOfZ4eZlziwAAAIAOgpGUgAWBjeT/KfHHNvB8leBlcMemWccx9VaUE32+5olWe4apPbZXKqyEnNvR9dgoK7r5HlgbKqnP4u0PYV+PS47uEMy7IwVB+b2c3kWc3AiBryeWMxb4uQLvYvpxu4/mVkIWix0G8xgo6DnueMks6OF03Tw5zzKkO0QmPE6IHgAAAIAeIjtBDcckLCRlNrQ36VwpJvUYd+zVe/4FsMecU6FN6J8wQ61MCnNbwB2UGVqNcR0AWSMCeJwYosSTMkEWeBV+/cs4yWteAee/slGBudC+HJxMYBHvbfjNSwJs9m/Z1WS517Lf8tWaSwbfFahdrVTWxYpLfAZt2QzxFKGpLESEKw== sshfp_dsa: ! 'SSHFP 2 1 204b51330d83ec15c3ed522692ac10f70a7c072f SSHFP 2 2 0920fe3e886fa5703969635615e117ebdaed21624d3d402956161337b722ed33' sshrsakey: B3NzaC1yc2EDAQABAAABAQCpRpNCshDHQoTYCv0azEdzpPoVVNqb44WJKtqs8WY75p+bp7hdmWRhKLN1a/ySsb1iObBTMO/w5wkBRg6UNUhfdsdYs4dg/hhjQGLRT9aXSNCCkDkgdSKO6PtRo+5WiMxIjnw2J4g9FLKh/M5rR+J58Mqd7jYGCdqUwhYw6ymfNk+B64mdd/CS9H/WqSpNl9eSLPUjteKgcMdm+o8V9u0iIC55/7eC6HSbJ824hNSv0JHaN3TFohbGddKAkFhZSS1igh3iKHGtXEwzrRkUYRdvTdEGKJgJiWvQylL/dDyc7qI5//h1uY2sU454KaEHJmq4FI5DJNCLEXTJwsVx9nTf sshfp_rsa: ! 'SSHFP 1 1 6b2284770b39a525d6021b4a2b30e332762f115d SSHFP 1 2 26e33eabe0e8bcfdb538a99b9fba436fece8324f6a1e9f807c4d2a6bbd0e3da0' sshecdsakey: E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBJgtJl/IlHw74EqnSFT2xQRMZv2SHUogpIXN96GxxHfsx2x4TuZPHNrmmccp9u2MW3kpcWZzjLT552WPOiiQEW8= sshfp_ecdsa: ! 'SSHFP 3 1 2a365770ea6fd069c3c1f8b0b4b86c88b6b6b92a SSHFP 3 2 9a1dc83a76acef199fb765f24b194aecb8f6fc00e1ab7075d1562e119bed49b3' virtual: virtualbox is_virtual: 'true' uptime_days: 0 filesystems: ext2,ext3 boardmanufacturer: Oracle Corporation boardproductname: VirtualBox boardserialnumber: '0' bios_vendor: innotek GmbH bios_version: VirtualBox bios_release_date: 12/01/2006 manufacturer: innotek GmbH productname: VirtualBox serialnumber: '0' uuid: 36B62114-9C32-4681-BB2E-CE64D928F993 type: Other macaddress: 08:00:27:7c:ea:12 partitions: sda1: uuid: 3a907488-8406-4b75-b7fd-4910b63955d7 size: '497664' mount: /boot
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Working on Fedora 20. Add Comment Facter / FACT-672 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-672) Smoke test packages
Title: Message Title Adrien Thebo commented on an issue Re: Smoke test packages Fedora 20 looks good: --- kernel: Linux network_eth0: 10.0.2.0 network_lo: 127.0.0.0 ipaddress: 10.0.2.15 gid: root hardwaremodel: i686 hardwareisa: i686 timezone: EDT operatingsystemmajrelease: '20' netmask: 255.255.255.0 kernelrelease: 3.11.10-301.fc20.i686+PAE boardmanufacturer: Oracle Corporation boardproductname: VirtualBox boardserialnumber: '0' bios_vendor: innotek GmbH bios_version: VirtualBox bios_release_date: 12/01/2006 manufacturer: innotek GmbH productname: VirtualBox serialnumber: '0' uuid: 2EAEE2C0-2650-4F7F-8CE5-DD8AE4BCDF75 type: Other osfamily: RedHat fqdn: localhost.corp.puppetlabs.net uptime_days: 0 uptime_hours: 0 architecture: i386 hostname: localhost dhcp_servers: system: 10.0.2.2 eth0: 10.0.2.2 operatingsystem: Fedora uptime: 0:09 hours physicalprocessorcount: '1' path: /sbin:/bin:/usr/sbin:/usr/bin partitions: sda1: uuid: 0a1ed8a0-8a2e-41a2-849b-1c321b3243ec size: '1024000' mount: /boot filesystem: ext4 sda2: size: '19740672' filesystem: LVM2_member system_uptime: seconds: 583 hours: 0 days: 0 uptime: 0:09 hours uptime_seconds: 583 id: root ps: ps -ef virtual: virtualbox is_virtual: 'true' os: name: Fedora family: RedHat release: major: '20' full: '20' facterversion: 2.2.0 processors: models: - Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz count: 1 physicalcount: 1 selinux: 'true' selinux_enforced: 'true' selinux_policyversion: '28' selinux_current_mode: enforcing selinux_config_mode: enforcing selinux_config_policy: unknown rubysitedir: /usr/local/share/ruby/site_ruby/ memorysize: 496.50 MB memoryfree: 429.02 MB swapsize: 1.03 GB swapfree: 1.03 GB swapsize_mb: '1056.00' swapfree_mb: '1055.33' memorysize_mb: '496.50' memoryfree_mb: '429.02' processor0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz processorcount: '1' interfaces: eth0,lo ipaddress_eth0: 10.0.2.15 macaddress_eth0: 08:00:27:44:20:78 netmask_eth0: 255.255.255.0 mtu_eth0: '1500' ipaddress_lo: 127.0.0.1 netmask_lo: 255.0.0.0 mtu_lo: '65536' sshrsakey: B3NzaC1yc2EDAQABAAABAQDKqJFWNKQmmshrV2ZKbUoekdtlZjGTOBBsvcQUFxcVrTNBwOFBJXQWHyXcNYIwazr+wB649FViSj+fgCKxJJbGCcZQEUP3V7seQ6uXSefOsU294HONIOib4S+BjSbaZQ4Tixb6RQu8ux+Zyn/oJxDeEJnzkWJ5lbJAGlN2DIff4VF5cjeU1O0zOB0ZJ835Rnafzj3JyqGTiSLsqMYT27rff+xqY9Kd/uy61FH+9U0NAEFYmYmLs3yEef2rFB/J30ffWmaR+IYhmHJt8HuIsZJVyL6yXVCusSaan+541CSD3C7vw/i2U4b+eThctZfIrDsH1VwO5WEe2eDffGh3 sshfp_rsa: |- SSHFP 1 1 4f8a53b8a58061b0214a1f2d2df3b6c8254be91b SSHFP 1 2 6c753b2ce41423710ac8651706271c9b579ddb601659cca8e4b20cc47e647b34 sshecdsakey: E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBMkJcCXopEddEE7gljnkPwsrn65PEiMyzRLmNGB80oedzCctGK9JEJplHfhHySjjFzvPS4+ZpV7Tjqf6Q6NmLS4= sshfp_ecdsa: |- SSHFP 3 1 9a464815b13899a64bd03168fb553263d7de6f57 SSHFP 3 2 a6bb4a1261612f165496dd02ea6cf26a436af20ad4f965e3a29770772eea59e7 kernelmajversion: '3.11' operatingsystemrelease: '20' macaddress: 08:00:27:44:20:78 uniqueid: 007f0100 kernelversion: 3.11.10 blockdevice_sda_size: 10632560640 blockdevice_sda_vendor: ATA blockdevice_sda_model: VBOX HARDDISK blockdevice_sr0_size: 1073741312 blockdevice_sr0_vendor: VBOX blockdevice_sr0_model: CD-ROM blockdevice_sr1_size: 1073741312 blockdevice_sr1_vendor: VBOX blockdevice_sr1_model: CD-ROM blockdevices: sda,sr0,sr1 domain: corp.puppetlabs.net filesystems: ext2,ext3,ext4 rubyversion: 2.0.0
Jira (FACT-672) Smoke test packages
Title: Message Title
Adrien Thebo commented on an issue
Re: Smoke test packages
CentOS 5:
[root@localhost ~]# facter
architecture = i386
bios_release_date = 12/01/2006
bios_vendor = innotek GmbH
bios_version = VirtualBox
blockdevice_hda_size = 4294965248
blockdevice_hdc_size = 4294965248
blockdevice_sda_model = VBOX HARDDISK
blockdevice_sda_size = 10632560640
blockdevice_sda_vendor = ATA
blockdevices = hda,hdc,sda
boardmanufacturer = Oracle Corporation
boardproductname = VirtualBox
boardserialnumber = 0
domain = localdomain
facterversion = 2.2.0
filesystems = ext2,ext3,iso9660
fqdn = localhost.localdomain
gid = root
hardwareisa = i686
hardwaremodel = i686
hostname = localhost
id = root
interfaces = eth0,lo,sit0
ipaddress = 10.0.2.15
ipaddress_eth0 = 10.0.2.15
ipaddress_lo = 127.0.0.1
is_virtual = true
kernel = Linux
kernelmajversion = 2.6
kernelrelease = 2.6.18-348.el5
kernelversion = 2.6.18
macaddress = 08:00:27:14:DC:79
macaddress_eth0 = 08:00:27:14:DC:79
manufacturer = innotek GmbH
memoryfree = 295.23 MB
memoryfree_mb = 295.23
memorysize = 375.80 MB
memorysize_mb = 375.80
mtu_eth0 = 1500
mtu_lo = 16436
mtu_sit0 = 1480
netmask = 255.255.255.0
netmask_eth0 = 255.255.255.0
netmask_lo = 255.0.0.0
network_eth0 = 10.0.2.0
network_lo = 127.0.0.0
operatingsystem = CentOS
operatingsystemmajrelease = 5
operatingsystemrelease = 5.9
os = {release={full=5.9, minor=9, major=5}, family=RedHat, name=CentOS}
osfamily = RedHat
partitions = {sda2={size=20547135}, sda1={mount=/boot, filesystem=ext3, uuid=3dde0328-bc0f-4377-ad37-a7427ef8bc04, size=208782}}
path = /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/vagrant/bin
physicalprocessorcount = 1
processor0 = Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
processorcount = 1
processors = {physicalcount=1, count=1, models=[Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz]}
productname = VirtualBox
ps = ps -ef
rubysitedir = /usr/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
selinux = true
selinux_config_mode = enforcing
selinux_config_policy = targeted
selinux_current_mode = enforcing
selinux_enforced = true
selinux_policyversion = 21
serialnumber = 0
sshdsakey = B3NzaC1kc3MAAACBAKKhiPVK4t/rviwOHlRJglVybmwqmX710PsNh0/GjSj1Xl7i9WXBAUSyH01gTF70cmYDVlBsYK97n+yH4tBysavWJCweSYsCmoWAoIAnAxy0PkxfnvbdC8r1r7TIjqzYDctBFJlxDQJJbxP3pzPbiwoFQMuWYPg4ecWJCbAK1N2xFQChUyFqqu5EmmExX96rJSygMyDAtQAAAIEAliPF89Nmc10RGr8JMSPfiudEYJqkNRyWtEFXuS/7N9F8AWT4pWBQ0O/Tv5c6xPPFXoLaa/yl9Ht5v2ojmjhFyZzkgZt8BTKkd8PMUIDrTZteHGNC+p+XlWJsdVx1qmWAziqPx2ZqEQI7J5tmEc/qtpESO4GXPYbNlsCFpa/yy8gAAACAUCFlM7PurckeAee02QvJdxpDt/Za6AsHjn5IPwHLcujbFs0gD/fzjahTeVemv5upXqqVzqScbDkCTUyHlsjlYjWQZo9J+Vm0r81D6SxpGoseX3LoZmzllkWFVa2Oa/V9XqhxNcIbc3k065nXGwII5AxGQu5RZcmcqmwEL4oo5f4=
sshfp_dsa = SSHFP 2 1 d1efc678ce197de277448223eece233ddab1af2c
SSHFP 2 2 3f0a524896a8321895ca0e2d720081b407f42215d1784132502c9cdd8067fc22
sshfp_rsa = SSHFP 1 1 64ad22ccadfe518d06e9ed5ddcc99b958b153c8d
SSHFP 1 2 7de57c080e5ff6e0686283e5894fd9c11b85eea68d3ce0c359d64121d2a072ad
sshrsakey = B3NzaC1yc2EBIwAAAQEAnIJGJqJJbLnH7Lo4vNsRzasgyHOTeEfQPn7hdCq8RLt/R239VQe/P/82F2o0VWC5JgxzqsJjSFU/jzeP/ZA8UTSM8VXtwy7dwxdwp5XcAQfOthX8BParoEgKYoZ5DPs7B7ytiO91Em5euTT2L8Xz1Sum6HPTft4BxqJ4FD1VIOKwwMb6+gLT2gsbrDKx+IYyu9iJtbrm145q+3iLGPMFXdf+sdYb5nCu1E61R7dKyk5P/wqkco8ttxar3sTDqhZhvEsjF/Q216DpNzzmF139e+l0VotCd0dyepJBPXp0m/2qpNilNx8blSQ1d8Wkh+7O4HlxoiElDBkj+WrFuHJiFw==
swapfree = 1.03 GB
swapfree_mb = 1055.99
swapsize = 1.03 GB
swapsize_mb = 1055.99
system_uptime = {days=0, hours=0, uptime=0:05 hours, seconds=301}
timezone = PDT
type = Other
uniqueid = 007f0100
uptime = 0:05 hours
uptime_days = 0
uptime_hours = 0
uptime_seconds = 301
uuid = 16499068-E2E8-413D-9FB8-6057DEA016F0
virtual = virtualbox
Jira (FACT-672) Smoke test packages
Title: Message Title
Adrien Thebo commented on an issue
Re: Smoke test packages
Solaris 10:
architecture = i86pc
bios_release_date = 12/01/2006
bios_vendor = innotek GmbH
bios_version = 1.2
domain = corp.puppetlabs.net
facterversion = 2.2.0
fqdn = solaris-10u11-i386-vbox4210-nocm.corp.puppetlabs.net
gid =
hardwareisa = i386
hardwaremodel = i86pc
hostname = solaris-10u11-i386-vbox4210-nocm
id = root
interfaces = lo0,e1000g0
ipaddress = 10.0.2.15
ipaddress_e1000g0 = 10.0.2.15
ipaddress_lo0 = 127.0.0.1
is_virtual = true
kernel = SunOS
kernelmajversion = Generic_147148-26
kernelrelease = 5.10
kernelversion = Generic_147148-26
macaddress = 08:00:27:b8:fd:d1
macaddress_e1000g0 = 08:00:27:b8:fd:d1
manufacturer = innotek GmbH
memoryfree = 540.69 MB
memoryfree_mb = 540.69
memorysize = 768.00 MB
memorysize_mb = 768.00
mtu_e1000g0 = 1500
mtu_lo0 = 8232
netmask = 255.255.255.0
netmask_e1000g0 = 255.255.255.0
netmask_lo0 = 255.0.0.0
network_e1000g0 = 10.0.2.0
network_lo0 = 127.0.0.0
operatingsystem = Solaris
operatingsystemmajrelease = 10_u11
operatingsystemrelease = 10_u11
os = {name=Solaris, family=Solaris, release={major=10_u11, full=10_u11}}
osfamily = Solaris
path = /opt/csw/bin:/usr/sbin:/usr/bin:/usr/ucb
physicalprocessorcount = 1
processor0 = Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz
processorcount = 1
processors = {models=[Intel(r) Core(tm) i7-3520M CPU @ 2.90GHz], physicalcount=1, count=1}
productname = VirtualBox
ps = ps -ef
rubysitedir = /opt/csw/lib/ruby/site_ruby/1.8
rubyversion = 1.8.7
serialnumber = 0
sshdsakey = B3NzaC1kc3MAAACBAPKE7MH3vAlt8pLc4SaLX17wZsYHQsDhjtL34mGNEj5pkMhDgsAW+FYP6ZxelVeqrCRtg2OhIJafbzOzaPtAhAiChLbPKGPj/TD6tp8SswhDICZVv0Qypa8+LwpLPfrRzFcOWNchzc60UsO32gm7jKz6AnJFR4X9+zVjf08GP1zHFQDRSsTO2HeXm6Uk2vR8QjYtDlD+VQAAAIBtEMq+kGJhu7K6IuPE9Za032cypwXceuQa5kC5Pjq0a1JYRFQu5o1EOF8iBK+GCSaQiw/3dKwwGzAqwVBzP7fkkBlCltg4hmMFIN/apRWimEYZ5cnzkTsSA/ei46farQusCCQyvLjHwHGytY5W6+M6V0uu/zC8CWyouiTeI3ALzQAAAIEAkwW5Zb9GPL3ChezElANl6JPp9SVdQuK4OMfz+KiDkTniKViboOYVk3fw7BSquCawrx4P4zMvl0/BYzjgY3MXovE7WPIWiYBymjSwMFqKwNC796zGFJTIZAA+57UCIRvfi3w3TC3lijYOZz3xoR9cCE5culcA1O6dHwe+E7bPLmg=
sshfp_dsa = SSHFP 2 1 25a3c71a6026fe985e68e59563082b9aa9345067
SSHFP 2 2 92f67d668778ae15f10cfa1a162b73e2de8aaf7fe762875fd92ba113e994acaf
sshfp_rsa = SSHFP 1 1 b09a53331e31234bd8f142605376caafaed4adee
SSHFP 1 2 97733b4cfa5a467da3ae03a34eec05b46420d4dec9d141f0cd2cf6a117a768d1
sshrsakey = B3NzaC1yc2EBIwAAAIEAnIFUhzpTYkJFYp1V1aRL0Il34QkXwQwio42dSon2v6HuJW0lSkEBu13Mbl3O4vqIwz1fe9JZ3JQpIXHt7ehRxpdd6Sl8PpgCLJ5nmKX6LWFXZ8ZRQPsxhObXnYDgYByXdArRDGb/sdxTGuF8wIDAQpE+PGZb28EW7aee05o7o9U=
swapfree = 1.00 GB
swapfree_mb = 1027.59
swapsize = 1.00 GB
swapsize_mb = 1027.59
system_uptime = {seconds=4020, days=0, hours=1, uptime=1:07 hours}
timezone = BST
type = 0x1 (other)
uniqueid = 187a449e
uptime = 1:07 hours
uptime_days = 0
uptime_hours = 1
uptime_seconds = 4020
uuid = 5ca01b88-de80-47a7-8191-876aec5a7411
virtual = virtualbox
zfs_version = 5
zonename = global
zones = 0
zpool_version = 32
Add Comment
Jira (FACT-679) Close all resolved tickets in Jira
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-679 Close all resolved tickets in Jira Change By: Adrien Thebo Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-678) Send out announcements
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-678 Send out announcements Change By: Adrien Thebo Assignee: EricSorenson AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3092) Json lib issue when installing Puppet on RHEL 7
Title: Message Title Adrien Thebo commented on an issue Re: Json lib issue when installing Puppet on RHEL 7 PUP-2940 looks very similar to the errors that you're seeing; are you using rvm or have you done anything like `gem update --system` ? Add Comment Puppet / PUP-3092 Json lib issue when installing Puppet on RHEL 7 Installed: puppet.noarch 0:3.6.2-1.el7 Dependency Installed: hiera.noarch 0:1.3.4-1.el7 Complete! When i run this command, it gives an error on json lib version 1.7.7 [ec2-user@ip-172-31-11-15 installers]$ puppet -version /usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- json/p... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Adrien Thebo commented on an issue Re: Deprecate non-string modes on file type Merged in 87b0b5d. Add Comment Puppet / PUP-2349 Deprecate non-string modes on file type The future parser treats literal numbers as actual numbers instead of strings as the old parser did. This makes file resources that use unquoted mode values behave strangely (see PUP-2156). In order to provide a good experience and still have numbers be numbers in the language, the mode parameter of file resources needs to issue a deprecation warning f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-614 Create structured operating system fact Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Adrien Thebo commented on an issue Re: Puppet searches disk for whit classes Merged GH-2979 in 69310a8. Add Comment Puppet / PUP-2924 Puppet searches disk for whit classes Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat(/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/modules/admin/lib/puppet/type/completed_stage This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-614) Create structured operating system fact
Title: Message Title
Adrien Thebo commented on an issue
Re: Create structured operating system fact
Merged in c0812a8.
Add Comment
Facter / FACT-614
Create structured operating system fact
Currently, there are several facts related to operating system based data, including: {noformat} operatingsystem operatingsystemmajrelease operatingsystemrelease osfamily {noformat} Also, there are a handful of lsb* facts for Linux systems, including: {noformat} lsbdistcodename lsbdistdescription lsbdistid lsbdistrelease lsbmajdistrele...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-659) Partitions fact does not correctly parse the filesystem attribute under Linux
Title: Message Title
Adrien Thebo commented on an issue
Re: Partitions fact does not correctly parse the filesystem attribute under Linux
Merged in c1cc408.
Add Comment
Facter / FACT-659
Partitions fact does not correctly parse the filesystem attribute under Linux
{code} $ be facter partitions -y --- partitions: sda1: size: '1953523087' filesystem: ntfs PARTUUID=d3676ebb-1343-4bac-9521-6bdd9bb2f7db sdb1: size: '2014' sdb2: uuid: e746c990-fb8d-4449-90ad-c517ccd859f6 size: '204800' mount: /boot filesystem: ext2 PARTLABEL=Linux filesystem PARTUUID=a9ddc9e2-adf2-4134...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title
Adrien Thebo commented on an issue
Re: User provider password_max_age attribute is flawed under Solaris
Verified:
Against 3.6.2:
bash-3.2# bundle exec puppet apply /foo.pp --verbose
Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.32 seconds
Info: Applying configuration version '1408395629'
Notice: /Stage[main]/Main/User[vagrant]/password_max_age: password_max_age changed '' to '-1'
Notice: Finished catalog run in 0.22 seconds
Against 9953b2c67009013894dcd0bcd5fb11409be16f02:
bash-3.2# bundle exec puppet apply /foo.pp --verbose
Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.44 seconds
Info: Applying configuration version '1408395694'
Notice: Finished catalog run in 0.11 seconds
Add Comment
Puppet / PUP-229
User provider password_max_age attribute is flawed under Solaris
A user reported this, and did an excellent write up of the issue and a possible fix, so I'm just going to paste that: The password_max_age logic is flawed on Solaris. At first, it seems to work: {noformat} # tail -1 /etc/passwd foobar:x:911:911::/home/foobar:/bin/sh # tail -1 /etc/shadow foobar:GI2XGzW0DitJk:15931::182:28::: {noformat} E...
Jira (FACT-659) Partitions fact does not correctly parse the filesystem attribute under Linux
Title: Message Title
Adrien Thebo commented on an issue
Re: Partitions fact does not correctly parse the filesystem attribute under Linux
Verified:
Against 19b8b2d:
---
partitions:
sda1:
uuid: 7de786a9-be75-4711-b782-fb26aec963d4
size: '1024000'
mount: /boot
sda2:
size: '975747072'
filesystem: LVM2_member PARTUUID=000443ef-02
sda3:
size: '2047'
Against c1cc408f:
---
partitions:
sda1:
uuid: 7de786a9-be75-4711-b782-fb26aec963d4
size: '1024000'
mount: /boot
sda2:
size: '975747072'
filesystem: LVM2_member
sda3:
size: '2047'
Add Comment
Facter / FACT-659
Partitions fact does not correctly parse the filesystem attribute under Linux
{code} $ be facter partitions -y --- partitions: sda1: size: '1953523087' filesystem: ntfs PARTUUID=d3676ebb-1343-4bac-9521-6bdd9bb2f7db sdb1: size: '2014' sdb2: uuid: e746c990-fb8d-4449-90ad-c517ccd859f6 size: '204800' mount: /boot filesystem: ext2 PARTLABEL=Linux filesystem PARTUUID=a9ddc9e2-adf2-4134...
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title
Adrien Thebo commented on an issue
Re: Regression when pluginsyncing external facts on Windows
Verified that pluginsync on Windows running against master no longer logs a warning.
Add Comment
Puppet / PUP-2907
Regression when pluginsyncing external facts on Windows
Ticket PUP-2705 restored the ability for pluginsync to preserve permissions for external facts synced to {{facts.d}}. However, on Windows, it generates a deprecation warning, which users cannot fix: {noformat} C:\work\puppet bundle exec puppet agent -t ... Info: Retrieving pluginfacts Warning: Copying owner/mode/group from the source file on Windo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title
Adrien Thebo commented on an issue
Re: Puppet searches disk for whit classes
Verified:
On 3.6.2:
strace -o strace.out -e trace=stat -- bundle exec puppet apply -e 'notify { hello: message = world }'; echo Admissible:; grep -c admissible strace.out ; echo Completed:; grep -c completed strace.out
Unable to open /dev/zfs: Permission denied.
Unable to open /dev/zfs: Permission denied.
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.03 seconds
Notice: world
Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'world'
Notice: Finished catalog run in 0.18 seconds
Admissible:
648
Completed:
648
On master (dbf3021):
strace -o strace.out -e trace=stat -- bundle exec puppet apply -e 'notify { hello: message = world }'; echo Admissible:; grep -c admissible strace.out ; echo Completed:; grep -c completed strace.out
Unable to open /dev/zfs: Permission denied.
Unable to open /dev/zfs: Permission denied.
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.02 seconds
Notice: world
Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'world'
Notice: Finished catalog run in 0.13 seconds
Admissible:
0
Completed:
0
For this trivial example it looks like catalog application time is roughly the same.
Add Comment
Puppet / PUP-2924
Puppet searches disk for whit classes
Our Puppet instance has
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1527 After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera Change By: Adrien Thebo 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-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Adrien Thebo commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Merged into master in 9953b2c.
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Adrien Thebo commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Nicholas Fagerlund non-string values.
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2623) non-environment setup required
Title: Message Title Adrien Thebo commented on an issue Re: non-environment setup required Puppet has been using environments under the hood for a very long time. In the no environment state before 3.5 and 3.6, you were using the production environment by default, and it happened to not include the environment name in the modulepath and related setting. In 3.6 + it just happens that this default environment is now part of the path and is less hidden. Using /etc/puppet/environments/production/modules is entirely equivalent to using /etc/puppet/modules in that in each case, that path is the modulepath for that specific environment. The directory environments in 3.6 doesn't force you to use environments more than you already have been; it just means that the paths move around a little bit. Add Comment Puppet / PUP-2623 non-environment setup required Hi everyone, with 3.6, puppet started to deprecate the concept of non-environment setups by throwing warnings about a few config-settings and by announcing to remove this kind of setup in future. I am the creator and admin of some kind of multi-master setup, with hiera as the fundamental database. My puppet manifests/modules solely contain funct... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title
Adrien Thebo commented on an issue
Re: Boolean facts not printed with facter -p if fact value is false
Martin Westergaard Lassen Non-string fact values in Facter 1.7 were not supported and 1.7.x is only receiving security updates, so we will not be backporting this into 1.7.x.
Add Comment
Facter / FACT-627
Boolean facts not printed with facter -p if fact value is false
Boolean facts are not printed with facter -p if the fact value is false. Example (using a custom fact): {noformat} [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = true [root@cxdrun01 ~]# facter -p is_cde true # fiddle the is_cde fact to be false here [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = false [root@cxdrun01 ~]# facter -p i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (PUP-2908) service provider should default to upstart in RHEL6 and greater
Title: Message Title Adrien Thebo commented on an issue Re: service provider should default to upstart in RHEL6 and greater It looks like this issue update was marked as spam and I never saw it. I don't know of many people that took advantage of Upstart support in Redhat 6, and in addition the Upstart support for Redhat in Puppet was done in a very limited fashion. To make this the default we would need to more thoroughly rework the Upstart provider (specifically it would need to be refactored to not always inherit from the Debian service provider) which would be nontrivial. Since not a lot of people ever took advantage of Upstart on Redhat 6 I don't think we should take this on, but if a community member felt like stepping up I think we could merge a pull request that did this in a complete and backwards compatible manner. Add Comment Puppet / PUP-2908 service provider should default to upstart in RHEL6 and greater In RHEL6, init was replaced with upstart. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html In puppet, when osfamily = redhat,suse, the provider for the service type defaults to the redhat type, which uses chkconfig. http://docs.puppetlabs.com/references/latest/type.html#service-provider... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Adrien Thebo commented on an issue
Re: native, deep, or deeper merge not working as expected
You're not seeing the data merged in because the node/%{::fqdn} variable isn't being set. If we do a normal priority lookup and the lookup was working, we should see the node specific value but we don't:
[vagrant@centos65 ~]$ hiera -c /vagrant/puppet/hiera.yaml mymodule::options
{param1=param1,
param2=param2,
param3=param3,
param4=param4,
nested=
{param1=nested_param1,
param2=nested_param2,
param3=nested_param3,
param4=nested_param4}}
This is because the ::fqdn variable isn't set. If we specify that on the command line as part of the scope we get the correct priority lookup:
[vagrant@centos65 ~]$ hiera -c /vagrant/puppet/hiera.yaml mymodule::options ::fqdn=centos65.vm.local
{nested={param4=new_nested_param4}}
And if we do that lookup with the scope and use a hash lookup, we see the deep merge occurring:
{nested=
{param1=nested_param1,
param2=nested_param2,
param3=nested_param3,
param4=new_nested_param4},
param1=param1,
param2=param2,
param3=param3,
param4=param4}
When running hiera on the commandline, there is no scope set up by default.
Since you're using a fully qualified variable name we can't directly dump the output of Facter and use it as the scope, but if you change ::fqdn to fqdn then you can use Facter as the scope input:
---
:backends:
- yaml
:hierarchy: - nodes/%{fqdn} # Note the omitted double colon
- common
:yaml:
:datadir: /vagrant/puppet/hieradata
:merge_behavior: deeper
[vagrant@centos65 ~]$ facter -y scope.yaml
[vagrant@centos65 ~]$ hiera --hash -c /vagrant/puppet/hiera.yaml --yaml scope.yaml mymodule::options
{nested=
{param1=nested_param1,
param2=nested_param2,
param3=nested_param3,
param4=new_nested_param4},
param1=param1,
param2=param2,
param3=param3,
param4=param4}
Add Comment
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title Adrien Thebo updated an issue Hiera / HI-283 native, deep, or deeper merge not working as expected Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title Adrien Thebo updated an issue Hiera / HI-283 native, deep, or deeper merge not working as expected Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Adrien Thebo commented on an issue
Re: native, deep, or deeper merge not working as expected
When you use data binding for variable lookups, Puppet can only use the priority lookup type. If you want to use the hash lookup, you have to directly invoke hiera_hash:
diff --git a/puppet/modules/mymodule/manifests/init.pp b/puppet/modules/mymodule/manifests/init.pp
index f96be37..76dae0d 100644
--- a/puppet/modules/mymodule/manifests/init.pp
+++ b/puppet/modules/mymodule/manifests/init.pp
@@ -2,10 +2,9 @@
class mymodule (
$template = undef,
- $options = undef,
#$options = hiera('$options', undef),
- #$options = hiera_hash('$options', undef),
){
+ $options = hiera_hash('mymodule::options', undef)
file { mymodule_config:
path= '/tmp/mymodule.conf',
[vagrant@centos65 vagrant]$ sudo puppet apply --modulepath puppet/modules --hiera_config puppet/hiera.yaml --fileserverconfig fileserver.conf -e 'include mymodule' --verbose
Notice: Compiled catalog for centos65.vm.local in environment production in 0.10 seconds
Info: Applying configuration version '1407519056'
Info: /Stage[main]/Mymodule/File[mymodule_config]: Filebucketed /tmp/mymodule.conf to puppet with sum 256bb409e0cadfb4b7cfe9278643d3b6
Notice: /Stage[main]/Mymodule/File[mymodule_config]/content: content changed '{md5}256bb409e0cadfb4b7cfe9278643d3b6' to '{md5}b32b087e53c6c86b52f0a1fefef1c442'
Notice: Finished catalog run in 0.04 seconds
[vagrant@centos65 vagrant]$ cat /tmp/mymodule.conf
# This file is managed by Puppet. DO NOT EDIT.
These are my options:
param1 = param1
param2 = param2
param3 = param3
param4 = param4
nested =
param1 = nested_param1
param2 = nested_param2
param3 = nested_param3
param4 = new_nested_param4
Add Comment
Hiera / HI-283
native, deep, or deeper merge not working as expected
Jira (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Adrien Thebo commented on an issue Re: changes to ordering in custom facts breaks things When Facter runs, it tries to do so in two passes - the first pass loads fact files and should not actually evaluate facts, and the second pass actually evaluate facts. However, if you do something like this: # somefact.rb Facter.value(something) This forces the evaluation of something at load time, which can cause bad behaviors with loading. To avoid this, write your facts like so: Facter.add(some_fact_that_needs_something) do setcode do Facter.value(something) # ... end end This will prevent the something fact from being evaluated until after all facts have been loaded. Add Comment Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi...
Jira (PUP-1263) Synonyms (title, namevar, name) make it confusing.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1263 Synonyms (title, namevar, name) make it confusing. Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-605) facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts
Title: Message Title Adrien Thebo updated an issue Facter / FACT-605 facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts Change By: Adrien Thebo Assignee: AdrienThebo EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2368 using booleans result in unmanaged property Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-605) facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts
Title: Message Title Adrien Thebo updated an issue Facter / FACT-605 facter incorrectly filters localhost and link-local IPv6 addresses when creating interface-specific ipaddress6 facts Change By: Adrien Thebo Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-623) add BSD interface alias support
Title: Message Title Adrien Thebo updated an issue Facter / FACT-623 add BSD interface alias support Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title
Adrien Thebo commented on an issue
Re: FileUtils implementation broke compare_stream
Maksym Melnychok the issue is that the change made only affected non-Windows systems (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_system.rb#L9-L18), so if Windows was being used with Ruby 2.0 it would still use the Ruby 1.9 file implementation and thus wouldn't pick up the patched version of #compare_stream. I'm looking into the Ruby implementation to see if there is another way we can solve this issue without having to replace #compare_stream but it does look like the change made in https://github.com/ruby/ruby/commit/2142287c makes this very hard.
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you
Jira (PUP-2967) Remove recurse = inf
Title: Message Title Adrien Thebo commented on an issue Re: Remove recurse = inf Merged in 5d1e87d. Add Comment Puppet / PUP-2967 Remove recurse = inf This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-410) Add deprecation warnings for Facter 2.x
Title: Message Title Adrien Thebo commented on an issue Re: Add deprecation warnings for Facter 2.x It could; the Facter::Core::Execution methods that have stubs in Facter::Util::Resolution could be removed but it doesn't hurt anything if we have both. Add Comment Facter / FACT-410 Add deprecation warnings for Facter 2.x In Facter 2.0.1 a number of soft deprecations were added because existing behavior was undesired, but they were so heavily used that deprecating everything right away would spew tons of noise. In Facter 2.1 we should start adding deprecation notices to those methods. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3010) Allow Upstart jobs on Amazon Linux
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3010 Allow Upstart jobs on Amazon Linux Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-637) Add lsbminordistrelease fact
Title: Message Title Adrien Thebo updated an issue Facter / FACT-637 Add lsbminordistrelease fact Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2379) Deprecate `recurse = inf` for file type
Title: Message Title Adrien Thebo commented on an issue Re: Deprecate `recurse = inf` for file type Merged into master in c1f1c47. Add Comment Puppet / PUP-2379 Deprecate `recurse = inf` for file type This was an old synonym for `recurse = true`, but it only makes sense in a world where you can also set integer values for `recurse` instead of using `recurselimit`... which you can't do, anymore. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1527 After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Adrien Thebo commented on an issue Re: Puppet searches disk for whit classes Merged into master in cb26e23; this should be released in 3.7.0. Add Comment Puppet / PUP-2924 Puppet searches disk for whit classes Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat(/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/modules/admin/lib/puppet/type/completed_stage This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2995) Proposal for custom trusted oid mapping file
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2995 Proposal for custom trusted oid mapping file Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) incorrect header check using Ruby 2
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1680 incorrect header check using Ruby 2 Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title
Adrien Thebo commented on an issue
Re: FileUtils implementation broke compare_stream
Merged in 1a428b9.
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2946) FileUtils implementation broke compare_stream
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Adrien Thebo 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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Adrien Thebo commented on an issue
Re: FileUtils implementation broke compare_stream
Maksym Melnychok we have to back this change out due to spec failures on Windows; we'll need to revisit this tomorrow.
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2626 Accept module paths in Puppet::Parser::Functions.file() Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2626 Accept module paths in Puppet::Parser::Functions.file() Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title
Adrien Thebo commented on an issue
Re: Accept module paths in Puppet::Parser::Functions.file()
Verified with the following:
modules/module_file/manifests/init.pp
class module_file {
$notify_title = file(module_file/file.txt)
notify { $notify_title: }
}
modules/module_file/files/file.txt
yay
output
$ bundle exec puppet apply -e 'include module_file'
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds
Notice: yay
Notice: /Stage[main]/Module_file/Notify[yay
]/message: defined 'message' as 'yay
'
Notice: Finished catalog run in 0.13 seconds
Add Comment
Puppet / PUP-2626
Accept module paths in Puppet::Parser::Functions.file()
Allow template-style module path to be used instead of the absolute path in for the file() function. {noformat} file('example/file.ext') {noformat} would return the same as {noformat} file('/etc/puppet/modules/example/files/file.ext') {noformat}This is supposed to be like how template does module paths, where: {noformat} template('exam...
Jira (HI-281) Add YAML output format to CLI
Title: Message Title
Adrien Thebo commented on an issue
Re: Add YAML output format to CLI
Verified with the following:
hiera.yaml
:backends:
- yaml
:yaml:
:datadir: /home/adrien/.puppet/hiera
:hierarchy:
- common
hiera/common.yaml
---
foo: {bar: baz}
output:
hiera -c ~/.puppet/hiera.yaml -f yaml foo
---
bar: baz
Add Comment
Hiera / HI-281
Add YAML output format to CLI
* Author: Ahmet Demir ahmet2mir+git...@gmail.com * Github ID: [ahmet2mir|https://github.com/ahmet2mir] * [Pull Request 198 Discussion|https://github.com/puppetlabs/hiera/pull/198] * [Pull Request 198 File Diff|https://github.com/puppetlabs/hiera/pull/198/files] Just add YAML output to https://tickets.puppetlabs.com/browse/HI-129 I use hiera w...
Jira (FACT-597) facter needs a package dependency on net-tools on rhel7 for ifconfig
Title: Message Title Adrien Thebo commented on an issue Re: facter needs a package dependency on net-tools on rhel7 for ifconfig Verified on packages build from 08f54afd7ca4ef584e7bd9e416d4084be95e08d2: └ rpm -qpR facter-2.1.0.627-1.fc20.x86_64.rpm|grep net-tools net-tools ┌[adrien☮grey]-(~/development/scratch/facter) └ rpm -qpR facter-2.1.0.627-1.el7.x86_64.rpm|grep net-tools net-tools 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)
Jira (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title
Adrien Thebo commented on an issue
Re: Boolean facts not printed with facter -p if fact value is false
Verified with the following:
Facter.add(:falsey) do
setcode { false }
end
└ bundle exec facter falsey
false
┌[adrien☮grey]-(~/eng/projects/platform/facter)-[git://master ✗]-
└ bundle exec facter -j falsey
{
falsey: false
}
Add Comment
Facter / FACT-627
Boolean facts not printed with facter -p if fact value is false
Boolean facts are not printed with facter -p if the fact value is false. Example (using a custom fact): {noformat} [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = true [root@cxdrun01 ~]# facter -p is_cde true # fiddle the is_cde fact to be false here [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = false [root@cxdrun01 ~]# facter -p i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2953) masterlog setting is dead code
Title: Message Title Adrien Thebo commented on an issue Re: masterlog setting is dead code Merged in c78df2a. Add Comment Puppet / PUP-2953 masterlog setting is dead code http://docs.puppetlabs.com/references/latest/configuration.html#masterlog Where puppet master logs. This is generally not used, since syslog is the default log destination. If you ack the Puppet source, you'll see that this setting is never referenced by any other area of code. It's dead, Jim. (The similar puppetdlog setting -- http://docs.pupp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2953) masterlog setting is dead code
Title: Message Title
Adrien Thebo commented on an issue
Re: masterlog setting is dead code
Verified with the following:
bundle exec puppet apply --masterlog heh -e notice('hi')
Warning: Setting masterlog is deprecated.
(at /home/adrien/eng/projects/platform/puppet/lib/puppet/settings.rb:1109:in `issue_deprecation_warning')
Notice: Scope(Class[main]): hi
Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds
Notice: Finished catalog run in 0.12 seconds
└ git checkout puppet-4
Switched to branch 'puppet-4'
Your branch is up-to-date with 'upstream/puppet-4'.
└ bundle exec puppet apply --masterlog heh -e notice('hi')
Error: Could not parse application options: invalid option: --masterlog
Add Comment
Puppet / PUP-2953
masterlog setting is dead code
http://docs.puppetlabs.com/references/latest/configuration.html#masterlog Where puppet master logs. This is generally not used, since syslog is the default log destination. If you ack the Puppet source, you'll see that this setting is never referenced by any other area of code. It's dead, Jim. (The similar puppetdlog setting -- http://docs.pupp...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily Merged in ad80437. Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2952) Puppet should only log facts in debug mode
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2952 Puppet should only log facts in debug mode Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2952) Puppet should only log facts in debug mode
Title: Message Title
Adrien Thebo commented on an issue
Re: Puppet should only log facts in debug mode
Verified against b7ce5e6; when running puppet agent -t the agent does not list out the fact files being loaded.
Add Comment
Puppet / PUP-2952
Puppet should only log facts in debug mode
In environments with lots of facts puppet agent can fill the screen and log files with loading fact messages. This is only useful when debugging and should thus be only enabled when in debug mode. {code} rickon:~# puppet agent --test Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /v...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo commented on an issue Re: module skeleton is using deprecated way to configure spec_helper Merged in cd41e5f. Add Comment Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper [~josh] states that we are using a deprecated method for configuring rspec This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo commented on an issue Re: factor 2.1.0 errors out on Mavericks Could you run facter --trace and provide the output of that? Add Comment Facter / FACT-630 factor 2.1.0 errors out on Mavericks Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-630) facter 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 facter 2.1.0 errors out on Mavericks Change By: Adrien Thebo Summary: factor facter 2.1.0errorsoutonMavericks 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-629) ec2 facts should ignore proxy
Title: Message Title Adrien Thebo updated an issue Facter / FACT-629 ec2 facts should ignore proxy Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
