Jira (PUP-1162) puppet resource error with no suitable provider: Could not run: undefined method `exists?' for nil:NilClass
Title: Message Title
Carlos Sanchez updated an issue
Puppet / PUP-1162
puppet resource error with no suitable provider: Could not run: undefined method `exists?' for nil:NilClass
Change By:
Carlos Sanchez
Following[theresourcesdocumentation](http://docs.puppetlabs.com/learning/ral.html)Iexecutethefollowingcommandasnormaluserandget: pre {code} igalic@tynix~%puppetresourceuserrootError:Couldnotrun:undefinedmethod`exists?'fornil:NilClass1igalic@tynix~%puppetresourceuserigalicError:Couldnotrun:undefinedmethod`exists?'fornil:NilClass1igalic@tynix~% /pre {code} Whenexecutingthesamecommandsasroot,Igettheexpectedresults: pre {code} tynix~#puppetresourceuserrootuser{'root':ensure='present',comment='root',gid='0',groups=['root','bin','daemon','sys','adm','disk','wheel'],home='/root',shell='/bin/bash',uid='0',}tynix~#puppetresourceuserigalicuser{'igalic':ensure='present',comment='IgorGalić',gid='501',groups=['wheel','jupiter','rvm'],home='/home/igalic',shell='/bin/zsh',uid='500',}tynix~# /pre {code} Environment:@ruby1.9.3p327(2012-11-10revision37606)[x86_64-linux]@
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian commented on an issue Re: Allow wildcards in hierarchy Yeah, you are right. 1. could be easy to fix 2. fixing yaml could be easy, but could be dozens of custom backends that will get broken 3. My problem is I want projects to define their own hostgroups, host templates, etc, and one node, Icinga/Nagios host, to implement all of them. But sure, reading and parsing dozens of json files in each lookup is definitely a bad idea. I am thinking moving to some other backend as mysql or redis. Thanks! Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1270
'pkg' package provider does not understand IPS package versions properly
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 2:37 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
It would seem the 'pkg' provider (for illumos/Solaris/OpenSolaris IPS) does not do the right thing with IPS package versions. We're running OmniOS and seeing this:
kekkonen ~ % pfexec puppet apply -e 'package {mdb: ensure = latest }
' Notice: Compiled catalog for kekkonen.niksula.hut.fi in environment production in 1.17 seconds Notice: Finished catalog run in 6.39 seconds kekkonen ~ % pfexec pkg update -nv mdb Packages to update: 1 Estimated space available: 14.11 TB Estimated space to be consumed: 24.61 MB Create boot environment: No Create backup boot environment: Yes Rebuild boot archive: No
Changed packages: omnios developer/debug/mdb 0.5.11,5.11-0.151006:20130731T194820Z - 0.5.11,5.11-0.151006:20131019T183740Z
So puppet thinks there are no updates, but pkg correctly notices that an update is available (only the timestamp has changed, not the version, build release, or branch numbers).
puppet resource provides some insight into this:
kekkonen ~ % puppet resource package mdb package { 'mdb': ensure = '0.5.11-0.151006', }
This version number is not correct, it's missing the build release (5.11) and timestamp.
Jira (PUP-1271) puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key.
Title: Message Title redmine.exporter created an issue Puppet / PUP-1271 puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key. Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 4:49 AM Labels: redmine Priority: Normal Reporter: redmine.exporter On my puppetmaster server (using Apache, PhusionPassenger, puppet 3.1.0-1 on Debian Squeeze), attempting to run puppet ca list --all fails with: Error: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: [[REDACTED]] To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean [[REDACTED]] On the agent: rm -f /etc/puppet/ssl/certs/[[REDACTED]].pem puppet agent -t Error: Try 'puppet help ca list' for usage I have used openssl x509 -in /path/to/cert.pem -fingerprint -md5 -nooout to check the fingerprints on all certs and they DO match. Additionally, running puppet cert list --all works without issue.
Jira (PUP-1272) Improve puppet apply to support network device
Title: Message Title redmine.exporter created an issue Puppet / PUP-1272 Improve puppet apply to support network device Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 4:50 AM Labels: redmine Priority: Normal Reporter: redmine.exporter After writing additional network device, it seems reasonable to support device in puppet apply. Currently network resources are skipped: debug: /Stage[main]//F5_virtualserver[www-http]: Skipping device resources because running on a host debug: /Stage[main]//F5_virtualserver[www-https]: Skipping device resources because running on a host Rather than having two separate modules with slight differences (see: https://github.com/puppetlabs/puppetlabs-f5/issues/42). It makes sense to ensure puppet resource and puppet apply also supports --deviceconfig option. Add Comment
Jira (PUP-1272) Improve puppet apply to support network device
Title: Message Title Anup Nair commented on an issue Re: Improve puppet apply to support network device Please could you let us know if this issue can be fixed or if there are any workarounds for this issue. Add Comment Puppet / PUP-1272 Improve puppet apply to support network device After writing additional network device, it seems reasonable to support device in puppet apply. Currently network resources are skipped: debug: /Stage[main]//F5_virtualserver[www-http]: Skipping device resources because running on a host debug: /Stage[main]//F5_virtualserver[www-https]: Skipping device resources because running on a host Ra... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title
Lauri Tirkkonen commented on an issue
Re: 'pkg' package provider does not understand IPS package versions properly
https://github.com/puppetlabs/puppet/pull/2200
Add Comment
Puppet / PUP-1270
'pkg' package provider does not understand IPS package versions properly
It would seem the 'pkg' provider (for illumos/Solaris/OpenSolaris IPS) does not do the right thing with IPS package versions. We're running OmniOS and seeing this: kekkonen ~ % pfexec puppet apply -e 'package {mdb: ensure = latest }' Notice: Compiled catalog for kekkonen.niksula.hut.fi in environment production in 1.17 seconds Notice...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1273) Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed
Title: Message Title redmine.exporter created an issue Puppet / PUP-1273 Error message ssl_connect returned=1 errno=0 state=sslv3 read server certificate b: certificate verify failed Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 6:49 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The following error message comes up commonly, based on search results. Information about the error: http://projects.puppetlabs.com/projects/puppet Unfortunately, I have not experienced this error directly. If you are experiencing this error, please append detailed logging information using the --verbose, --debug, and --evaltrace options. Add Comment
Jira (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (780): Refactor to trapperkeeper - cprice404 senior commented: Other than the two minor things I pointed out, looks good! I like the namespaced keywords for the error types. Add Comment PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 h2. Refactor to trapperkeeper * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 780 Discussion|https://github.com/puppetlabs/puppetdb/pull/780] * [Pull Request 780 File Diff|https://github.com/puppetlabs/puppetdb/pull/780/files] h2. Pull Request Description This PR is a replacement 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
Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot created an issue Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek Issue Type: Task Assignee: Unassigned Components: Community Created: 30/Dec/13 7:56 AM Labels: github Priority: Normal Reporter: gepetto-bot PE-2123 Do not fail hard on unparseable files Author: Filip Hrbek filip.hr...@gmail.com Company: Github ID: fhrbek Pull Request 2201 Discussion Pull Request 2201 File Diff Pull Request Description
Jira (PDB-245) PR (109): Support rspec-puppet v1.0.0 - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (109): Support rspec-puppet v1.0.0 - ghoneycutt senior commented: test this please Add Comment PuppetDB / PDB-245 PR (109): Support rspec-puppet v1.0.0 - ghoneycutt h2. Support rspec-puppet v1.0.0 * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 109 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/109] * [Pull Request 109 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/109/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (780): Refactor to trapperkeeper - cprice404 cprice404 commented: SNAPSHOT test dependency is fixed. Will wait to hear response on the github docs link before making any changes there. Add Comment PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 h2. Refactor to trapperkeeper * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 780 Discussion|https://github.com/puppetlabs/puppetdb/pull/780] * [Pull Request 780 File Diff|https://github.com/puppetlabs/puppetdb/pull/780/files] h2. Pull Request Description This PR is a replacement 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
Jira (PUP-1249) puppet module install --dir option is not working
Title: Message Title John Duarte updated an issue Puppet / PUP-1249 puppet module install --dir option is not working Change By: John Duarte Labels: commandlinemoduleoptions qa-reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1015) Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1015 Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368 Change By: Andrew Parker Fix Version/s: 3.4.1 Fix Version/s: 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1254) PR (2190): Issue/master/pup 798 watched files - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2190): Issue/master/pup 798 watched files - jpartlow hlindberg commented: Look good now. Merged. Add Comment Puppet / PUP-1254 PR (2190): Issue/master/pup 798 watched files - jpartlow h2. Issue/master/pup 798 watched files * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2190 Discussion|https://github.com/puppetlabs/puppet/pull/2190] * [Pull Request 2190 File Diff|https://github.com/puppetlabs/puppet/pull/2190/files] h2. Pull Request Description A refactor of #2181 ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1254) PR (2190): Issue/master/pup 798 watched files - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2190): Issue/master/pup 798 watched files - jpartlow Pull request Issue/master/pup 798 watched files has been closed. Add Comment Puppet / PUP-1254 PR (2190): Issue/master/pup 798 watched files - jpartlow h2. Issue/master/pup 798 watched files * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2190 Discussion|https://github.com/puppetlabs/puppet/pull/2190] * [Pull Request 2190 File Diff|https://github.com/puppetlabs/puppet/pull/2190/files] h2. Pull Request Description A refactor of #2181 ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (780): Refactor to trapperkeeper - cprice404 puppetlabs-jenkins commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/112/ Add Comment PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 h2. Refactor to trapperkeeper * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 780 Discussion|https://github.com/puppetlabs/puppetdb/pull/780] * [Pull Request 780 File Diff|https://github.com/puppetlabs/puppetdb/pull/780/files] h2. Pull Request Description This PR is a replacement 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.
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title
Andrew Parker commented on an issue
Re: Default file mode is now 0600 instead of 0644
Kylo Ginsberg, Joshua Partlow, and I investigated this. It is happening because in the case when a mode it not specified the mode on the resulting file is now determined by the mode applied to the tempfile, which is moved into place. Since tempfiles receive fairly restrictive permissions we end up with 0600 on the resulting file.
Add Comment
Puppet / PUP-1255
Default file mode is now 0600 instead of 0644
As of Puppet 3.4.1 and 2.7.24, the default file mode when no mode is explicitly specified on a file resource has changed from 0644 to 0600. It appears from the commits (https://github.com/puppetlabs/puppet/commit/65909fbe and 691fbbeaa) that this was not the intention. {noformat} # rpm -q puppet puppet-3.4.0-1.el6.noarch # puppet apply -e 'file { ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1255 Default file mode is now 0600 instead of 0644 Change By: Andrew Parker Fix Version/s: 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1249) puppet module install --dir option is not working
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1249 puppet module install --dir option is not working Change By: Andrew Parker Fix Version/s: 3.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Encoding mis-matches cause package prefetching to fail
On CentOS and Debian Wheezy, I can only re-produce this if I explicitly force Puppet to run in an ASCII locale:
# LANG=C LC_ALL=C puppet resource package
Error: Could not run: invalid byte sequence in US-ASCII
# puppet resource package
package { 'acpi':
ensure = '1.6-1',
}
package { 'acpi-support-base':
ensure = '0.140-5',
}
package { 'acpid':
ensure = '1:2.0.16-1',
}
...
Add Comment
Puppet / PUP-736
Encoding mis-matches cause package prefetching to fail
One of our RPM packages has some UTF-8 characters in its description, leading to an exception (Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII) in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error. Priority=High because it breaks file { ensure = latest; }.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1255 Default file mode is now 0600 instead of 0644 Change By: Andrew Parker Fix Version/s: 2.7.25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1255 Default file mode is now 0600 instead of 0644 Change By: Andrew Parker Assignee: DominicCleal AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot commented on an issue Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek h2. PE-2123 Do not fail hard on unparseable files * Author: Filip Hrbek filip.hr...@gmail.com * Company: * Github ID: [fhrbek|https://github.com/fhrbek] * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201] * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1275) Windows agent only runs when --onetime is specified
Title: Message Title redmine.exporter created an issue Puppet / PUP-1275 Windows agent only runs when --onetime is specified Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:18 AM Labels: redmine Priority: Normal Reporter: redmine.exporter In 2.7.x, you could run the windows agent as `puppet agent` or `puppet agent --no-onetime` and the agent would periodically retrieve and apply catalogs. In 3.0.2, in commit 4d1a2f83d9 (#17361), the agent was modified to fork when not doing a onetime run. But this breaks Windows, because fork is not implemented. This was not detected earlier because the windows service always runs the agent with `--onetime`. There are also no acceptance tests around this behavior. Add Comment
Jira (PUP-1275) Windows agent only runs when --onetime is specified
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1275 Windows agent only runs when --onetime is specified Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Justin Stoller updated an issue Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud Change By: Justin Stoller Priority: Normal Trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-123) hiera json backend is broken on puppet 3.1.1 for windows
Title: Message Title Joshua Cooper updated an issue Hiera / HI-123 hiera json backend is broken on puppet 3.1.1 for windows Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-123) hiera json backend is broken on puppet 3.1.1 for windows
Title: Message Title
redmine.exporter created an issue
Hiera / HI-123
hiera json backend is broken on puppet 3.1.1 for windows
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
30/Dec/13 10:23 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
From this example: http://www.craigdunn.org/2011/10/puppet-configuration-variables-and-hiera/
pre C:\Users\Administrator\temp type hiera.yaml :backends: - json
:logger: console
:hierarchy: - % {env}
common :json: :datadir: hieradata
C:\Users\Administrator\temp\hieradatatype common.json { webname: localhost }
C:\Users\Administrator\temp\hieradatatype dev.json { webname: dev.app.local }
C:\Users\Administrator\temphiera -c hiera.yaml webname C:/Puppet/sys/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem original_require': no such file to load json (LoadError) from C:/Puppet/sys/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.b:36:in `require' from C:/Puppet/hiera/lib/hiera/backend/json_backend.rb:5:in `initialize from C:/Puppet/hiera/lib/hiera/backend.rb:158:in `new' from C:/Puppet/hiera/lib/hiera/backend.rb:158:in `lookup' from C:/Puppet/hiera/lib/hiera/backend.rb:156:in `each' from C:/Puppet/hiera/lib/hiera/backend.rb:156:in `lookup' from C:/Puppet/hiera/lib/hiera.rb:62:in `lookup' from C:/Puppet/hiera/bin/hiera:220 /pre
Jira (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Justin Stoller commented on an issue Re: Hiera stable acceptance testing for Solaris with Vcloud Getting the solaris and windows jobs to function have become a very low priority because the hiera tests use puppet apply on the master (or so is my understanding of what I've been told). So these tests aren't actually runny hiera on the agent, and regardless there's no platform specific code (so the value here really comes in doing a final test of packaging/integration). I don't think they are worth spending any time on until we are ready to use packages in the hiera pipeline. Add Comment Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1276) Tidy causes 'Cannot alias' ArgumentError exception on Windows
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1276
Tidy causes 'Cannot alias' ArgumentError exception on Windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 10:24 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
This example: pre class puppet-bug {
file { 'C:\bug': ensure = directory, }
tidy { 'C:\bug': recurse = true, backup = false }
file { 'C:\bug\test.txt': content = 'Look, a bug!' }
} /pre
Causes this error:
pre err: Got an uncaught exception of type ArgumentError: Cannot alias File[C:\bug/test.txt] to [C:/bug/test.txt]; resource [File, C:/bug/test.txt] already declared at /etc/puppet/modules/puppet-bug/manifests/init.pp:14 /pre
It appears to be due to the way slashes are handled on Windows. If you change the tidy to 'C:/bug' it all works just fine and the duplicate resource is detected and excluded from the tidy as expected.
That might be an acceptable fix, except when you're using variables for File resources that are also used as msiexec parameters and thus can't have Unix slashes.
Jira (PUP-1277) service does not implement custom start / stop commands on windows
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1277
service does not implement custom start / stop commands on windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 10:25 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
The provider for service does not have support for explicit start and stop commands, however the documentation does not mention that limitation.
Example (taken from the mcollective module): precode service { $mc_service_name: ensure = running, enable = true, hasstatus = true, start = $mc_service_start, stop = $mc_service_stop, }
/code/pre Windows will still run the default command, which is:
C:\Windows\System32\net.exe $mc_service_name start
C:\Windows\System32\net.exe $mc_service_name stop
In stead of the specified start and stop commands.
The fix could be a simple as this: precode lib\puppet\provider\service\windows-orig.rb 2013-06-17 17:23:16 +0200 +++ lib\puppet\provider\service\windows.rb 2013-10-25 11:57:42 +0200 @@ -73,13 +73,21 @@ end end
net(:start, @resource[:name]) + if
Jira (PUP-1278) Windows Puppet Agent Service gracefully terminates after succesfully being put into a Paused state
Title: Message Title redmine.exporter created an issue Puppet / PUP-1278 Windows Puppet Agent Service gracefully terminates after succesfully being put into a Paused state Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:26 AM Labels: redmine Priority: Normal Reporter: redmine.exporter If you successfully pause the Windows Puppet Agent Server, then after a period of time the Puppet Agent service will gracefully stop. This does not appear to be appropriate behaviour. The service should remain in a paused state until a Continue or Stop message is sent to the service. It looks like it's to do with the following lines; while running? do return if state != RUNNING According to ruby doco [1] running? is defined as the service is in a RUNNING, PAUSED or IDLE state, but the following line terminates the main loop if the service is not in the running state. It seems that the return if state != RUNNING line is not really required [1] http://rubydoc.info/gems/win32-service/0.8.2/frames Add
Jira (PUP-1277) service does not implement custom start / stop commands on windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1277 service does not implement custom start / stop commands on windows Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1279
Windows Group and User fail during deletion even though it is successful
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 10:26 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
This is due to commit being called in the flush method when it should not be.
Steps to reproduce:
1. Create a user `puppet apply -e user {'FakeTestUser': ensure = present, password = 'nobodyknowssupersecret', }
2. Delete a user - `puppet apply -e user {'FakeTestUser': ensure = absent, }
pre Notice: /User[FakeTestUser]/ensure: removed Error: /User[FakeTestUser]: Could not evaluate: User update failed: ADSI connection error: failed to parse display name of moniker `WinNT://./FakeTestUser,user' HRESULT error code:0x800708ad The user name could not be found. C:/code/puppetlabs/puppet/lib/puppet/util/adsi.rb:101:in `rescue in commit' C:/code/puppetlabs/puppet/lib/puppet/util/adsi.rb:98:in `commit' C:/code/puppetlabs/puppet/lib/puppet/provider/user/windows_adsi.rb:54:in `flush'
C:/code/puppetlabs/puppet/lib/puppet/type.rb:963:in `flush' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:144:in `evaluate' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:161:in `apply' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:174:in `eval_resource' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:104:in `call' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:104:in `block (2 levels) in evaluate'
Jira (PUP-1280) windows agents don't parse runinterval as a duration setting
Title: Message Title redmine.exporter created an issue Puppet / PUP-1280 windows agents don't parse runinterval as a duration setting Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:27 AM Labels: redmine Priority: Normal Reporter: redmine.exporter When running as a service, puppet on windows runs `puppet agent --configprint runinterval` and assumes the result is in seconds. It then runs `puppet agent --onetime` every runinterval seconds. In 3.0.0, runinterval was changed to a `duration` setting, so it can be of the form 5m, 2h, etc http://docs.puppetlabs.com/references/latest/configuration.html#runinterval. This was done in commit [2cb9b503](https://github.com/puppetlabs/puppet/commit/2cb9b503c427c75b45ba47a0ea538ae95342bee2) Add Comment
Jira (PUP-1278) Windows Puppet Agent Service gracefully terminates after succesfully being put into a Paused state
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1278 Windows Puppet Agent Service gracefully terminates after succesfully being put into a Paused state Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Justin Stoller updated an issue Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud Change By: Justin Stoller Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1179) puppet agent service can't start when using GBK encoding in windows environment
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1179 puppet agent service can't start when using GBK encoding in windows environment Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1276) Tidy causes 'Cannot alias' ArgumentError exception on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1276 Tidy causes 'Cannot alias' ArgumentError exception on Windows Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title redmine.exporter created an issue Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:28 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/luislavena/win32console/issues/17#issuecomment-20811539 Add Comment
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1280) windows agents don't parse runinterval as a duration setting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1280 windows agents don't parse runinterval as a duration setting Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1283) Update win32-service gem
Title: Message Title redmine.exporter created an issue Puppet / PUP-1283 Update win32-service gem Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:29 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The win32-service gem was patched upstream to resolve #16080. The fix was merged upstream https://github.com/djberg96/win32-service/pull/8. At a minimum we need to update the gem and remove the patch https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3/16080-handle-missing-description.patch. We also need to make sure we can update to the `ffi` branch of `win32-service` without running into the same problem again https://github.com/djberg96/win32-service/pull/8#issuecomment-20688123 Add Comment
Jira (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (780): Refactor to trapperkeeper - cprice404 puppetlabs-jenkins commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/113/ Add Comment PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 h2. Refactor to trapperkeeper * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 780 Discussion|https://github.com/puppetlabs/puppetdb/pull/780] * [Pull Request 780 File Diff|https://github.com/puppetlabs/puppetdb/pull/780/files] h2. Pull Request Description This PR is a replacement 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.
Jira (PUP-1283) Update win32-service gem
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1283 Update win32-service gem Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1284 win32-security gem doesn't handle 'Authenticated Users' correctly Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title redmine.exporter created an issue Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:28 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The puppet gem on windows has dependencies on win32-dir, etc, but these are not expressed in the gemspec file. So if you are developing a module, and attempt to `bundle install`, the transitive dependencies are not satisfied. The same issue exists in facter and hiera. Add Comment
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1049) Windows puppet service should log to the eventlog
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1049 Windows puppet service should log to the eventlog Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1287) Manage both 32 and 64-bit packages with the same name
Title: Message Title redmine.exporter created an issue Puppet / PUP-1287 Manage both 32 and 64-bit packages with the same name Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:35 AM Labels: redmine Priority: Normal Reporter: redmine.exporter From Windows user: citeI'd like to install 2 instance of SQL Server 2008 R2 Analysis - 32bit and 64bit - which can be done, using the package resource with a MSI. Unfortunately, they have the exact same name in 'Programs Features' on w2k8r2. If I rename one and install them, it installs itself every 30 minutes. /cite Add Comment
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1286) Automatically backslashify windows MSI package sources
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1286 Automatically backslashify windows MSI package sources Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1285) Allow windows to manage hidden applications
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1285 Allow windows to manage hidden applications Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly
Title: Message Title redmine.exporter created an issue Puppet / PUP-1284 win32-security gem doesn't handle 'Authenticated Users' correctly Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:31 AM Labels: redmine Priority: Normal Reporter: redmine.exporter If you attempt to add a user to the 'Authenticated Users' group, the owner/group of a file, etc the win32-security gem incorrectly maps this to SID `S-1-5-0` instead of `S-1-5-11`. The gem calls `String#strip` on the binary SID structure, which is of the form: ...x0bx00, and 0x0b is vertical tab, which ruby considers to be white space, and strips it. See https://github.com/djberg96/win32-security/issues/3 Add Comment
Jira (PUP-1288) Windows user provider fails to create user with non-ASCII characters
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1288
Windows user provider fails to create user with non-ASCII characters
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 10:36 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
The windows_adsi user provider essentially does the following when creating a user:
pre require 'Win32API' require 'win32ole'
def computer_name buf = * 128 Win32API.new('kernel32', 'GetComputerName', ['P','P'], 'I').call(buf, buf.length.to_s) buf.unpack(A*) end
conn = WIN32OLE.connect(WinNT://# {computer_name}
) user = conn.Create('user', name) user.SetPassword(password) user.SetInfo /pre
On Ruby 1.8.7, this succeeds, but results in a corrupt username when using the name 'Евгений'. I think this is because ruby's implementation (win32ole.c) defaults to ANSI codepage, so internally it tries to convert MultiByteToWideChar using the wrong codepage. There is a `WIN32OLE.codepage=` method, but it only accepts a select number of options in 1.8.7.
Also the `Puppet::Util::ADSI.computer_name` calls `buf.unpack('A*')` when building the ADSI connection string. This returns an array, instead of a string. In ruby 1.8.7, it automatically converts the array to a string.
On Ruby 1.9.3, WIN32OLE uses the right code page, and puppet would set the username correctly, but since ruby 1.9 doesn't automatically convert the array to a string, it fails. The `buf.unpack('A*')` line should be removed as
Jira (PUP-1287) Manage both 32 and 64-bit packages with the same name
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1287 Manage both 32 and 64-bit packages with the same name Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly
Title: Message Title Joshua Cooper commented on an issue Re: win32-security gem doesn't handle 'Authenticated Users' correctly This issue was fixed in win32-security version 0.2.3, which is ffi based. We're currently on 0.1.4 (non-ffi), so it should just be a matter of moving to the latest version. Add Comment Puppet / PUP-1284 win32-security gem doesn't handle 'Authenticated Users' correctly If you attempt to add a user to the 'Authenticated Users' group, the owner/group of a file, etc the win32-security gem incorrectly maps this to SID `S-1-5-0` instead of `S-1-5-11`. The gem calls `String#strip` on the binary SID structure, which is of the form: ...x0bx00, and 0x0b is vertical tab, which ruby considers to be white space, and strips it. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-1288) Windows user provider fails to create user with non-ASCII characters
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1288 Windows user provider fails to create user with non-ASCII characters Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1289) Ability to manage a windows service's user account and password
Title: Message Title redmine.exporter created an issue Puppet / PUP-1289 Ability to manage a windows service's user account and password Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 10:37 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Puppet should be able to manage the username and password of a windows service, similar to how it does for scheduled tasks. From presales support ticket #17700. Add Comment This message was sent by
Jira (PUP-1285) Allow windows to manage hidden applications
Title: Message Title redmine.exporter created an issue Puppet / PUP-1285 Allow windows to manage hidden applications Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 10:34 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Currently, the windows package provider excludes hidden applications (those whose SystemComponent registry value is set to 1) from its `instances` method (both exe and msi). This is done so that puppet has parity with what is displayed in Add/Remove Programs, e.g. `SQL Server 2008 R2 SP2 Common Files`. But it means if you install a hidden application, then puppet won't know it's installed, and try to reinstall it next time. For example, https://groups.google.com/d/topic/puppet-users/ftvvO51bX1U/discussion Add Comment
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1165 Spurious 'trigger changed' messages generated by scheduled task provider Change By: Joshua Cooper Labels: customerredmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1289) Ability to manage a windows service's user account and password
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1289 Ability to manage a windows service's user account and password Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1286) Automatically backslashify windows MSI package sources
Title: Message Title redmine.exporter created an issue Puppet / PUP-1286 Automatically backslashify windows MSI package sources Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:35 AM Labels: redmine Priority: Normal Reporter: redmine.exporter When installing an MSI, the windows package provider passes the package source parameter to msiexec.exe. Unfortunately, it bmust/b use backslashes, otherwise, msiexec thinks it's a command line argument and will fail with a cryptic error: preFailed to install: Fail on INT 24./pre The windows package provider should automatically convert the source to backslashes so that it just works. Add Comment
Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title redmine.exporter created an issue Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 10:38 AM Labels: redmine Priority: Normal Reporter: redmine.exporter As stated in the Puppet documentation (http://docs.puppetlabs.com/windows/writing.html#scheduledtaskscheduledtask), the scheduled_task resource type does not support repetition modes such as every X minutes. It is a pity, because such tasks are very commonly used in Windows servers (and maybe less on Windows clients), making scheduled_task not so useful. It is true that the configuration of Windows scheduled task is complicated (as opposed to crontab...); we may not need all the features available in the Windows GUI (like Until, Duration or If the task is still running, stop it at this time), I guess it would be enough to support every X minutes and every Y hours. Add Comment
Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1290) Puppet should support *.msp upgrade packages on Windows
Title: Message Title redmine.exporter created an issue Puppet / PUP-1290 Puppet should support *.msp upgrade packages on Windows Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 10:38 AM Labels: redmine customer Priority: Normal Reporter: redmine.exporter Puppet client on Windows should make enable installing *.msp upgrade packages. For example when I'm trying to install update file to previously installed msi package client responds with error message like below: pre change from absent to present failed: Don't know how to install 'c:\AdbeRdrUpd1013.msp' /pre *.msp packages are installed in the same way as *.msi files. The only difference is /p switch instead if /i Add Comment
Jira (PUP-1290) Puppet should support *.msp upgrade packages on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1290 Puppet should support *.msp upgrade packages on Windows Change By: Joshua Cooper Labels: customerredmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1292) Chocolatey package provider on Windows
Title: Message Title redmine.exporter created an issue Puppet / PUP-1292 Chocolatey package provider on Windows Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 10:39 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Investigate chocolatey package provider: http://chocolatey.org/br https://github.com/rismoney/puppet-chocolatey Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1292) Chocolatey package provider on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1292 Chocolatey package provider on Windows Change By: Joshua Cooper Labels: redmine windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1258) Puppet should be filesystem ACL aware
Title: Message Title
Patrick Hemmer commented on an issue
Re: Puppet should be filesystem ACL aware
Here is a provider I wrote which subclasses the POSIX provider, and uses getfacl/setfacl to manage permissions. It properly solves all the issues listed.
Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
Puppet::Type.type(:file).provide :posix_facl, :parent = :posix do
desc Uses POSIX file ACL functionality to manage file ownership and permissions.
initvars
commands :getfacl = 'getfacl', :setfacl = 'setfacl'
def mode
mode = super
return mode unless mode.is_a?(String)
mode = mode.to_i(8)
output = getfacl('--', resource[:path])
mode_parts = {}
output.split(\n).each do |line|
next if line[0] == '#'
if line.match(/^(user|group|other)::(\S+)/) then
mode_parts[$1] = $2
end
end
mode_str = u=#{mode_parts['user'].gsub('-','')},g=#{mode_parts['group'].gsub('-','')},o=#{mode_parts['other'].gsub('-','')}
# we take the original mode from the POSIX provider, strip off the last 3 octal digits, and replace them with what we got from `getfacl`
mode = (mode 07000) | (resource.symbolic_mode_to_int(mode_str) 0777)
mode.to_s(8)
end
def mode=(value)
setfacl('-m', user::#{value[-3]},group::#{value[-2]},other::#{value[-1]}, '--', resource[:path])
if value.length = 4 then
# we also need to set flags (which can't be done with setfacl (without a `--restore`)). Pull the current mode, strip off the flags, then add our flags on to it, and then use the normal chmod
File.chmod((File.stat(resource[:path]).mode 00777) | (value.to_i(8) 07000), resource[:path])
end
end
end
Add Comment
Puppet / PUP-1258
Puppet should be filesystem ACL aware
Jira (HI-124) Write tests to test hiera on agent platforms
Title: Message Title Justin Stoller updated an issue Hiera / HI-124 Write tests to test hiera on agent platforms Change By: Justin Stoller Currentlythehierafunctionaltestsdon'tdoanythingonagentplatforms.Weneedtowritenewtestsorrefactorexistingteststoensurethathappens.SeeHI-8 Hi HI -9. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-124) Write tests to test hiera on agent platforms
Title: Message Title Justin Stoller created an issue Hiera / HI-124 Write tests to test hiera on agent platforms Issue Type: Bug Assignee: Kurt Wall Components: QA Created: 30/Dec/13 10:50 AM Priority: Normal Reporter: Justin Stoller Currently the hiera functional tests don't do anything on agent platforms. We need to write new tests or refactor existing tests to ensure that happens. See HI-8 Hi-9. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1293) service status is ignored ( puppet 3.2 + upstart provider )
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1293
service status is ignored ( puppet 3.2 + upstart provider )
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 10:50 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
pre cat test.pp EOF notice(os = $::operatingsystem, puppetversion = $::puppetversion) exec { 'run': command = /sbin/status network-interface INTERFACE=eth0, logoutput = true, }
- service { 'network-interface': ensure = running, status = '/sbin/status network-interface INTERFACE=eth0', }
EOF puppet apply test.pp /pre will output the following pre Notice: Scope(Class[main]): os = Ubuntu, puppetversion = 3.2.4 Notice: /Stage[main]//Exec[run]/returns: network-interface (eth0) start/running Notice: /Stage[main]//Exec[run]/returns: executed successfully Error: /Stage[main]//Service[network-interface]: Could not evaluate: Execution of '/sbin/status network-interface' returned 1: status: Unknown parameter: INTERFACE Notice: Finished catalog run in 0.27 seconds /pre
Add Comment
Jira (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Justin Stoller updated an issue Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud Change By: Justin Stoller Assignee: JoshuaPartlow KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Justin Stoller updated an issue Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Change By: Justin Stoller Assignee: JustinStoller KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1294) The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys
Title: Message Title redmine.exporter created an issue Puppet / PUP-1294 The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys Issue Type: Bug Assignee: Unassigned Created: 30/Dec/13 10:58 AM Labels: redmine Priority: Normal Reporter: redmine.exporter I have a particular configuration where a custom NSS plugin intercepts getent passwd calls and replaces the login shell with a new shell. In this situation, using the standard 'user' resource causes a false-positive for Puppet where it thinks the shell is configured as this new value, but it should be set to the value specified in the manifest. Unfortunately, setting 'forcelocal' to 'true' does not appear to solve the issue. I did a little looking through the code, and as far as I can tell, only certain specific subkeys (uid, gid, etc.) utilize the 'forcelocal' parameter (and the login shell is unfortunately not one of them). If 'forcelocal' does not support certain keys than (IMO) either: 1. The documentation should be updated to explicitly list the supported keys 2. The behavior should change so that all of the keys are supported. 3. The login shell key is made compatible with 'forcelocal', and #1 is done to boot for the remaining keys to avoid future confusion about this issue Right now this is not a huge blocker, but it's requiring me to avoid validating the local settings for login shells wherever this custom NSS module is being used. As a side note, my 'libuser' Puppet feature appears to be loading correctly (which is a prereq for 'forcelocal')
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
Issue Type:
Bug
Assignee:
Unassigned
Created:
30/Dec/13 11:00 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; }
[root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '% {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm --version' debug: Puppet::Type::Package::ProviderUrpmi: Executing '/bin/rpm -ql rpm' debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --version' debug: Puppet::Type::Package::ProviderAptrpm: Executing '/bin/rpm -ql rpm' debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portupgrade does not exist debug: Puppet::Type::Package::ProviderAptitude: file /usr/bin/aptitude does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does not exist debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does not exist debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgrm does not exist debug: Puppet::Type::Package::ProviderAptrpm: file apt-get does not
Jira (PUP-1133) Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist
Title: Message Title Joshua Cooper commented on an issue Re: Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist Merged in bc89aec to be released in 3.5.0 Add Comment Puppet / PUP-1133 Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist If %ALLUSERSPROFILE%\PuppetLabs\puppet (C:\ProgramData\PuppetLabs\puppet on Win2008 R2) does not exist, a number of failures are generated. On cursory examination, manually creating `C:\ProgramData\PuppetLabs` is not sufficient to remove the errors. One work-around that *does* work is to run the Windows MSI package, allow it to create `C:\ProgramDat... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1211) Puppet Resource Package fails
Title: Message Title
Louis Mayorga commented on an issue
Re: Puppet Resource Package fails
Yeah,
I guess so but i did rebuilt my desktop machine with puppet and now is working fine. I don't use the PowerGUI (Just a Powershell experiment a while ago.)
Add Comment
Puppet / PUP-1211
Puppet Resource Package fails
Trying to get all windows package resources i get the following error {code} ruby 1.9.3p448 (2013-06-27) [i386-mingw32] C:\Windows\system32puppet resource package Error: Could not run: invalid byte sequence in US-ASCII {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-168) Changed domain and fqdn facts
Title: Message Title Brandon Ooi commented on an issue Re: Changed domain and fqdn facts Hi guys, is there any final word on what the correct behavior is? We use virtual machines heavily and reverse dns isn't set up when we run puppet for the first time (in fact, we use puppet to do it). In my opinion, it's incorrect behavior to basically guess the hostname by what's in /etc/resolv.conf. It should fall back to whatever hostname reports. Also, how would this work if the machine is being run independently at a remote location (no dns changes...) Add Comment Facter / FACT-168 Changed domain and fqdn facts I just updated a bunch of RHEL6 systems from facter 1.6.18 to 1.7.2, and for some reason the domain and fqdn facts have changed. I think it's related to the fix in issue #20938, since all of the servers affected have non-resolvable hostnames. Before : pre [root@d01 ~]# facter domain fqdn hostname domain = evo.example.com fqdn = d01.evo.exampl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PUP-1133) Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1133 Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez
Title: Message Title Joshua Cooper commented on an issue Re: PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez Merged in 9ea2f7f to be released in 3.5.0. Add Comment Puppet / PUP-797 PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez h2. (#23219) - Fix support of extra arguments in windows service * Author: Luis Fernndez lvarez * Company: CERN * Github ID: [luisfdez|https://github.com/luisfdez] * [Pull Request 2094 Discussion|https://github.com/puppetlabs/puppet/pull/2094] * [Pull Request 2094 File Diff|https://github.com/puppetlabs/puppet/pull/2094/files] h2. Pull Request... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot commented on an issue Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek fhrbek commented: @hlindberg Thanks for your comments. I fixed the erros typo and answered your question, however as I force pushed the comments are now hidden So, whoever is interested in what Henrik asked about, please disclose the second outdated diff. The question was about where to find the parse errors, it's probably a problem that needs to be solved. I appreciate any help in this area (as I am not the puppet core developer I don't know where it fits the best). Add Comment Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek h2. PE-2123 Do not fail hard on unparseable files * Author: Filip Hrbek filip.hr...@gmail.com * Company: * Github ID: [fhrbek|https://github.com/fhrbek] * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201] * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1296) PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1296 PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 30/Dec/13 12:10 PM Labels: github Priority: Normal Reporter: gepetto-bot Issue/master/pup 1255 incorrect default permissions Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2202 Discussion Pull Request 2202 File Diff Pull Request Description
Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot commented on an issue Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek kylog commented: Can you enter a PUP ticket for this and reference it in the commit message? Also, travis is faling, though I didn't look at what the failure was. Add Comment Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek h2. PE-2123 Do not fail hard on unparseable files * Author: Filip Hrbek filip.hr...@gmail.com * Company: * Github ID: [fhrbek|https://github.com/fhrbek] * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201] * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1192) PR (2176): (maint) Windows file provider :links = :follow - Iristyle
Title: Message Title Joshua Cooper assigned an issue to Unassigned Puppet / PUP-1192 PR (2176): (maint) Windows file provider :links = :follow - Iristyle Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-797 PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez Change By: Joshua Cooper Assignee: RobReynolds JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1296) PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog Pull request Issue/master/pup 1255 incorrect default permissions has been closed. Add Comment Puppet / PUP-1296 PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog h2. Issue/master/pup 1255 incorrect default permissions * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2202 Discussion|https://github.com/puppetlabs/puppet/pull/2202] * [Pull Request 2202 File Diff|https://github.com/puppetlabs/puppet/pull/2202/files] h2. Pull Request Description (w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-246) One item array are casted to String when stored in puppetdb
Title: Message Title
Maxence Dunnewind created an issue
PuppetDB / PDB-246
One item array are casted to String when stored in puppetdb
Issue Type:
Bug
Affects Versions:
2.x
Assignee:
Unassigned
Created:
30/Dec/13 12:36 PM
Environment:
Debian 7. Puppet vm : facter 1.7.4-1puppetlabs1 hiera 1.3.0-1puppetlabs1 puppet 3.4.1-1puppetlabs1 puppet-common 3.4.1-1puppetlabs1 puppet-dashboard 1.2.23-1puppetlabs1 puppetdb-terminus 1.5.2-1puppetlabs1 puppetlabs-release 1.0-7 puppetmaster 3.4.1-1puppetlabs1 puppetmaster-common 3.4.1-1puppetlabs1 puppetmaster-passenger 3.4.1-1puppetlabs1 ruby-rgen 0.6.5-1puppetlabs1
puppetdb vm: puppetdb 1.5.2-1puppetlabs1
Priority:
Normal
Reporter:
Maxence Dunnewind
When I try to create an exported resource (in my exemple a nginx::resource::vhost) with some parameters containing a one-item array, it is casted to String in puppetdb :
@@nginx::resource::vhost { 'my resource': ensure = present, server_name = ['first item'], listen_port = 9200, proxy = http://${::fqdn} }
In puppetdb I get :
puppetdb=# select * from resource_params where resource = '0e27f67d04b10bf659967bc8ecc704fa767bf278';
Jira (PUP-1297) PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1297 PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 30/Dec/13 12:37 PM Labels: github Priority: Normal Reporter: gepetto-bot Issue/master/pup 1255 incorrect default permissions Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2203 Discussion Pull Request 2203 File Diff Pull Request Description
Jira (PUP-1297) PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog Pull request Issue/master/pup 1255 incorrect default permissions has been closed. Add Comment Puppet / PUP-1297 PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog h2. Issue/master/pup 1255 incorrect default permissions * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2203 Discussion|https://github.com/puppetlabs/puppet/pull/2203] * [Pull Request 2203 File Diff|https://github.com/puppetlabs/puppet/pull/2203/files] h2. Pull Request Description (w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1255) Default file mode is now 0600 instead of 0644
Title: Message Title
Andrew Parker commented on an issue
Re: Default file mode is now 0600 instead of 0644
Merged into stable in 6cabaa
Add Comment
Puppet / PUP-1255
Default file mode is now 0600 instead of 0644
As of Puppet 3.4.1 and 2.7.24, the default file mode when no mode is explicitly specified on a file resource has changed from 0644 to 0600. It appears from the commits (https://github.com/puppetlabs/puppet/commit/65909fbe and 691fbbeaa) that this was not the intention. {noformat} # rpm -q puppet puppet-3.4.0-1.el6.noarch # puppet apply -e 'file { ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title redmine.exporter created an issue Puppet / PUP-1298 manage_membership for unix groups provider Issue Type: New Feature Assignee: Unassigned Created: 30/Dec/13 1:03 PM Labels: redmine Priority: Normal Reporter: redmine.exporter I searched and didn't see this feature request so if is/was at some point forgive me. I'd like to be able to define the users that belong to a group in the group's resource. My compelling reason is that a specific unix group is used to determine ssh access via AllowGroups in sshd_config, and I'd like to make sure that at all times only specific users are in that group. My workaround is to manage /etc/group as a file resource, which isn't very puppet-like. Add Comment
Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek
Title: Message Title gepetto-bot commented on an issue Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek fhrbek commented: I'll at the travis failure and the PUP ticket tomorrow. Add Comment Puppet / PUP-1274 PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek h2. PE-2123 Do not fail hard on unparseable files * Author: Filip Hrbek filip.hr...@gmail.com * Company: * Github ID: [fhrbek|https://github.com/fhrbek] * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201] * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Antoine commented on an issue Re: manage_membership for unix groups provider There seems to be a working provider here: https://github.com/pdxcat/puppet-module-group/blob/master/lib/puppet/provider/group/ggroupadd.rb Looks simple enough/ Add Comment Puppet / PUP-1298 manage_membership for unix groups provider I searched and didn't see this feature request so if is/was at some point forgive me. I'd like to be able to define the users that belong to a group in the group's resource. My compelling reason is that a specific unix group is used to determine ssh access via AllowGroups in sshd_config, and I'd like to make sure that at all times only specific users a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-247) Fix Schema warning, replacing String and Number
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-247 Fix Schema warning, replacing String and Number Issue Type: Bug Affects Versions: 1.6.0 Assignee: Unassigned Created: 30/Dec/13 1:41 PM Fix Versions: 2.0 Priority: Normal Reporter: Ryan Senior Due to this issue: https://github.com/Prismatic/schema/issues/21 we're seeing warnings like: WARNING: String already refers to: class java.lang.String in namespace: schema.core, being replaced by: #'schema.core/String WARNING: Number already refers to: class java.lang.Number in namespace: schema.core, being replaced by: #'schema.core/Number to stderr. We should be able to fork it and fix it, or if someone beats us to it, just upgrade. Add Comment
Jira (PUP-1192) PR (2176): (maint) Windows file provider :links = :follow - Iristyle
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1192 PR (2176): (maint) Windows file provider :links = :follow - Iristyle Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-168) Changed domain and fqdn facts
Title: Message Title Justin Honold commented on an issue Re: Changed domain and fqdn facts http://serverfault.com/questions/562842/name-resolution-difference-between-centos-and-debian could be in play too, on resolv.conf stuff? I ran into that ticket (as well as the Redmine base for this ticket) when I updated Facter on my own CentOS boxes, and started getting different results. Add Comment Facter / FACT-168 Changed domain and fqdn facts I just updated a bunch of RHEL6 systems from facter 1.6.18 to 1.7.2, and for some reason the domain and fqdn facts have changed. I think it's related to the fix in issue #20938, since all of the servers affected have non-resolvable hostnames. Before : pre [root@d01 ~]# facter domain fqdn hostname domain = evo.example.com fqdn = d01.evo.exampl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
