Jira (PUP-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Rakesh Kathpal commented on an issue Re: Undeprecate 'puppet kick' run mode The issue here is not just activemq.. but installing anything extra that needs more plugins/clients to be installed on the puppet agent node is an overhead. Add Comment Puppet / PUP-1135 Undeprecate 'puppet kick' run mode bq. Please not deprecate puppet kick. We use puppet in some our projects, and not use mcollective, also don’t plan use mcollective. Why? Mcollective is require mq (activemq/rabbitmq etc) and provides unneeded functionality. We can use one function from mcollective – puppet agent runonce, but why do we need to install extra software, and extra daemon on ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
Title: Message Title
Jrgen Weber commented on an issue
Re: java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
no I did not and yes, now after the restart it works great.
Add Comment
PuppetDB / PDB-686
java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
on puppet agent run: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace catalog' command for vagrant-tools01.intfd.local to PuppetDB at vagrant-tools01.intfd.local:8081: [500 java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 ms] htmlheadmeta http-equiv=Content-Type ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2634) source_permissions invalid option?
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2634
source_permissions invalid option?
Issue Type:
Bug
Assignee:
Unassigned
Created:
22/May/14 3:48 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
I just tried to set source_permissions on my default File resource: File { owner = 'S-1-5-18', group = 'Administrators', source_permissions = ignore }
But windows puppet agent v3.4.0-rc2 says: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter source_permissions at /etc/puppet/modules/nscp/manifests/init.pp:19
Add Comment
Jira (PUP-2634) source_permissions invalid option?
Title: Message Title
Cedef commented on an issue
Re: source_permissions invalid option?
Hi,
I have the same issue, using a puppet master 3.4.3 and a puppet agent 2.7.23 and when defining
manifests/site.pp
# File: manifests/site.pp
File {
owner = root
group = 0
source_permissions = ignore
}
Add Comment
Puppet / PUP-2634
source_permissions invalid option?
I just tried to set source_permissions on my default File resource: File { owner = 'S-1-5-18', group = 'Administrators', source_permissions = ignore } But windows puppet agent v3.4.0-rc2 says: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter source_permissions at /etc/puppet/modules/nscp/manifests/in...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Change By: Felix Frank Assignee: FelixFrank Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
Title: Message Title
Kenneth Barber commented on an issue
Re: java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
I've been able to replicate this on Ubuntu 12.04 using Ruby 1.9.3p0. This is an old release of Ruby 1.9.3, so I'm guessing its a bug in that ancient release.
Switching to Ruby 1.8.7 actually fixes the issue, so does installing the latest Ruby 1.9.3 from the brightbox repos.
We're going to try and work-around the bug in our terminus if possible. Stay tuned.
Add Comment
PuppetDB / PDB-686
java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
on puppet agent run: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace catalog' command for vagrant-tools01.intfd.local to PuppetDB at vagrant-tools01.intfd.local:8081: [500 java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 ms] htmlheadmeta http-equiv=Content-Type ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Doug Byrne created an issue
Puppet / PUP-2635
user purge_ssh_keys not purged
Issue Type:
Bug
Affects Versions:
3.6.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
22/May/14 8:01 AM
Environment:
Ubuntu 12.04
Priority:
Normal
Reporter:
Doug Byrne
I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys.
I've added this code to my manifest:
user { 'ubuntu': purge_ssh_keys = true, home = '/home/ubuntu', }
However, no keys are purged. I do see the following lines in the agent debug output:
Debug: /Stage[main]/Role::Search/Ssh_authorized_key[key2purge1]: Nothing to manage: no ensure and the resource doesn't exist Debug: /Stage[main]/Role::Search/Ssh_authorized_key[key2purge2]: Nothing to manage: no ensure and the resource doesn't exist
Those are the two keys that I expect would be purged. It appears that puppet has correctly identified the keys to purge, and
Jira (PUP-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2635
user purge_ssh_keys not purged
Change By:
Felix Frank
I'musingPuppet3.6.0onUbuntu12.04andI'mtryingtopurgeunmanagedsshauthorizedkeys.I'veaddedthiscodetomymanifest: {code} user{'ubuntu':purge_ssh_keys=true,home='/home/ubuntu',} {code} However,nokeysarepurged.Idoseethefollowinglinesintheagentdebugoutput: {noformat} Debug:/Stage[main]/Role::Search/Ssh_authorized_key[key2purge1]:Nothingtomanage:noensureandtheresourcedoesn'texistDebug:/Stage[main]/Role::Search/Ssh_authorized_key[key2purge2]:Nothingtomanage:noensureandtheresourcedoesn'texist {noformat} ThosearethetwokeysthatIexpectwouldbepurged.Itappearsthatpuppethascorrectlyidentifiedthekeystopurge,andcreatedresourcesforthem,butdidnotensure=absent.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
Title: Message Title
Kenneth Barber commented on an issue
Re: java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
Looks like this happens when the payload being submitted with Net::HTTP is bigger than 16384 bytes. Below that number its fine, above that number we see a timeout. There are other reports of this on the internet.
Add Comment
PuppetDB / PDB-686
java.util.concurrent.TimeoutException: Idle timeout expired since PDB 2.0.0
on puppet agent run: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace catalog' command for vagrant-tools01.intfd.local to PuppetDB at vagrant-tools01.intfd.local:8081: [500 java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 ms] htmlheadmeta http-equiv=Content-Type ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from 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 (PDB-679) Smoke test PDB 2.0.0 packages for Ubuntu 14.04
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test PDB 2.0.0 packages for Ubuntu 14.04 Looking good, closing. Add Comment PuppetDB / PDB-679 Smoke test PDB 2.0.0 packages for Ubuntu 14.04 Smoke test on Ubuntu 14.04 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1125) Exec checks should be turned into metaparameters
Title: Message Title Deepak Giridharagopal commented on an issue Re: Exec checks should be turned into metaparameters Kylo Ginsberg Why wouldn't we just mimic the behavior of those metaparams when used with exec? People are already used to that, and it seems like it would be an uncontroversial place to start. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2636) CRL last_update should be valid more than 1 second in the past
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2636 CRL last_update should be valid more than 1 second in the past Change By: Joshua Cooper Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2636) CRL last_update should be valid more than 1 second in the past
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2636 CRL last_update should be valid more than 1 second in the past Issue Type: Bug Assignee: Andy Parker Components: Networking Services Created: 22/May/14 10:03 AM Priority: Normal Reporter: Joshua Cooper When puppet's CA generates a CRL, it sets the last_update field to one second in the past (relative to the CA's local time). https://github.com/puppetlabs/puppet/blob/3.6.0/lib/puppet/ssl/certificate_revocation_list.rb#L87 When the CRL is downloaded to the agent, the agent will use it when making authenticated SSL connections. If the agent's local time, is slightly in the past, then the CRL will not yet be valid, and cause errors like: Error: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [CRL is not yet valid for /CN=o85sgww6moc2jxb.delivery.puppetlabs.net] We should set the CRL last_update time earlier in the past to be less sensitive to timing issues. In the case of Certificates, we set the not_before time to 24 hours in the past: https://github.com/puppetlabs/puppet/blob/3.6.0/lib/puppet/ssl/certificate_factory.rb#L49
Jira (PUP-2596) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2596 Prepare long form release notes and short form release story Attaching the list of issues I'll be building release notes off. We can use this later if we need to determine whether new issues were added after the release notes were written. Change By: Nicholas Fagerlund Attachment: puppet3.6.1issuesmay22.txt 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-247) Prepare long form release notes and short form release story
Title: Message Title Justin Holguin commented on an issue Re: Prepare long form release notes and short form release story The release notes are done and ready to merge. The release story should be: *Pre-release:* Entered RC1 on May 22, 2014. Hiera 1.3.3 is a backward-compatible performance and fixes release in the 1.3 series. It provides a substantial speed increase for lookups compared to Hiera 1.3.2. This release also adds support for Ubuntu 14.04 (Trusty Tahr) and discontinues support for Fedora 18 and Ubuntu 12.04 (Raring Ringtail). Add Comment Hiera / HI-247 Prepare long form release notes and short form release story Collaborating with product for release story Dependencies: * Is there a JIRA ticket targeted at the release for every commit? * Is there a commit for every JIRA ticket targeted at the release? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (HI-249) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages Packages: http://builds.puppetlabs.lan/hiera/1.3.3/ Add Comment Hiera / HI-249 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 (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Same issue here with Puppet version 3.6.0 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2554) FFI Puppet::Util::ADSI module
Title: Message Title
Ethan Brown commented on an issue
Re: FFI Puppet::Util::ADSI module
There are some changes to FFI MemoryPointer that should be merged in first
Add Comment
Puppet / PUP-2554
FFI Puppet::Util::ADSI module
Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. GetComputerNameW. Also don't do things like: {code} buf = * 128 Win32API.new('kernel32', 'GetComputerName', ['P','P'], 'I').call(buf, buf.length.to_s) @computer_name = buf.unpack(A*)[0] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2519) Settings catalog should create the default environment if environmentpath set.
Title: Message Title Kurt Wall commented on an issue Re: Settings catalog should create the default environment if environmentpath set. With environmentpath unset in puppet.conf, /etc/puppet/environments exists, and environment is the default production environment, Puppet creates /etc/puppet/environments/production if it doesn't exist. With environmentpath unset in puppet.conf, /etc/puppet/environments exists, and environment (directory) specfied exists, Puppet is happy. With environmentpath unset in puppet.conf, /etc/puppet/environments exists, and the environment specified as a non-existent directory, Puppet complains. Add Comment Puppet / PUP-2519 Settings catalog should create the default environment if environmentpath set. Ensure that settings catalog creates the default production environment if an environmentpath has been set. This will help ensure that once PUP-2252 is done, we don't fail in new installations where no production environment directory has been created yet. If environmentpath is set, we should manage $environmentpath.first/$environment.default. W... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2595) Is a new version created in Jira for the next version in the series?
Title: Message Title Peter Huene updated an issue Puppet / PUP-2595 Is a new version created in Jira for the next version in the series? Change By: Peter Huene Assignee: PeterHuene 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-2597) Tag the release and create packages
Title: Message Title Peter Huene commented on an issue Re: Tag the release and create packages SHA is bb83a84e066581bc0fdd3ff929cacdfc640a57b9 out of stable. Add Comment Puppet / PUP-2597 Tag the release and create packages Tag and create packages * Developer provides the SHA - [~peter.huene] - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb) * checkout the sha * NOTE: If this is a final release, make sure you're releasing only the code that already went through rc, so don't let any new code get into the final r... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2519) Settings catalog should create the default environment if environmentpath set.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2519 Settings catalog should create the default environment if environmentpath set. Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-681) Light Announcements for PDB 2.0.0 and Ubuntu 14.04
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-681 Light Announcements for PDB 2.0.0 and Ubuntu 14.04 Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-677) Release PuppetDB 2.0.0 for Ubuntu 14.04
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-677 Release PuppetDB 2.0.0 for Ubuntu 14.04 Change By: Kenneth Barber Sprint: 20140604 20140521 to 20140618 20140604 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-2598) Smoke test packages
Title: Message Title Melissa Stone commented on an issue Re: Smoke test packages packages: http://builds.puppetlabs.lan/puppet/3.6.1/ Add Comment Puppet / PUP-2598 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 (PUP-2598) Smoke test packages
Title: Message Title Peter Huene commented on an issue Re: Smoke test packages Testing the deb out on Ubuntu / Debian. Add Comment Puppet / PUP-2598 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 (PUP-2637) windows install_options = command with spaces is quoted fails
Title: Message Title Rob Reynolds moved an issue Puppet / PUP-2637 windows install_options = command with spaces is quoted fails Change By: Rob Reynolds Workflow: Forge Platform Workflow Key: MODULES PUP - 728 2637 Project: ForgeModules Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2637) windows install_options = command with spaces is quoted fails
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2637 windows install_options = command with spaces is quoted fails Change By: Rob Reynolds Labels: puppetlabs- windows 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-2637) windows install_options = command with spaces is quoted fails
Title: Message Title Rob Reynolds commented on an issue Re: windows install_options = command with spaces is quoted fails I'm pretty sure this is not a bug though, just a misunderstanding of how install_options should be used. http://docs.puppetlabs.com/windows/writing.html#packagepackage - Scroll down to Install and Uninstall Options. Add Comment Puppet / PUP-2637 windows install_options = command with spaces is quoted fails Puppet will automatically quote any option that contains spaces. Adding a quote becuase of the space between /adminfile and the path, which causes the installer to fail install_options = ['/passive', '/adminfile \\server1\IDEinstall\AdminDeployment.xml','/norestart'], the windows error says cmdline: '/passive /adminfile \\ the quote sho... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving 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 (PUP-2598) Smoke test packages
Title: Message Title Peter Huene commented on an issue Re: Smoke test packages Testing .tar.gz on Linux and OSX. Add Comment Puppet / PUP-2598 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 (PUP-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Lindsey Smith PO created an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Issue Type: Bug Assignee: Unassigned Created: 22/May/14 1:11 PM Priority: Normal Reporter: Lindsey Smith PO I was creating a masterless puppet agent on a fresh Windows 8 installation, so I installed the Puppet agent with the following command line; MSIEXEC /i source\puppet-enterprise-3.2.3.msi PUPPET_AGENT_STARTUP_MODE=Disabled REBOOT=ReallySuppress ALLUSERS=1 /qb- /l*v c:\PuppetAgent.Install.log Then I tried to run a Puppet Apply with the following command line; C:\Windows\SysWOW64\cmd.exe /E:ON /C C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\bin\puppet.bat apply --modulepath=%LOCALSRC%\modules %LOCALSRC%\manifests\site.pp However i received an error that it could not created resources.dot. It was trying to create it in C:\ProgramData\PuppetLabs\puppet\var\state\graphs which looks like the expected place, however the directory structure was incomplete. Only C:\ProgramData\PuppetLabs\puppet\var existed. If I manually created this directory (MD C:\ProgramData\PuppetLabs\puppet\var\state\graphs) and then ran Puppet Apply it executed fine. It seems like that the code that creates the resources.dot file does not check for the existence of the dependent directory structure first.
Jira (PUP-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title
Lindsey Smith PO updated an issue
Puppet / PUP-2638
Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Change By:
Lindsey Smith PO
Iwascreating ViaENTERPRISE-181:Thisis a masterless general puppet agent platformissue.Itcanoccur( on afreshWindows8installation,soIinstalled anyplatform)whenallof the Puppetagentwiththe following commandline; aretrue: {noformat} #The`$vardir/state/graphs`directorydoesn'texist MSIEXEC #The`graph`settingistrue#TheagenthasneverrunbeforeExecuting`puppetapply`willfailtowritethecatalog.OnWindows,weset`graph`totrue:https: / isource\ /github.com/puppetlabs/puppet_for_the_win/blob/master/wix/ puppet .wxs#L302 - L306.On*nix(PEonly),weset`graph`totrue:https://github.com/puppetlabs/ enterprise- dist/blob/ 3. 2. 3. msiPUPPET_AGENT_STARTUP_MODE=DisabledREBOOT=ReallySuppressALLUSERS=1 x / qb- ext / l*v erb/puppet.conf.erb#L52{noformat}$bundleexecpuppetapply-e c notice'foo'--graphNotice : \PuppetAgent Scope(Class[main]):fooNotice:Compiledcatalogforarcturus . Install luna . log laninenvironmentproductionin0.01seconds Error:Nosuchfileordirectory-/Users/josh/.puppet/var/state/graphs/resources.dot {noformat} ThenItriedtorunaPuppetApplywiththefollowingcommandline; OnWindows: {noformat}C:\ Windows work \ SysWOW64\cmd puppet[stable+1~0-0!]bundleexecpuppetapply-enotice'foo'--graph--traceNotice:Scope(Class[main]):fooNotice:Compiledcatalogforwin-qp47voha2p4 . exe solar.laninenvironmentproductionin0.05secondsError:Nosuchfileordirectory-C: / E ProgramData/PuppetLabs/puppet/var/state/graphs/resources.dotC : ON / work/puppet/lib/puppet/graph/simple_graph.rb:474:in`initialize' C :/work/puppet/lib/puppet/graph/simple_graph.rb:474:in`open' C: \ProgramFiles(x86)\PuppetLabs\PuppetEnterprise\bin\ /work/ puppet /lib/puppet/graph/simple_graph . bat rb:474:in`write_graph'C:/work/puppet/lib/puppet/resource/catalog.rb:448:in`write_graph'C:/work/puppet/lib/puppet/resource/catalog.rb:231:in`finalize'C:/work/puppet/lib/puppet/application/ apply --modulepath=%LOCALSRC%\modules%LOCALSRC%\manifests\site . pp rb:219:in`blockinmain' {noformat} C:/work/puppet/lib/puppet/context.rb:56:in`override' C:/work/puppet/lib/puppet.rb:234:in`override' Howeverireceivedanerrorthatitcouldnotcreatedresources C:/work/puppet/lib/puppet/application/apply . dot rb:190:in`main'C:/work/puppet/lib/puppet/application/apply . Itwastryingtocreateit rb:151: in {{ `run_command' C: \ProgramData\PuppetLabs\ /work/ puppet \var\state\graphs}}whichlooksliketheexpectedplace,howeverthedirectorystructurewasincomplete /lib/puppet/application . Only{{ rb:371:in`block(4levels)inrun' C: \ProgramData\PuppetLabs\ /work/ puppet \var}}existed /lib/puppet/application . IfImanuallycreatedthisdirectory rb:479:in`plugin_hook'C:/work/puppet/lib/puppet/application.rb:371:in`block ( MD{{ 3levels)inrun' C: \ProgramData\PuppetLabs\ /work/ puppet \var\state\graphs}} /lib/puppet/util.rb:479:in`exit_on_fail'C:/work/puppet/lib/puppet/application.rb:371:in`block(2levels ) andthenranPuppetApplyitexecutedfine inrun'C:/work/puppet/lib/puppet/context . rb:56:in`override' C:/work/puppet/lib/puppet.rb:234:in`override' Itseemslike
Jira (PUP-2598) Smoke test packages
Title: Message Title Peter Huene commented on an issue Re: Smoke test packages .tar.gz looks good on Linux and OSX. Tested install.rb. Tested master/agent. Tested help and man. Tested puppet apply and agent. Add Comment Puppet / PUP-2598 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 (PUP-2598) Smoke test packages
Title: Message Title Peter Huene commented on an issue Re: Smoke test packages Testing the gem on Linux and OSX. Add Comment Puppet / PUP-2598 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 (PUP-2554) FFI Puppet::Util::ADSI module
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2554 FFI Puppet::Util::ADSI module Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-686 java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0 Change By: Kenneth Barber Summary: java.util.concurrent.TimeoutException:Idletimeoutexpired onUbuntu12.04andRuby1.9.3p0 sincePDB2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2639) Increase environment_timeout defeault.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2639 Increase environment_timeout defeault. Change By: Joshua Partlow Story Points: 1 Affects Version/s: 3.6.1 Fix Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2639) Increase environment_timeout defeault.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-2639 Increase environment_timeout defeault. Issue Type: Bug Assignee: Unassigned Created: 22/May/14 1:43 PM Priority: Normal Reporter: Joshua Partlow Current environment_timeout defaults to 5s, which is too quick for typically production catalog build. It is essential that the timeout be longer than the typical catalog build time, and we want a default that will work reasonable well for general production cases. Three minutes seems reasonable. This fix should be cherry picked (or merged down if all stable is being merged) back to pe-puppet/3.3.x. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2639) Increase environment_timeout defeault.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2639 Increase environment_timeout defeault. Change By: Joshua Partlow Sprint: Week2014-5-28to2014-6-4 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-2639) Increase environment_timeout defeault.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2639 Increase environment_timeout defeault. Change By: Joshua Partlow Component/s: Modules 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-2519) Settings catalog should create the default environment if environmentpath set.
Title: Message Title Joshua Partlow commented on an issue Re: Settings catalog should create the default environment if environmentpath set. Kurt Wall with environmentpath not set (no environmentpath), Puppet still creates a production directory? Add Comment Puppet / PUP-2519 Settings catalog should create the default environment if environmentpath set. Ensure that settings catalog creates the default production environment if an environmentpath has been set. This will help ensure that once PUP-2252 is done, we don't fail in new installations where no production environment directory has been created yet. If environmentpath is set, we should manage $environmentpath.first/$environment.default. W... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2640) mysql_grant not idempotent
Title: Message Title
Hadmut Danisch created an issue
Puppet / PUP-2640
mysql_grant not idempotent
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Andy Parker
Components:
Modules
Created:
22/May/14 1:53 PM
Environment:
Ubuntu 14.04 with puppet 3.4.3 and puppet-module-puppetlabs-mysql Version: 2.1.0-2
Priority:
Normal
Reporter:
Hadmut Danisch
I'm using ressources like
mysql_grant { 'blog@192.168.160.%-blog_danisch.de': ensure = 'present', options = ['GRANT'], privileges = ['ALL'], table = 'blog_danisch.de.*', user = 'blog@192.168.160.%', }
which do work well, but do not detect that they already had succeeded before. Everytime I call puppet, I get a
Notice: /Stage[main]/Hadmut::Application::Blogdevelop/Mysql_grant[blog@192.168.160.%-blog_danisch.de]/ensure: created
regards
Jira (PUP-2598) Smoke test packages
Title: Message Title Peter Huene commented on an issue Re: Smoke test packages Testing .dmg on OSX. Add Comment Puppet / PUP-2598 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 (HI-249) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Testing on rhel7 Add Comment Hiera / HI-249 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 (PUP-2519) Settings catalog should create the default environment if environmentpath set.
Title: Message Title Kurt Wall commented on an issue Re: Settings catalog should create the default environment if environmentpath set. Joshua Partlow No, sorry about the mistake (reversing the behaviour between the environmentpath set and unset cases). I've done that a couple of times while working on this bug. I've corrected the 11:11 am comment so it's correct. For the record: if environmentpath is not set and the requested environment is the default production environment, Puppet does not create the production directory. Add Comment Puppet / PUP-2519 Settings catalog should create the default environment if environmentpath set. Ensure that settings catalog creates the default production environment if an environmentpath has been set. This will help ensure that once PUP-2252 is done, we don't fail in new installations where no production environment directory has been created yet. If environmentpath is set, we should manage $environmentpath.first/$environment.default. W... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PUP-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Rob Reynolds commented on an issue Re: Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed This will be great. I had some folks specifically ask about this last week. Add Comment Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed With Windows 2012, installing the puppet MSI (3.5.0-rc1 in this case) and then trying to run the Run Facter or Run Puppet Agent commands from the Start Menu will result in an error that it needs the .NET Framework version 3.5 in order to run and it cannot install it. However Start Command Prompt With Puppet works without issue. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (HI-251) Push tag
Title: Message Title Melissa Stone commented on an issue Re: Push tag tag pushed early so that we can include Hiera 1.3.3 in the Puppet 3.6.1 msi package Add Comment Hiera / HI-251 Push tag The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: * Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-688) java.lang.OutOfMemoryError
Title: Message Title Kenneth Barber commented on an issue Re: java.lang.OutOfMemoryError What is your heap set to in /etc/sysconfig/puppetdb? You can look at the JAVA_ARGS variable to see what it is set at with the -Xmx switch, for example: JAVA_ARGS=-Xmx192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof It may be that you need to increase this. Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this
Jira (PDB-688) java.lang.OutOfMemoryError
Title: Message Title jon yeargers commented on an issue Re: java.lang.OutOfMemoryError JAVA_ARGS is being set via the puppetdb startup options in /etc/sysconfig/puppetdb. Still at default: -Xmx192m The default value must be quite low if my installation of ~60 clients is crashing it. Recommended value? Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2642 selector _expression_ default should be matched last Change By: Henrik Lindberg Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2642 selector _expression_ default should be matched last Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 22/May/14 2:49 PM Priority: Major Reporter: Henrik Lindberg The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the default entry last in the selector. Add Comment
Jira (PUP-2643) Puppet Cron Resource Overwrites Crontab File Under Certain Situations
Title: Message Title Nick Walker created an issue Puppet / PUP-2643 Puppet Cron Resource Overwrites Crontab File Under Certain Situations Issue Type: Bug Assignee: Unassigned Created: 22/May/14 2:52 PM Labels: customer support Priority: Normal Reporter: Nick Walker In the case where a crontab file has invalid entries the cron resource ends up overwriting the whole file with just the resources puppet knows about and removes any manually entered crontab entries even if they were valid. On a fresh system I have the following crontab setup provided by puppet: [root@master323-centos ~]# crontab -l # HEADER: This file was autogenerated at 2014-05-02 17:31:32 + by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. # Puppet Name: pe-mcollective-metadata 0,15,30,45 * * * * /opt/puppet/sbin/refresh-mcollective-metadata # Puppet Name: pe-puppet-console-prune-task * 1 * * * /opt/puppet/bin/rake -f /opt/puppet/share/puppet-dashboard/Rakefile RAILS_ENV=production reports:prune reports:prune:failed upto=30 unit=day /dev/null I then use crontab -e to add a new entry: [root@master323-centos ~]#
Jira (PUP-2598) Smoke test packages
Title: Message Title Joshua Cooper commented on an issue Re: Smoke test packages MSI looks good on 2008r2. Tested service start/stop, doc links, puppet resource, apply, and agent: C:\Windows\system32puppet --version 3.6.1 C:\Windows\system32facter --version 2.0.1 Add Comment Puppet / PUP-2598 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
Jira (PUP-2643) Puppet Cron Resource Overwrites Crontab File Under Certain Situations
Title: Message Title Nick Walker updated an issue Puppet / PUP-2643 Puppet Cron Resource Overwrites Crontab File Under Certain Situations Change By: Nick Walker Affects Version/s: 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Joshua Partlow commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x The +ExportCertData was merged to enterprise-dist in 0f6adaa Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-689) Option to compress / limit /var/lib/puppetdb/reports
Title: Message Title jon yeargers created an issue PuppetDB / PDB-689 Option to compress / limit /var/lib/puppetdb/reports Issue Type: New Feature Assignee: Unassigned Created: 22/May/14 2:57 PM Priority: Minor Reporter: jon yeargers For sites that don't have the wherewithal or resources to add a postgres machine - it would be nice to be able to compress all the .yaml files stored in /var/lib/puppetdb/reports. I have ~60 clients. Have been adding steadily for several months. My folder has 113K .yaml files. Maybe an option to .GZ the files as they are added. Or expire / remove them after a certain period of time.. or a differential storage of sorts to compress the older ones.. Just thinking out loud. Add Comment
Jira (PUP-2598) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages I'll grab Windows2003, 2008, and 2012. Add Comment Puppet / PUP-2598 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 (PUP-2644) Code Formatter
Title: Message Title redmine.exporter created an issue Puppet / PUP-2644 Code Formatter Issue Type: New Feature Assignee: Unassigned Created: 22/May/14 3:02 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Hi, I think it would be really nice if there was an automagic code formatter for `.pp` files. We did some go programming lately and one of the things that turned out to be the thing we liked the most was `gofmt`. We stopped mucking over styles and everybody could just (once and for all) configure his favorite editor to display the one correct way (which isn't necessarily the same as the output `gofmt` produces). It makes no difference what the preferences are (tabs vs. spaces, 2 vs. 4 vs. 8 – but who likes tabs anyway ). The authoritative answer is whatever the output from `gofmt` is. Please please, `puppet format somefile.pp` – outputs to stdout `puppet format -w somefile.pp` – rewrites the file thanks, Martin
Jira (PUP-2598) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Looks good on Windows 2003: === Versions === 3.6.1 2.0.1 1.3.3 === Help Commands === Usage: puppet subcommand [options] action [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally caLocal Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. configInteract with Puppet's settings. describe Display help about resource types deviceManage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucketStore and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. instrumentation_listener Manage instrumentation listeners. instrumentation_probe Manage instrumentation probes. key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. masterThe puppet master daemon moduleCreates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parserInteract directly with the parser. pluginInteract with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs reportCreate, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all manifests. secret_agent Mimics puppet agent. statusView puppet server status. See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.6.1 puppet-apply(8) -- Apply Puppet manifests locally SYNOPSIS Applies a standalone Puppet manifest to the local system. USAGE - puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute] [--detailed-exitcodes] [-l|--logdest file] [--noop] [--catalog catalog] [--write-catalog-summary] file DESCRIPTION --- This is the standalone puppet execution tool; use it to apply individual manifests. When provided with a modulepath, via command line or config file, puppet apply can effectively mimic the catalog that would be served by puppet master with access to the same modules, although there are some subtle differences. When combined with scheduling and an automated system for pushing manifests, this can be used to implement a serverless Puppet site. Most users should use 'puppet agent' and 'puppet master' for site-wide manifests. OPTIONS --- Note that any setting that's valid in the configuration file is also a valid long argument. For example, 'tags' is a valid setting, so you can specify '--tags class,tag' as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet with
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title
William Van Hevelingen commented on an issue
Re: selector _expression_ default should be matched last
Adding steps to reproduce
root@localhost:~# puppet --version
3.6.0
root@localhost:~# cat test.pp
$cmd_host = $database_host ? {
default = -h ${database_host} ,
undef = ,
}
notify { database_host is ${cmd_host}: }
# current parser correctly return
root@localhost:~# puppet apply --parser=current test.pp
Notice: Compiled catalog for localhost in environment production in 0.02 seconds
Notice: database_host is
Notice: /Stage[main]/Main/Notify[database_host is ]/message: defined 'message' as 'database_host is '
Notice: Finished catalog run in 0.02 seconds
# future parser on 3.6.0 returns -h
root@localhost:~# puppet apply --parser=future test.pp
Notice: Compiled catalog for localhost in environment production in 0.38 seconds
Notice: database_host is -h
Notice: /Stage[main]/Main/Notify[database_host is -h ]/message: defined 'message' as 'database_host is -h '
Notice: Finished catalog run in 0.02 seconds
# As Henrik pointed out on irc putting default at the end results in desired results with future parser
root@localhost:~# cat test.pp
$cmd_host = $database_host ? {
undef = ,
default = -h ${database_host} ,
}
notify { database_host is ${cmd_host}: }
root@localhost:~# puppet apply --parser=future test.pp
Notice: Compiled catalog for localhost in environment production in 0.36 seconds
Notice: database_host is
Notice: /Stage[main]/Main/Notify[database_host is ]/message: defined 'message' as 'database_host is '
Notice: Finished catalog run in 0.04 seconds
Add Comment
Puppet / PUP-2642
selector _expression_ default should be matched last
The future evaluator treats a default in a selector _expression_ just
Jira (PUP-2598) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Looks good on Win2008R2: === Versions === 3.6.1 2.0.1 1.3.3 === Help Commands === Usage: puppet subcommand [options] action [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally caLocal Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. configInteract with Puppet's settings. describe Display help about resource types deviceManage remote network devices doc Generate Puppet documentation and references facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucketStore and retrieve files in a filebucket help Display Puppet help. inspect Send an inspection report instrumentation_data Manage instrumentation listener accumulated data. instrumentation_listener Manage instrumentation listeners. instrumentation_probe Manage instrumentation probes. key Create, save, and remove certificate keys. kick Remotely control puppet agent man Display Puppet manual pages. masterThe puppet master daemon moduleCreates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parserInteract directly with the parser. pluginInteract with the Puppet plugin system. queue Deprecated queuing daemon for asynchronous storeconfigs reportCreate, display, and submit reports. resource The resource abstraction layer shell resource_type View classes, defined resource types, and nodes from all manifests. secret_agent Mimics puppet agent. statusView puppet server status. See 'puppet help subcommand action' for help on a specific subcommand action. See 'puppet help subcommand' for help on a specific subcommand. Puppet v3.6.1 puppet-apply(8) -- Apply Puppet manifests locally SYNOPSIS Applies a standalone Puppet manifest to the local system. USAGE - puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute] [--detailed-exitcodes] [-l|--logdest file] [--noop] [--catalog catalog] [--write-catalog-summary] file DESCRIPTION --- This is the standalone puppet execution tool; use it to apply individual manifests. When provided with a modulepath, via command line or config file, puppet apply can effectively mimic the catalog that would be served by puppet master with access to the same modules, although there are some subtle differences. When combined with scheduling and an automated system for pushing manifests, this can be used to implement a serverless Puppet site. Most users should use 'puppet agent' and 'puppet master' for site-wide manifests. OPTIONS --- Note that any setting that's valid in the configuration file is also a valid long argument. For example, 'tags' is a valid setting, so you can specify '--tags class,tag' as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet with '--genconfig'. * --debug:
Jira (HI-249) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages - Testing Debian7 - passed Add Comment Hiera / HI-249 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 (HI-249) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages Eric tested and passed rhel5 Add Comment Hiera / HI-249 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 (PUP-2598) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages Windows 2012 also looked good. Worked with Agent apply on all three versions of Windows as well and got good results when working with master. Add Comment Puppet / PUP-2598 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 (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title
Eric Sorenson commented on an issue
Re: Certname must be lowercase error not helpful
I am not going to re-open the original problem for further debate, but I agree it's completely terrible.
Christopher Price can you make sure this is not the case (hah-hah no pun intended) in the new CA service?
i.e. we should permit mixed-case (and indeed mixed character) subject names and not store the files on disk in a character-for-character representation of the certificate's subject name because this + https://projects.puppetlabs.com/issues/15561
We can remove the agent warning/restriction once we're no longer on the Ruby CA.
Add Comment
Puppet / PUP-2551
Certname must be lowercase error not helpful
Currently if you set a non lowercase certname you get this error: {code} Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 {code} Its not terribly helpful for a couple reasons. # We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say oh right, redmine, duh. # #1168 i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title
Zachary Stern commented on an issue
Re: Certname must be lowercase error not helpful
Would it be possible in the interim to simply provide a better error message, without doing any actual fixing of the problem in the current CA?
Add Comment
Puppet / PUP-2551
Certname must be lowercase error not helpful
Currently if you set a non lowercase certname you get this error: {code} Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 {code} Its not terribly helpful for a couple reasons. # We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say oh right, redmine, duh. # #1168 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 options, visit https://groups.google.com/d/optout.
Jira (PUP-2645) puppet module build checksums.json has incorrect metadata.json md5
Title: Message Title Jascha Lee created an issue Puppet / PUP-2645 puppet module build checksums.json has incorrect metadata.json md5 Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 22/May/14 3:32 PM Labels: module Priority: Minor Reporter: Jascha Lee 'puppet module build' modifies metadata.json. However, the checksum in checksums.json is for the unmodified metadata.json file, not the one that is built for the module. The consequence is that 'puppet module changes' shows: Warning: 1 files modified metadata.json Either it should not modify the metadata.json or it should checksum the modified file. Add Comment
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title John Bollinger commented on an issue Re: Exec checks should be turned into metaparameters I know this feature has been requested multiple times, but I am deeply skeptical of it. The 'onlyif' and 'unless' parameters make sense for Exec because, along with 'creates', they provide the basis for determining whether the resource is in sync. There is no other basis for making such a determination, since Execs have only parameters, and no properties. It all hangs together in that case, with Exec representing ad hoc resources built directly out of commands. For other resource types, the general premise that resources are in sync when and only when all their properties are in sync is deeply ingrained in users, modules, docs, and the code itself. Modifying that pillar of Puppetdom cannot help but be disruptive, and certainly cannot be considered uncontroversial. Furthermore, as I am inclined to say from time to time on the user list, Puppet is not a script engine. That is not a limitation, it is a strength! I urge you to not slip in (more) scripting through the back door. Useful new features are great, but not when they weaken what Puppet already offers. Promoting 'onlyif' and 'unless' to metaparameters might be less disruptive if instead of the behavior they now have on Execs (for in-syncedness evaluation), they instead set conditions under which resource synchronization would fail. E.g. if an 'onlyif' command were declared, and it failed when executed during the catalog run, then the resource would fail. But then either many erstwhile perfectly good Execs would be broken, or else there would be a confusing difference in behavior between Execs and other resource types. I think it would be wise to collect some proposed use cases for the feature (any implementation flavor) to evaluate how those might best be served. I'm inclined to think that where Puppet's existing facilities are insufficient for those, there will be better directions to go than endowing more resource types with 'onlyif' and 'unless'. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters
Jira (PDB-689) Option to compress / limit /var/lib/puppetdb/reports
Title: Message Title Kenneth Barber commented on an issue Re: Option to compress / limit /var/lib/puppetdb/reports jon yeargers I think you want the Puppet project, not PuppetDB. We don't create YAML files at all. Just an aside you could always use 'tmpwatch' (on redhat) or 'tmpreaper' (on debian) on the folder to retire reports after an age. As far as expiration I'm sure a combination of 'find' with -xargs with -mtime could be used to compress these files, ran as a cron job you get automation. Also, PuppetDB can run in small cases using HSQL, which is an embedded database. I'd only recommend it for 50-100 node setups at the most. Add Comment PuppetDB / PDB-689 Option to compress / limit /var/lib/puppetdb/reports For sites that don't have the wherewithal or resources to add a postgres machine - it would be nice to be able to compress all the .yaml files stored in /var/lib/puppetdb/reports. I have ~60 clients. Have been adding steadily for several months. My folder has 113K .yaml files. Maybe an option to .GZ the files as they are added. Or expire / remove t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2646) Option to compress / limit /var/lib/puppetdb/reports
Title: Message Title Kenneth Barber moved an issue Puppet / PUP-2646 Option to compress / limit /var/lib/puppetdb/reports Change By: Kenneth Barber Workflow: Engineering Platform Workflow Key: PDB PUP - 689 2646 Project: PuppetDB Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Eric Sorenson moved an issue Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x Change By: Eric Sorenson Workflow: PuppetEnterprise Platform Workflow Issue Type: Bug Improvement Key: PE FACT - 4262 483 Project: PuppetEnterprise[Internal] Facter Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-686 java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0 Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x 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-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Adrien Thebo updated an issue Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x Change By: Adrien Thebo Sprint: Week2014-5-21to2014-5-28 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-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Adrien Thebo updated an issue Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Ethan Brown Assignee: EthanBrown 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-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Adrien Thebo commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 It looks like 079e3ec9 should have fixed this, which set the restriction to '1.6 x 3.0'. I just blew away my installed gems and Gemfile.lock and got facter 2.0.1 upon reinstallation: └ rm -rf .bundle; rm -rf Gemfile.lock ; bundle install --path .bundle |grep facter Installing facter 2.0.1 Ethan Brown could you test this out? AFAICT this should be solved. Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Kylo Ginsberg commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 Adrien Thebo I think the Gemfile situation is the same as the gemspec situation in my comment above: i.e. yes, if you blow away gems, you'll get facter 2.something, but if you previously have gotten 1.7.something, puppet doesn't force an update. Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Adrien Thebo commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 Is it necessary for us to force that update? Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2385) FFI Puppet::Util::Windows::File module
Title: Message Title
Joshua Cooper commented on an issue
Re: FFI Puppet::Util::Windows::File module
Kurt Wall yeah, we have lots of test coverage around symlinks and replace_file, which is what calls MoveFileEx.
Add Comment
Puppet / PUP-2385
FFI Puppet::Util::Windows::File module
Need to FFI {{move_file_ex}} using {{MoveFileExW}}, and refactor common function declarations, e.g. {{CreateFileW}}.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Kylo Ginsberg commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 I don't know I thought that was the point of this ticket though. Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Adrien Thebo commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Kylo Ginsberg commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 I'm confused too about what is being requested here. I think however that the Gemfile and the gemspec are consistent. Ethan Brown Joshua Cooper thoughts? Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg commented on an issue Re: selector _expression_ default should be matched last William Van Hevelingen thanks for updating the issue with reproducer. The paint is drying on the fix right now. A PR is coming in a couple of minutes. I also discovered that the current parser also raises an error if there is no match. This was also missing in the future evaluator and included in this PR. With future parser, the result is simply undef if there is no match (until this is fixed). Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (HI-252) Packages pushed
Title: Message Title Melissa Stone commented on an issue Re: Packages pushed We're having issues with createrepo for el7 x86_64 metadata creation. Working on a solution now. Everything else is live and happy. Add Comment Hiera / HI-252 Packages pushed Push packages * run `rake pl:jenkins:uber_ship` * You will need the keys to the castle (aka the passphrase) for this to work. * Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. * Get a *second set of RelEng eyes* on the package... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2642 selector _expression_ default should be matched last Change By: Henrik Lindberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg commented on an issue Re: selector _expression_ default should be matched last If me make a 3.6.2 release, this should go in, otherwise targeted for 3.7. Language specification updated as it defined the old behavior. Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options,
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2642 selector _expression_ default should be matched last Change By: Henrik Lindberg Sprint: Week2014-5-28to2014-6-4 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-978) multiple literal default entries in case should raise error
Title: Message Title
Henrik Lindberg commented on an issue
Re: multiple literal default entries in case should raise error
the same validation should be applied to selector expressions
Add Comment
Puppet / PUP-978
multiple literal default entries in case should raise error
Multiple 'default' entries should result in a parse error. It creates an ambiguity. Consider the following examples: {code} case 10 { default : { notice 'nbr1' } default : { notice 'nbr2' } } # = notices nbr 2 case default { default : { notice 'nbr1 } default : { notice 'nbr2' } } # = notices nbr1 {code} The solution is to val...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-481) Make variable references strict by default
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-481 Make variable references strict by default Change By: Henrik Lindberg Fix Version/s: 4.x Fix Version/s: 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-481) Make variable references strict by default
Title: Message Title
Henrik Lindberg commented on an issue
Re: Make variable references strict by default
Changed version to 5.0.0 since this is a breaking change and cannot be introduced as the default during the course of 4.x.
Add Comment
Puppet / PUP-481
Make variable references strict by default
In 3x variable references result in undef if variable has not been set. Decide how to handle strict references: * Always * A setting/option * Is $x = undef the same as $x == nil, and if so is it 'set/defined' or not? In strict mode, defined($x) does not make sense since it is an error to reference x, instead defined('x') must be used, or defined(...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Ethan Brown commented on an issue Re: FFI Puppet::Util::Windows::Process module requires read_dword, which is defined in PUP-2554 Add Comment Puppet / PUP-838 FFI Puppet::Util::Windows::Process module This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-840) FFI Puppet::Util::Colors module
Title: Message Title
Ethan Brown commented on an issue
Re: FFI Puppet::Util::Colors module
Leverages read_dword which is part of PUP-2554
Add Comment
Puppet / PUP-840
FFI Puppet::Util::Colors module
In order to maintain compatibility with ruby 1.9.x, this ticket is about FFI'ing the {{Puppet::Util::Colors}} module, so use FFI instead of: {code} WriteConsole = Win32API.new( kernel32, WriteConsoleW, ['l', 'p', 'l', 'p', 'p'], 'l' ) {code} We should always prefer wide character APIs, and not make assumptions about pointer lengths: {code} ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2604) Send out announcements
Title: Message Title Eric Sorenson commented on an issue Re: Send out announcements Announcement: Puppet 3.6.1 is a bug fix release in the Puppet 3.6 series. It addresses a few issues which were “in flight” but whose fixes did not land by the cutoff for Puppet 3.6.0 and some regressions in recent Puppet releases. Here’s a summary of changes in this release: • Changes to RPM Behavior With Virtual Packages • Improvements to transaction_uuid in Reports and Node Termini • Windows Start Menu Fixes • Improved Passenger Packages on Debian/Ubuntu • HTTP API Fixes • Directory Environment Fixes • Future Parser Improvements If you're trying out directory environments, please set `environment_timeout=3m` in the `[main]` section of your master’s puppet.conf — this helps the new environment cache reduce CPU usage and will become the default in a future version. Read/comment on the puppet-users mailing list thread for more info or to contribute your experience: https://groups.google.com/d/topic/puppet-users/arLckU-mPhw/discussion Please read through the Release Notes for the full list of changes:http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html To install Puppet, follow the Installation Guide: http://docs.puppetlabs.com/guides/install_puppet/pre_install.html To report issues with the release, file a ticket in the “PUP” project on https://tickets.puppetlabs.com/ and set the “Affects version/s” field to 3.6.1”. To see a list of known issues slated for the next bugfix release, follow this JIRA query: https://tickets.puppetlabs.com/issues/?filter=12304 Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 puppet platform // coffee // techno // bicycles Add Comment Puppet / PUP-2604 Send out announcements * Update the
Jira (PUP-836) FFI Puppet::Util::Windows::User module
Title: Message Title
Joshua Cooper commented on an issue
Re: FFI Puppet::Util::Windows::User module
Merged into master in 6722eac to be released in 3.7.0.
Add Comment
Puppet / PUP-836
FFI Puppet::Util::Windows::User module
Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. LogonUserW. Also don't do things like: {code} sid = 0.chr * 80 size = [80].pack('L') member = 0.chr * 4 {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 22/May/14 7:31 PM Labels: windows Priority: Normal Reporter: Joshua Cooper If you change an existing user's password on Windows, puppet reports: Notice: /Stage[main]/Main/User[testing6]/password: created password If the desired password doesn't match current password, the windows_adsi provider's #password method returns :absent, to force the provider to apply the new password. But this causes puppet to think the property was created. It would be preferrable to say that the passwords were changed. See https://github.com/puppetlabs/puppet/commit/51b33d1f/lib/puppet/provider/user/windows_adsi.rb#diff-cb6db5b98229b4ec070f9158795e3708R61
Jira (PUP-2554) FFI Puppet::Util::ADSI module
Title: Message Title
Joshua Cooper commented on an issue
Re: FFI Puppet::Util::ADSI module
Merged into master in bd7a103 to be released in 3.7.0
Add Comment
Puppet / PUP-2554
FFI Puppet::Util::ADSI module
Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. GetComputerNameW. Also don't do things like: {code} buf = * 128 Win32API.new('kernel32', 'GetComputerName', ['P','P'], 'I').call(buf, buf.length.to_s) @computer_name = buf.unpack(A*)[0] {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2554) FFI Puppet::Util::ADSI module
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-2554 FFI Puppet::Util::ADSI module Change By: Joshua Cooper Assignee: RobReynolds JoshuaCooper 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-840) FFI Puppet::Util::Colors module
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-840 FFI Puppet::Util::Colors module Change By: Joshua Cooper Assignee: JoshuaCooper 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.
