Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Baptiste Hebert commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Thank you Rob Reynolds for your prompt answer. This happens when there is no prior installation of Puppet, but in a particular situation: this is during a fresh Windows installation in our post-installation script (vbs). If I run the same script after the windows post-installation script, I can't reproduce the issue. So I guess the issue is linked to some user context that maybe not complete during our post-installation. Our Locale is English (United States). Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title
Luke Kanies commented on an issue
Re: Remove support for yaml on the network
Ah, I didn't realize the agent didn't send yaml any more - thanks for the update on that, Andy Parker.
Add Comment
Puppet / PUP-3272
Remove support for yaml on the network
YAML on the network is either dangerous or slow. It is dangerous without safe_yaml and slow with it. We've had it deprecated for a while now. Puppet 4 is the time to completely remove it. We can remove: * vendored safe_yaml * serializing and deserializing yaml * special parsing for query parameters that start with {{\-\-\-}} * more?
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-3346) curl allows --insecure SSL connections
Title: Message Title
Daniele Sluijters commented on an issue
Re: curl allows --insecure SSL connections
Since this is curl all it takes is setting CURL_CA_BUNDLE environment variable to point to a pem-file that contains a certificate which can be used to validate a connection.
Whether this is the OS trust store or not doesn't matter really. As far as 'insecure' goes, I would vote for people to make said root CA available on the system and set the environment variable as proposed above. Even if it's not a trusted root CA you'll now at least know when someone tries to MITM you.
Add Comment
Puppet / PUP-3346
curl allows --insecure SSL connections
The {{appdmg}} and {{pkgdmg}} providers were calling {{curl}} with {{\-k}} (alias for {{--insecure}}) which allows curl'ing over insecure HTTPS connections. I can't see why this would ever be desired, and many connections will often fail when attempting establish a connection. I have a PR removing the insecure option: https://github.com/puppetlabs/pupp...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed
Jira (PUP-3477) Improved Cipher settings only used by fresh installations
Title: Message Title Per Cederqvist created an issue Puppet / PUP-3477 Improved Cipher settings only used by fresh installations Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Unassigned Created: 16/Oct/14 2:35 AM Priority: Normal Reporter: Per Cederqvist As a long-time Puppet user, I have a fairly bad /etc/apache2/sites-available/puppetmaster file. It accepts SSLv3, which we all know is a very bad idea (SSLv3 POODLE – I need not say more, I guess). The /usr/share/puppetmaster-passenger/apache2.site.conf.tmpl file installed on my Puppet master seems to be a lot more secure. They way that these files are handled on Debian makes it needlessly hard to get the improvements into production, though. I think it would be better if /etc/apache2/sites-available/puppetmaster were re-created from apache2.site.conf.tmpl each time Puppet was upgraded. That way my installation would be kept secure when you fix new issues in the future. I understand that you may not want to make such changes because the user may have edited the file in sites-available. But at least as long as it hasn't been touched by the user, it should be upgraded. Failing that, it would be nicer if the installation created a file (say /usr/share/puppetmaster-passenger/apache2.site.conf) with all the edits that the postinst script does, so that it is easier for an admin to just copy that file to sites-available if he wants to get the new cipher settings. The release notes for Puppet 3.7.0 should also have explained what an
Jira (PDB-968) PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-968 PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres Issue Type: Task Assignee: Unassigned Created: 16/Oct/14 4:40 AM Labels: github module Priority: Normal Reporter: gepetto-bot Remove invisible unicode character to prevent invalid byte sequence in ... Author: Stefan Andres s.and...@syseleven.de Company: SysEleven GmbH Github ID: stefanandres Pull Request 149 Discussion Pull Request 149 File Diff Pull Request Description Someone inserted an unicode character (probably by accident) to the jetty_ini.pp file which prevents puppet-run without unicode environment to run the puppet module. Those scenarios are likely while bootstrapping new server.
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Jeff Waugh commented on an issue Re: Windows Puppet x86 Installer on x64 system issue I can reproduce the crap out of this with a very fresh packer-windows build of Windows 2008 R2 Core and Puppet 3.7.1 (32 and 64 bit). Installed with: msiexec.exe /qn /norestart /i https://downloads.puppetlabs.com/windows/puppet-3.7.1-x64.msi PUPPET_AGENT_STARTUP_MODE=Disabled When Vagrant connects to execute Puppet, it fails with: == default: # CLIXML == default: Objs Version=1.1.0.1 xmlns=http://schemas.microsoft.com/powershell/2004/04S S=ErrorThe term 'puppet' is not recognized as the name of a cmdlet, function, script f_x000D__x000A_/SS S=Errorile, or operable program. Check the spelling of the name, or if a path was incl_x000D__x000A_/SS S=Erroruded, verify that the path is correct and try again._x000D__x000A_/SS S=ErrorAt line:1 char:7_x000D__x000A_/SS S=Error+ puppet lt;lt;lt;lt; apply --verbose --color=false --manifestdir /tmp/vagrant-puppet-_x000D__x000A_/SS S=Error4/manifests --detailed-exitcodes /tmp/vagrant-puppet-4/manifests/default.pp; ex_x000D__x000A_/SS S=Errorit $LASTEXITCODE_x000D__x000A_/SS S=Error+ CategoryInfo : ObjectNotFound: (puppet:String) [], CommandNotFo _x000D__x000A_/SS S=Error undException_x000D__x000A_/SS S=Error+ FullyQualifiedErrorId : CommandNotFoundException_x000D__x000A_/SS S=Error _x000D__x000A_/S/Objs However, when I log in as vagrant via RDP, the path looks correct, and works. C:\Users\vagrantpath PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\OpenSSH\bin;C:\Program Files\Puppet Labs\Puppet\bin
Jira (PDB-968) PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-968 PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres Change By: Kenneth Barber Sprint: PuppetDB2014-10-22 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-297) hiere (debian) package does not register as gem
Title: Message Title Igor Galić created an issue Hiera / HI-297 hiere (debian) package does not register as gem Issue Type: Bug Assignee: Unassigned Created: 16/Oct/14 6:47 AM Priority: Normal Reporter: Igor Galić when installing the hiera package from apt.puppetlabs.com, it's not registered as gem, this makes it tricky to install third-party gems that depend on hiera Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-968) PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-968 PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres Change By: Kenneth Barber Affects Version/s: module-4.0.0 Story Points: 0 Fix Version/s: module-4.1.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-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Jeff Waugh commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Interesting. I added another shell provisioner script, debug.bat, which just runs path and puppet. == default: Running provisioner: shell... default: Running: c:\tmp\vagrant-shell.ps1 == default: Puppet version 3.7.1-x64 specified, updated MsiUrl to https://downloads.puppetlabs.com/windows/puppet-3.7.1-x64.msi == default: Puppet is not installed, continuing... == default: Installing Puppet. Running msiexec.exe /qn /norestart /i https://downloads.puppetlabs.com/windows/puppet-3.7.1-x64.msi PUPPET_AGENT_STARTUP_MODE=Disabled == default: Puppet successfully installed. == default: Running provisioner: shell... default: Running: c:\tmp\vagrant-shell.bat == default: C:\Windows\system32path == default:
Jira (HI-297) hiere (debian) package does not register as gem
Title: Message Title
Igor Galić updated an issue
Hiera / HI-297
hiere (debian) package does not register as gem
Change By:
Igor Galić
wheninstallingthehierapackagefromapt.puppetlabs.com,it'snotregisteredasgem,thismakesittrickytoinstallthird-partygemsthatdependonhiera :{code}igalic@puppet01-mgmt~%hieraforeman01.mgmt.acme.com.key.pemWARN:2014-10-1615:50:42+0200:Cannotloadbackendfile:Couldnotfind'hiera'(=1.0.0)among24totalgem(s)Checkedin'GEM_PATH=/home/igalic/.gem/ruby/1.9.1:/usr/lib/ruby/gems/1.9.1',execute`gemenv`formoreinformationnil{code}
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-2387) Remote users, specifically AD-LDAP, do not have their home directories created with managehome set to true
Title: Message Title Rob Nelson commented on an issue Re: Remote users, specifically AD-LDAP, do not have their home directories created with managehome set to true Kylo, anything I can do to help this along? In IRC it came up today that the managehome attribute only creates the directory when the user is created, so perhaps this is less of a bug and more of a feature request. Regardless, if I could help this along let me know how! Add Comment Puppet / PUP-2387 Remote users, specifically AD-LDAP, do not have their home directories created with managehome set to true I am attempting to add certificates to a user's home directory for use with mcollective. This involves the puppetlabs/mcollective class and mcollective::user definition, plus our local modules site_mcollective and 'orgname' modules and the provided orgname::mcollective::user definition. The users are members of LDAP and show up via 'getent', therefore the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title
Rob Reynolds commented on an issue
Re: Windows Puppet x86 Installer on x64 system issue
Jeff Waugh I am not completely sure what you are seeing is the same thing. Do you have chocolatey installed on the VM?
Try this in your debug.bat:
path
@powershell -NoProfile -ExecutionPolicy unrestricted -Command iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin
refreshenv
path
where puppet
Add Comment
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title
Jeff Waugh commented on an issue
Re: Windows Puppet x86 Installer on x64 system issue
If I then log in on the console, the path is correct and {{puppet]} is found.
If I then run my debug.bat shell provisioner again, the path is incorrect and puppet is not found, same as the previous comment.
I think you're right – based on the output of path, this doesn't look like the same problem. Might be an issue with Vagrant, because I'm sure it's opening a new WinRM session for each provisioner (be it shell or puppet). Maybe there's a problem with Vagrant's WinRM communicator and paths.
Add Comment
Puppet / PUP-3471
Windows Puppet x86 Installer on x64 system issue
When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Baptiste Hebert thanks so much for the followup. Am I correct in understanding this may be environment related? That's slightly relieving...but waiting for confirmation. Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs.
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Jeff Palmer commented on an issue Re: Default setting for pluginsource problematic for deployments using SRV records with puppet 3.7, there is an additional piece needed to work around the issue. In puppet.conf for each agent, under [main] set the following two overrides: pluginsource = puppet:///plugins pluginfactsource = puppet:///pluginfacts Thanks to Erik Daln for realizing what the issue was! Add Comment Puppet / PUP-1035 Default setting for pluginsource problematic for deployments using SRV records The current default for the `pluginsource` setting is `puppet://$server/plugins`. This works well with a `server` set, but in deployments that utilize 3.0's SRV record feature, the `server` setting is likely not utilized at all for communication with a master, and will often be unset. If SRV records are in use the `pluginsource` still gets filled in 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
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Jeff Waugh commented on an issue Re: Windows Puppet x86 Installer on x64 system issue I'm going to take my issue here: https://github.com/mitchellh/vagrant/issues/4334 Thanks for your help! Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Baptiste Hebert commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Hey there, Thank you very much for your help! Our issue is a bit different but seems to be related: in our case the puppet binaries folder has been added to the PATH environment, but all %SystemRoot% based variables are gone. It's like the shell was not able to expand this variable as 'C:\Windows' and removed it. The consequence is that C:\Windows\System32 and some other paths are removed from PATH environment variable and if we open a new command prompt (cmd), we are not able to run simple windows commands such as 'hostname' or 'dir'. Doing so basically kills the server because all applications are based on it (Puppet included)... Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Baptiste Hebert commented on an issue Re: Windows Puppet x86 Installer on x64 system issue As a workaround, I modified my installation script to save the PATH variable before installation and then restore it after installation appending Puppet binaries folder It's working, but dirty. Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-3402) Custom module installation in synced folder on vagrant virtualbox fails
Title: Message Title
Christian Oyarzun commented on an issue
Re: Custom module installation in synced folder on vagrant virtualbox fails
I had the same problem, worked on OS X host and got operation not permitted on Windows hosts. It seems there are two issue with Windows hosts.
1) The 260 character limit for paths (https://github.com/rodjek/librarian-puppet/issues/256). Fixed this by having librarian-puppet use a temp dir inside the VM instead of a synced folder. eg. librarian-puppet config tmp /home/vagrant/.tmp --global
2) If your puppet modules are saved on a synced folder the read-only attribute gets set on the files. So if librarian-puppet tries to update the module it will get operation not permitted. This can be fixed with the following change PUP-3168 (https://github.com/puppetlabs/puppet/pull/3039). You will need to remove the downloaded modules or remove the read-only attribute on the modules files.
Add Comment
Puppet / PUP-3402
Custom module installation in synced folder on vagrant virtualbox fails
I have recently started playing around with Vagrant, VirtualBox and now Puppet and i wanted to try out and build my own configuration. I found a nice puppet module manager in librarian-puppet, but unfortunately it doesn't work. After it errored out, it asked me to run the following command to see if it was an error with itself or with puppet: {code} p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Baptiste Hebert ugh - so it's still there. Yeah, we definitely need to correct this. Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue Change By: Rob Reynolds Fix Version/s: PUP3.7.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-3294) Remove support for :parent
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3294 Remove support for :parent Change By: Kylo Ginsberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3294) Remove support for :parent
Title: Message Title Kylo Ginsberg commented on an issue Re: Remove support for :parent Nicholas Fagerlund: Looks like we should update this: https://docs.puppetlabs.com/guides/custom_types.html#options. Thanks to Jeremy Barlow for noticing this. Add Comment Puppet / PUP-3294 Remove support for :parent lib/puppet/metatype/manager.rb:88: Puppet.deprecation_warning option :parent is deprecated. It has no effect This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2012) puppet module --modulepath command errors when run as non-root
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2012 puppet module --modulepath command errors when run as non-root Change By: Adrien Thebo Component/s: PMT 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-3311) Remove deprecated methods from Puppet::Provider
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3311 Remove deprecated methods from Puppet::Provider 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 (PDB-968) PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres
Title: Message Title gepetto-bot commented on an issue Re: PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres Pull request Remove invisible unicode character to prevent invalid byte sequence in ... has been closed. Add Comment PuppetDB / PDB-968 PR (149): Remove invisible unicode character to prevent invalid byte sequence in ... - stefanandres h2. Remove invisible unicode character to prevent invalid byte sequence in ... * Author: Stefan Andres s.and...@syseleven.de * Company: SysEleven GmbH * Github ID: [stefanandres|https://github.com/stefanandres] * [Pull Request 149 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/149] * [Pull Request 149 File Diff|https://github.c... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Baptiste Hebert Would you mind sending me the script that you are using to do this? If you can attach it here, that would be great. If you don't feel comfortable doing so you can email me at rob at puppetlabs dot com Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-3477) Improved Cipher settings only used by fresh installations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3477 Improved Cipher settings only used by fresh installations Change By: Josh Cooper Component/s: RE 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-3310) Remove warning for copying owner/group to windows
Title: Message Title Michael Smith commented on an issue Re: Remove warning for copying owner/group to windows Work so far: https://github.com/MikaelSmith/puppet/tree/task/master/PUP-3310-Windows-error-on-copy-permissions Add Comment Puppet / PUP-3310 Remove warning for copying owner/group to windows The file resource produces a warning that copying owner or group or mode from a remote source is not supported on windows. The warning needs to be removed and replaced with a failure. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2613) Change source_permissions default to :ignore
Title: Message Title Michael Smith updated an issue Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Michael Smith Sprint: PlatformClient2014-10-29 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-3459) reports directory created by first puppet agent/apply run, should be created by OS package
Title: Message Title Wayne Warren commented on an issue Re: reports directory created by first puppet agent/apply run, should be created by OS package Josh Cooper that was just a workaround for puppet-server. I am going to change the title of this ticket to reflect discussion in that PR where Matthaus Owens suggested that reportsdir have group write permissions and setgid. group write permissions means that the puppet group would have write permissions on reportsdir, setgid on the reportsdir directory will ensure that the group permissions are inherited by subdirectories So even if root creates a subdirectory, the puppet user (having its primary group as the puppet group) will also be able to write to it. Let me know if any further clarification is necessary. Add Comment Puppet / PUP-3459 reports directory created by first puppet agent/apply run, should be created by OS package When running puppet apply as root during acceptance/integration test pre_suite in order to stub a host in /etc/hosts, a reports directory directory is created as the root user which leads to permissions errors during subsequent runs of puppet as the puppet user. This is a directory that we should definitely not be creating on a programmatic basis. ...
Jira (PUP-3459) reports directory should have group write permissions and be setgid
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3459 reports directory should have group write permissions and be setgid Change By: Wayne Warren Summary: reportsdirectory createdbyfirstpuppetagent/applyrun, should havegroupwritepermissionsand be createdbyOSpackage setgid 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-3459) reports directory should have group write permissions and be setgid
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3459 reports directory should have group write permissions and be setgid Change By: Wayne Warren Whenrunningpuppetapplyasrootduring puppet-server acceptance/integrationtestpre_suite ( inordertostubahostin/etc/hosts ) ,areports subdirectory directory directory forthemasterhost iscreatedastherootuserwhichleadstopermissionserrorsduringsubsequentrunsofpuppetasthepuppetuser. This Suggestedfix is adirectorythatweshoulddefinitelynotbecreating to*setgroupwritepermission on aprogrammaticbasis.Ifwemustdo reportsdir*setgidonreportsdir so thenmoredetailedthoughtshouldgointodirectoryownershipand subdirectoriesinheritgroup permissions .Inthepastwehaveaddressedsimilarproblemswithotherdirectoriesbycreatingthemduringpackageinstallationwhichseemslikeagoodapproachtome. 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-2613) Change source_permissions default to :ignore
Title: Message Title
Michael Smith commented on an issue
Re: Change source_permissions default to :ignore
Check syncing plugin facts, plugins, and retrieving explicit file resource.
Add Comment
Puppet / PUP-2613
Change source_permissions default to :ignore
Currently, puppet will copy the owner/group/mode from sourced files when those properties are unspecified. This leads to surprising results, e.g. PUP-1986. We discussed changing the default behavior in https://groups.google.com/forum/#!msg/puppet-users/XNy8gI3jcf0/HufQkYQdKMAJ This ticket calls for changing the default value of {{:source_permissions...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-2613) Change source_permissions default to :ignore
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Michael Smith Assignee: MichaelSmith 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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker assigned an issue to Britt Gresham Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Assignee: AndyParker BrittGresham 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-3201) Validation thinks that an Undef instance is of type Runtime
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3201 Validation thinks that an Undef instance is of type Runtime Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3401) Type system does not handle Pattern correctly
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3401 Type system does not handle Pattern correctly Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3401) Type system does not handle Pattern correctly
Title: Message Title Andy Parker updated an issue Puppet / PUP-3401 Type system does not handle Pattern correctly Change By: Andy Parker Fix Version/s: PUP4.0.0 Fix Version/s: PUP3.7.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 (PDB-958) PR (1120): Our code currently requires Puppet 3.5.1 or higher by using Puppet.lookup() - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1120): Our code currently requires Puppet 3.5.1 or higher by using Puppet.lookup() - senior Pull request Our code currently requires Puppet 3.5.1 or higher by using Puppet.lookup() has been closed. Add Comment PuppetDB / PDB-958 PR (1120): Our code currently requires Puppet 3.5.1 or higher by using Puppet.lookup() - senior h2. Our code currently requires Puppet 3.5.1 or higher by using Puppet.lookup() * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1120 Discussion|https://github.com/puppetlabs/puppetdb/pull/1120] * [Pull Request 1120 File Diff|https://github.com/puppetlabs/puppetdb/pull/1120/fil... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post 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-3401) Type system does not handle Pattern correctly
Title: Message Title Andy Parker updated an issue Puppet / PUP-3401 Type system does not handle Pattern correctly Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Also, some other things that would be helpful powershell version windows installer version (or default that comes with windows) Can you verify that Puppet 3.6.2 did or did not have this problem? What results do you get when you run the following powershell script on the box (before the puppet install)? %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Progra~2\WINDOWS RESOURCE KITS\TOOLS\.Replace(C:\Program Files\Puppet Labs\Puppet\bin;,).Replace(C:\Program Files\Puppet Labs\Puppet\bin,) | Write-Host [System.Environment]::GetEnvironmentVariable(PATH,Machine).Replace(C:\Program Files\Puppet Labs\Puppet\bin;,).Replace(C:\Program Files\Puppet Labs\Puppet\bin,) | Write-Host Add Comment
Jira (PUP-3310) Remove warning for copying owner/group to windows
Title: Message Title Andy Parker commented on an issue Re: Remove warning for copying owner/group to windows Michael Smith, did you mean to close this as a duplicate? Does the other ticket cover removing this functionality? Add Comment Puppet / PUP-3310 Remove warning for copying owner/group to windows The file resource produces a warning that copying owner or group or mode from a remote source is not supported on windows. The warning needs to be removed and replaced with a failure. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3401) Type system does not handle Pattern correctly
Title: Message Title
Andy Parker commented on an issue
Re: Type system does not handle Pattern correctly
Since we have the PR already and 3.7.2 isn't out yet, I think putting this into 3.7.2 is best. It makes the types of Pattern, String, and Enum consistent in 3.7.2.
Merged into stable in 873a93
Add Comment
Puppet / PUP-3401
Type system does not handle Pattern correctly
The Pattern type has similar problems to the Enum type + it is not implemented correctly. {code} Pattern Pattern[/.*/] # false Pattern Pattern[/.*/] # false Pattern == Pattern[/.*/] # false {code} That is not correct and neither complies with the spec, nor the the law of least surprise
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to 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-3310) Remove warning for copying owner/group to windows
Title: Message Title Michael Smith commented on an issue Re: Remove warning for copying owner/group to windows Josh Cooper, Rob Reynolds, and I took a look at these tickets. PUP-2609 and PUP-3310 both cover changing the deprecation warning to an error; PUP-2609 has more backstory. PUP-2613 covers changing the default to :ignore, so we don't get an error on the default. Add Comment Puppet / PUP-3310 Remove warning for copying owner/group to windows The file resource produces a warning that copying owner or group or mode from a remote source is not supported on windows. The warning needs to be removed and replaced with a failure. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer on x64 system issue GetEnvironmentVariable automatically expands paths, which could be undesirable, but I'm not sure that is what would cause the issue you are seeing (although perhaps partly related). Still researching some. Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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 (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber Issue Type: Task Assignee: Unassigned Created: 16/Oct/14 11:22 AM Labels: github Priority: Normal Reporter: gepetto-bot Correct the ssl-protocols rewrite for the master branch Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 1127 Discussion Pull Request 1127 File Diff Pull Request Description Right now tk-webserver-jetty9 0.7.5 requires a list to be passed to it for the setting `ssl-protocols` but our rewrite still provides a comma separated string. While this is a bug in-and-of-itself, its causing our tests to fail. This patch gets us back to passing. We'll look
Jira (PUP-3294) Remove support for :parent
Title: Message Title Adrien Thebo commented on an issue Re: Remove support for :parent Merged in d096266. Add Comment Puppet / PUP-3294 Remove support for :parent lib/puppet/metatype/manager.rb:88: Puppet.deprecation_warning option :parent is deprecated. It has no effect This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3250) Remove secret_agent
Title: Message Title
Adrien Thebo commented on an issue
Re: Remove secret_agent
Merged in 2399249.
Add Comment
Puppet / PUP-3250
Remove secret_agent
The {{secret_agent}} face was an experiment to create a new agent built up of individual small tools (upload facts, perform pluginsync, fetch catalog, etc.). However it was never worked on and has languished.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber Change By: Kenneth Barber Sprint: PuppetDB2014-10-22 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-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber Change By: Kenneth Barber Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber 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-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber Change By: Kenneth Barber Affects Version/s: 3.0.0 Story Points: 0 Fix Version/s: 3.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-3291) Remove autoloader from Puppet::Interface
Title: Message Title
Adrien Thebo commented on an issue
Re: Remove autoloader from Puppet::Interface
Merged in 3073c31.
Add Comment
Puppet / PUP-3291
Remove autoloader from Puppet::Interface
{noformat} lib/puppet/interface.rb:35: # @deprecated lib/puppet/interface.rb:37: Puppet.deprecation_warning(Puppet::Interface.autoloader is deprecated; please use Puppet::Interface#loader instead) {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3372) Remove extlookup function
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3372 Remove extlookup function Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3478) Remove extlookup2hiera
Title: Message Title Adrien Thebo created an issue Puppet / PUP-3478 Remove extlookup2hiera Issue Type: Improvement Assignee: Unassigned Created: 16/Oct/14 12:08 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Adrien Thebo The extlookup function was removed in Puppet 4 but the extlookup2hiera executable was left around to allow users to migrate from extlookup2hiera. It should be removed in Puppet 5. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/108/ Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith created an issue Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Unassigned Components: Trivial Created: 16/Oct/14 12:24 PM Priority: Normal Reporter: Michael Smith Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+. Add Comment
Jira (PUP-3305) Change allow_virtual default to true
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3305 Change allow_virtual default to true Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3267) Remove puppet kick and related agent functionality
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3267 Remove puppet kick and related agent functionality Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2923) Add assumeyes attribute to yumrepo
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2923 Add assumeyes attribute to yumrepo 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-2923) Add assumeyes attribute to yumrepo
Title: Message Title Rob Reynolds commented on an issue Re: Add assumeyes attribute to yumrepo Merged into master at 640ec9c1 Add Comment Puppet / PUP-2923 Add assumeyes attribute to yumrepo The yumrepo type appears to be missing the boolean assumeyes attribute. This attribute is necessary in the following condition, and possibly others: - The gpgkey attribute is set to a URL - The repo_gpgcheck attribute is set to 1 When the above two attributes are set, yum will prompt for user input asking the user whether the GPG key should be imp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Karmo Rosental created an issue Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Issue Type: Improvement Affects Versions: PUP 3.7.1, PUP 3.7.0, PUP 3.6.2, PUP 3.6.1, PUP 3.6.0, PUP 3.5.1, PUP 3.5.0, PUP 3.4.3, PUP 3.4.2, PUP 3.4.1, PUP 3.4.0 Assignee: Andy Parker Components: Modules Created: 16/Oct/14 2:41 PM Environment: All environments with python 3 installed Labels: python Priority: Normal Reporter: Karmo Rosental There is no way to install python 3 package in puppet without long exec blocks or some other hacks. Python 2 package provider is present in Puppet and works well.
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title
Karmo Rosental updated an issue
Puppet / PUP-3480
Puppet does not have Python 3 package provider (pip3)
Change By:
Karmo Rosental
Thereisnowaytoinstallpython3packageinpuppetwithoutlongexecblocksorsomeotherhacks.Python2packageproviderispresentinPuppetandworkswell. Python2packageproviderinPuppetmaster:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip.rbSomebodyhavemadePython3providerthatbasesonPython2provider:https://github.com/openstack-infra/config/blob/master/modules/pip/lib/puppet/provider/package/pip3.rbItestedPython3packageproviderfromopenstack-infrawithfollowingmanifestanditworked:package{['django==1.7']:ensure=present,provider=pip3,require=Package['python3-pip'],}package{['uwsgi==2.0']:ensure=present,provider=pip3,require=Package['python3-pip'],}
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-3396) Add support for testing 4x functions in modules
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3396 Add support for testing 4x functions in modules Change By: Joshua Partlow Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title
Karmo Rosental updated an issue
Puppet / PUP-3480
Puppet does not have Python 3 package provider (pip3)
Change By:
Karmo Rosental
Thereisnowaytoinstallpython3packageinpuppetwithoutlongexecblocksorsomeotherhacks.Python2packageproviderispresentinPuppetandworkswell.Python2packageproviderinPuppetmaster:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip.rb Somebody Openstack-Infra havemadePython3providerthatbasesonPython2provider:https://github.com/openstack-infra/config/blob/master/modules/pip/lib/puppet/provider/package/pip3.rbItestedPython3packageproviderfromopenstack-infrawithfollowingmanifestanditworked:package{['django==1.7']:ensure=present,provider=pip3,require=Package['python3-pip'],}package{['uwsgi==2.0']:ensure=present,provider=pip3,require=Package['python3-pip'],}
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-3396) Add documentation of existing puppetlabs_spec_helper support for testing 4x functions in modules
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3396 Add documentation of existing puppetlabs_spec_helper support for testing 4x functions in modules Change By: Joshua Partlow Summary: Add documentationofexistingpuppetlabs_spec_helper supportfortesting4xfunctionsinmodules 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-3396) Add support for testing 4x functions in modules
Title: Message Title
Joshua Partlow commented on an issue
Re: Add support for testing 4x functions in modules
While working on this with Henrik, Charlie discovered a feature in puppetlabs_spec_helper that fits the bill.
From Charlie Sharpsteen:
I just discovered that this change may not be necessary due to some support built into puppetlabs_spec_helper.
The spec helper can install modules listed in the .fixtures.yml file into spec/fixtures/modules which is placed on the modulepath during test runs. What I was unaware of is there there is a syntax for dynamically generating a symlink to the module under test:
fixtures:
symlinks:
name_of_module_here: #{source_dir}
This accomplishes the goal of making v4 functions loadable.
Marking this for documentation instead, and closing PR-3168 which was adding test specific instrumentation for adding modules.
Add Comment
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Andy Parker updated an issue Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Change By: Andy Parker Issue Type: Improvement NewFeature 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-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Andy Parker updated an issue Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Change By: Andy Parker Component/s: Modules Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Kylo Ginsberg, given that we are pushing again to pull a lot of the core types/providers out, is this something that we would want to add in? Or should we ask openstack-infra to publish it as a separate module? Another option is that we get openstack-infra to contribute the pip3 provider to into puppet and then take it out into a module later when the package type gets split out. Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Change By: Andy Parker Assignee: AndyParker KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3481) Regex problem with an SELinux context type with a dash
Title: Message Title Jude N created an issue Puppet / PUP-3481 Regex problem with an SELinux context type with a dash Issue Type: Bug Affects Versions: PUP 2.7.23 Assignee: Kylo Ginsberg Components: Types and Providers Created: 16/Oct/14 3:27 PM Priority: Normal Reporter: Jude N I have a file on the system with the following SELinux context [root@sut ~]# matchpathcon /etc/my-app/my-config.cfg /etc/my-app/my-config.cfgsystem_u:object_r:my-app_config_t:s0
Jira (PUP-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3396) Add documentation of existing puppetlabs_spec_helper support for testing 4x functions in modules
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-3396 Add documentation of existing puppetlabs_spec_helper support for testing 4x functions in modules Change By: Joshua Partlow Assignee: JoshuaPartlow 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-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title
William Hopper commented on an issue
Re: Windows user provider reports that the password is created instead of changed
Functional review: verified at latest build (SHA 640ec9c1e18257c4680c8f1bbe4ea39339fdcc53) in Windows 2008R2 x86:
In build 640ec9c1 from builds.puppetlabs
Using the following manifest:
user { 'someuser':
name = 'someuser',
password = 'hunter2',
}
The first run of puppet apply manifest.pp produces:
PS C:\Users\Administrator\Desktop puppet apply .\manifest.pp
Notice: Compiled catalog for fqdn in environment production in 0.27 seconds
Notice: /Stage[main]/Main/User[someuser]/ensure: created
Jira (PUP-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title William Hopper updated an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3396) Add support for testing 4x functions in modules
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3396 Add support for testing 4x functions in modules Change By: Joshua Partlow Summary: Add documentationofexistingpuppetlabs_spec_helper supportfortesting4xfunctionsinmodules 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-3396) Add support for testing 4x functions in modules
Title: Message Title Joshua Partlow commented on an issue Re: Add support for testing 4x functions in modules Document-210 created at Nicholas Fagerlund's request so that he and Lauren can review. Add Comment Puppet / PUP-3396 Add support for testing 4x functions in modules When testing a single module with a typical disk layout, the module is usually located in a directory that cannot be used as a modulepath entry. The Loaders helper facade has no public way of adding a module under test to the configuration it builds. While there is nothing preventing a different configuration to be created and used as the loaders for ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2966) Remove stringify_facts option (should never stringify)
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-2966 Remove stringify_facts option (should never stringify) Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3482) server-side only execution stub
Title: Message Title Kevin Corcoran created an issue Puppet / PUP-3482 server-side only execution stub Issue Type: Improvement Assignee: Unassigned Created: 16/Oct/14 3:58 PM Fix Versions: PUP 4.1.0 Priority: Normal Reporter: Kevin Corcoran In puppet-server, we install an 'execution stub' into puppet. The reason for this is that, when no execution stub has been installed, Puppet::Util::Execution.execute eventually ends up calling Kernel.fork to run the command, and Kernel.fork is not available on JRuby. Puppet::Util::Execution.execute takes a second parameter which is a set of options to be used when executing the command. The execution stub used by puppet-server does not support any of these options, for a couple of reasons: we haven't had time to implement them, but more importantly ... it seems like most of them are really only relevant when running an external command on an agent host, not the master. To avoid unnecessarily implementing support for all of those options in puppet-server's execution stub, we would like to change Puppet::Util::Execution.execute to be marked as a agent-side only API, and introduce a new method for use on the server side. This was the conclusion of a discussion with Eric Sorenson. To wrap this up,
Jira (PUP-3482) server-side only execution stub
Title: Message Title
Kevin Corcoran commented on an issue
Re: server-side only execution stub
Andy Parker, Christopher Price - look what i made!
Add Comment
Puppet / PUP-3482
server-side only execution stub
In puppet-server, we install an 'execution stub' into puppet. The reason for this is that, when no execution stub has been installed, {{Puppet::Util::Execution.execute}} eventually ends up calling {{Kernel.fork}} to run the command, and {{Kernel.fork}} is not available on JRuby. {{Puppet::Util::Execution.execute}} takes a second parameter which is a s...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3294) Remove support for :parent
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove support for :parent Kylo Ginsberg Gotcha, thanks for the ping. Removed it. Add Comment Puppet / PUP-3294 Remove support for :parent lib/puppet/metatype/manager.rb:88: Puppet.deprecation_warning option :parent is deprecated. It has no effect This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2609 Don't allow source_permissions to be set to anything other than ignore on Windows Change By: Michael Smith Assignee: MichaelSmith 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-3201) Validation thinks that an Undef instance is of type Runtime
Title: Message Title
Andy Parker commented on an issue
Re: Validation thinks that an Undef instance is of type Runtime
Let's take another stab at this: PR 3210.
This one changes it so that :undef isn't used internally nearly as much anymore. Most of these places are only for the future parser, but a few affect the current system. In the cases that affect the current system, it is only removing some checking that is done to prevent bugs in the development process. However, those checks created a lot of difficulty in keeping nil and :undef straight. Removing those changes only broke a couple of very focused unit tests (that the validation was performed), and allowed using nil in a lot more places.
This fixes both the valuing being reported as Runtime[ruby, Symbol] and allows undef as a value for an Optional type.
Add Comment
Puppet / PUP-3201
Validation thinks that an Undef instance is of type Runtime
Create a define like this: {noformat} define hey(String $x) { notice $x } {noformat} Call it like this: {noformat} hey{'heyer': x = undef } {noformat} Get the somewhat unexpected error: {noformat} Expected parameter 'x' of 'Hey[heyer]' to have type String, got Runtime[ruby, Symbol] {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-3142
exec type should allow passing of arguments as an array rather than a string
Change By:
Andy Parker
Theexectypetakescommandsandargumentsasastring,(@echofoo@)whichwillthengetpassedto/bin/sh(@sh-cechofoo@)byKernel#system.Thiscanmakethingsprettyawkwardifthecommandyou'retryingtoexecutecontainsshellmetacharactersorquotesofitsown,andunderappropriatelypathologicalconditionscouldevenbeasecurityproblem...(username'rm-rf/'orsomething?*shrug*)It'dbegrandiftheexectypewouldsupportpassingthingsaroundasarrays.eg: pre {code} exec{example:command=/bin/echo,arguments=[*,yay,*],} /pre {code} (Passinganarrayto {{ Kernel#system }} bypassestheshellcompletely:http://www.ruby-doc.org/core/classes/Kernel.html#M005982)-sq
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-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title Andy Parker updated an issue Puppet / PUP-3142 exec type should allow passing of arguments as an array rather than a string Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-3142 exec type should allow passing of arguments as an array rather than a string Change By: Andy Parker Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title Joshua Hoblitt commented on an issue Re: exec type should allow passing of arguments as an array rather than a string Passing in an array would be useful when building up lists flags lists for a command. Certainly better than interpolating them all into a string and then regexing out any extra whitespace, which is what I've been doing. However, I don't think adding a separate parameter covers any use case that passing an array to the command parameter doesn't cover. I can't think of a good reason to be able to set the process name either. Add Comment Puppet / PUP-3142 exec type should allow passing of arguments as an array rather than a string The exec type takes commands and arguments as a string, (@echo foo@) which will then get passed to /bin/sh (@sh -c echo foo@) by Kernel#system. This can make things pretty awkward if the command you're trying to execute contains shell metacharacters or quotes of its own, and under appropriately pathological conditions could even be a security probl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/110/ Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/109/ Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber kbarber commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/111/ Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PDB-969) PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber Pull request Correct the ssl-protocols rewrite for the master branch has been closed. Add Comment PuppetDB / PDB-969 PR (1127): Correct the ssl-protocols rewrite for the master branch - kbarber h2. Correct the ssl-protocols rewrite for the master branch * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1127 Discussion|https://github.com/puppetlabs/puppetdb/pull/1127] * [Pull Request 1127 File Diff|https://github.com/puppetlabs/puppetdb/pull/1127/files] h2. Pull ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-970) PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-970 PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt Issue Type: Task Assignee: Unassigned Created: 16/Oct/14 10:08 PM Labels: github module Priority: Normal Reporter: gepetto-bot Allow only TLS - Fixes POODLE CVE-2014-3566 Author: Garrett Honeycutt git...@garretthoneycutt.com Company: Github ID: ghoneycutt Pull Request 150 Discussion Pull Request 150 File Diff Pull Request Description (webhooks-id: 2e0bc244e48e032b6bd45f4ee7abd2e2)
Jira (PDB-970) PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt
Title: Message Title garrett honeycutt updated an issue PuppetDB / PDB-970 PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt Change By: garrett honeycutt Assignee: KennethBarber Issue Type: Task Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-970) PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt
Title: Message Title garrett honeycutt commented on an issue Re: PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt This patch follows the method outlined by Michael Stahnke at http://puppetlabs.com/blog/impact-assessment-sslv3-vulnerability-poodle-attack Add Comment PuppetDB / PDB-970 PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt h2. Allow only TLS - Fixes POODLE CVE-2014-3566 * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 150 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/150] * [Pull Request 150 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
