Jira (PUP-1243) PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune
Title: Message Title gepetto-bot commented on an issue Re: PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1243 PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune h2. (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 * Author: Jeff McCune j...@puppetlabs.com * Company: Puppet Labs * Github ID: [jeffmccune|https://github.com/jeffmccune] * [Pull Request 2184 Discussion|https://github.com/puppetlabs/puppet/pull/2184] * [Pull Request 2184 File Diff|https://github.com/puppetlabs/puppet/pull/2184/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title
gepetto-bot commented on an issue
Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Savar commented:
Now I remember why I don't like to allow stuff like - 353 . The lexer is interpreting this as a number 353 and does the negation afterwards. And if you get the impression that this is a valid number and you would like to add this to a configuration file or as parameter to a command, you could be suprised by the empty spaces.
I think it is in the responsibility of the user to clean strings if the user knows that strings like above can occur.
So wouldn't it be better to disallow the r {\s}
parts in the regexpressions?
Add Comment
Puppet / PUP-1195
PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1244
Yum provider using version-release to validate installation.
Issue Type:
Bug
Assignee:
Unassigned
Created:
26/Dec/13 3:08 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.
pre $snmp_version = 5.3.2.2 package { net-snmp: ensure = $ {snmp_version}; } /pre Client output: pre debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensure debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 1 change(s) debug: Package[net-snmp](provider=yum): Ensuring = 5.3.2.2 *(1)* debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2' *(2)* debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} ' err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version 5.3.2.2, got version 5.3.2.2-7.el5_4.2 instead at /opt/git/development/modules/snmp/manifests/init.pp:26 notice: //Node[client.example.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Dependency package[net-snmp] has 1 failures warning: //Node[labtest40-v3.ea-colo.ea.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Skipping because of failed dependencies /pre The package is installed *(1)* but the error is still shown at the time of validation *(2)*, same situation if package is already installed. in .../provider/package/yum.rb: pre def install
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar hlindberg commented: Yeah, no whitespace anywhere. Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1245) Arrays and hashes are mutable; new members can be added and existing values changed
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1245
Arrays and hashes are mutable; new members can be added and existing values changed
Issue Type:
Bug
Assignee:
Unassigned
Created:
26/Dec/13 6:13 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Courtesy Henrik: Puppet doesn't let you reassign variables within a given scope, but it lets you change the values of hashes and arrays by mucking with their members. That seems wrong.
$myary = ['zero', 'one', 'two'] $myhash = {first = 'one', second = 'two', third = 'three'}
$myary[3] = 'three' #can insert new element $myary[3] = 'something else' #can reassign notice($myary[3])
$myhash[fourth] = 'four' #can insert new element $myhash[fourth] = 'something else' #can't reassign, fails compilation notice($myhash[fourth])
$myary += ['four'] #can't append in same scope, fails compilation
AND it's inconsistent, so obviously SOMETHING is whacked, even if we actually do want these objects to be mutable.
I don't know what we should do about this. I think the extent to which this is being used in the wild is completely unknown.
Jira (PUP-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title Alexei Romanov created an issue Puppet / PUP-1246 Hiding error details in fileserver.conf parser when this config is wrong Issue Type: Bug Affects Versions: 3.3.3, 3.3.2 Assignee: Alexei Romanov Attachments: fileserver.conf, fix_file_serving_parser_error_handling.diff, test.pp Components: Community Created: 26/Dec/13 6:33 AM Environment: Ubuntu 12.04.3 LTS (GNU/Linux 3.2.0-57-generic x86_64) ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Labels: puppet-fileserver Priority: Normal Reporter: Alexei Romanov
Jira (PUP-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title
Alexei Romanov commented on an issue
Re: Hiding error details in fileserver.conf parser when this config is wrong
https://github.com/puppetlabs/puppet/pull/2185
Add Comment
Puppet / PUP-1246
Hiding error details in fileserver.conf parser when this config is wrong
When I try to apply simple manifest _test.pp_ which is just tries to copy file from puppet master using *puppet://* schema, I receive following error at client node: {code} Error: /Stage[main]//File[/tmp/example-file.txt]: Could not evaluate: Error 403 on SERVER: Forbidden request: mel4102.melesta.local(10.32.32.111) access to /file_metadata/custom_fil...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Savar commented: So any other things I should change? Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1247) Enabling --parser future causes classes to be not found and other errors
Title: Message Title redmine.exporter created an issue Puppet / PUP-1247 Enabling --parser future causes classes to be not found and other errors Issue Type: Bug Assignee: Unassigned Created: 26/Dec/13 7:12 AM Labels: redmine customer Priority: Normal Reporter: redmine.exporter (from a customer) After setting parser = future in puppet.conf, code that was working now causes errors. Sample error: undefined method `value' for Puppet::Pops::Model::AccessExpression:Puppet::Pops::Model::AccessExpression at /etc/puppetlabs/puppet/modules/.../manifests/logic.pp:24 (code sample is in the support ticket, will be linked to in a comment) Add Comment
Jira (PUP-1248) file content audit does not work
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1248
file content audit does not work
Issue Type:
Bug
Assignee:
Unassigned
Created:
26/Dec/13 8:32 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
http://projects.puppetlabs.com/issues/5065 is marked as a documentation issue, but it looks like it isn't just a documentation bug. File content audit does not seem to work.
blockquote It is supposed to work that way, kind of - this behaviour changed recently and the docs apparently haven't been updated. The correct way to do this is now: file { /tmp/bar: audit = content }
exec { '/usr/bin/true': refreshonly = true, subscribe = File['/tmp/bar'] }
So this is a documentation issue. /blockquote
We've tested it on 2.6.* up to 2.6.4 and it gives the following error:
err: /Stage[main]//File[/tmp/bar]: Could not evaluate: Could not retrieve content for {md5}
d404401c8c6495b206fc35c95e55a6d5 from filebucket: File not found at /etc/puppet/manifests/site.pp:1 notice: /Stage[main]//Exec[/usr/bin/true]: Dependency File[/tmp/bar] has failures: true warning: /Stage[main]//Exec[/usr/bin/true]: Skipping because of failed dependencies notice: Finished catalog run in 3.74 seconds
File /tmp/bar exists on the node, we put some random content in that file for our tests.
Jira (PUP-1249) puppet module install --dir option is not working
Title: Message Title Aydin Coskun created an issue Puppet / PUP-1249 puppet module install --dir option is not working Issue Type: Bug Affects Versions: 3.3.3, 3.2.4, 3.4.0 Assignee: Unassigned Components: Modules, QA Created: 26/Dec/13 9:05 AM Environment: Linux localhost.localdomain 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Fix Versions: 3.4.0 Labels: module options commandline Priority: Normal Reporter: Aydin Coskun
Jira (PUP-986) Update CONTRIBUTING and README files
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-986 Update CONTRIBUTING and README files Change By: Andrew Parker Assignee: 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-986) Update CONTRIBUTING and README files
Title: Message Title Andrew Parker commented on an issue Re: Update CONTRIBUTING and README files Merged into Puppet's master in de8d6 Add Comment Puppet / PUP-986 Update CONTRIBUTING and README files With the move to JIRA on Dec 16 we need to update the contributor guidelines where Redmine is mentioned. Links must be updated. The task is to review the guidelines and fix whatever needs fixing wrt. to the move. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1231) PR (214): (doc) Update to point to Jira - zaphod42
Title: Message Title gepetto-bot commented on an issue Re: PR (214): (doc) Update to point to Jira - zaphod42 Pull request (doc) Update to point to Jira has been closed. Add Comment Puppet / PUP-1231 PR (214): (doc) Update to point to Jira - zaphod42 h2. (doc) Update to point to Jira * Author: Andrew Parker * Company: Puppet Labs * Github ID: [zaphod42|https://github.com/zaphod42] * [Pull Request 214 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/214] * [Pull Request 214 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/214/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-986) Update CONTRIBUTING and README files
Title: Message Title Andrew Parker commented on an issue Re: Update CONTRIBUTING and README files Merged into Stdlib's master branch in 01c9c3 Add Comment Puppet / PUP-986 Update CONTRIBUTING and README files With the move to JIRA on Dec 16 we need to update the contributor guidelines where Redmine is mentioned. Links must be updated. The task is to review the guidelines and fix whatever needs fixing wrt. to the move. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1099) incorrect permissions in rpms
Title: Message Title Ryan McKern updated an issue Puppet / PUP-1099 incorrect permissions in rpms Merged in #42315be410556560072cda4f5dab41246f391126 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-122) PR (170): (doc) Update links to point to Jira - zaphod42
Title: Message Title gepetto-bot commented on an issue Re: PR (170): (doc) Update links to point to Jira - zaphod42 Pull request (doc) Update links to point to Jira has been closed. Add Comment Hiera / HI-122 PR (170): (doc) Update links to point to Jira - zaphod42 h2. (doc) Update links to point to Jira * Author: Andrew Parker * Company: Puppet Labs * Github ID: [zaphod42|https://github.com/zaphod42] * [Pull Request 170 Discussion|https://github.com/puppetlabs/hiera/pull/170] * [Pull Request 170 File Diff|https://github.com/puppetlabs/hiera/pull/170/files] h2. Pull Request Description Since we chang... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-986) Update CONTRIBUTING and README files
Title: Message Title Andrew Parker commented on an issue Re: Update CONTRIBUTING and README files Merged into Hiera's master branch in 2f8d52 Add Comment Puppet / PUP-986 Update CONTRIBUTING and README files With the move to JIRA on Dec 16 we need to update the contributor guidelines where Redmine is mentioned. Links must be updated. The task is to review the guidelines and fix whatever needs fixing wrt. to the move. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-178) PR (588): (doc) Update to point to the new Jira instance - zaphod42
Title: Message Title gepetto-bot commented on an issue Re: PR (588): (doc) Update to point to the new Jira instance - zaphod42 Pull request (doc) Update to point to the new Jira instance has been closed. Add Comment Facter / FACT-178 PR (588): (doc) Update to point to the new Jira instance - zaphod42 h2. (doc) Update to point to the new Jira instance * Author: Andrew Parker * Company: Puppet Labs * Github ID: [zaphod42|https://github.com/zaphod42] * [Pull Request 588 Discussion|https://github.com/puppetlabs/facter/pull/588] * [Pull Request 588 File Diff|https://github.com/puppetlabs/facter/pull/588/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-986) Update CONTRIBUTING and README files
Title: Message Title Andrew Parker commented on an issue Re: Update CONTRIBUTING and README files Merged into Facter's facter-2 branch in 9629ed Add Comment Puppet / PUP-986 Update CONTRIBUTING and README files With the move to JIRA on Dec 16 we need to update the contributor guidelines where Redmine is mentioned. Links must be updated. The task is to review the guidelines and fix whatever needs fixing wrt. to the move. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1243) PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune
Title: Message Title gepetto-bot commented on an issue Re: PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune Pull request (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 has been closed. Add Comment Puppet / PUP-1243 PR (2184): (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 - jeffmccune h2. (maint) Fix can't modify frozen Symbol error on Ruby 2.1.0 * Author: Jeff McCune j...@puppetlabs.com * Company: Puppet Labs * Github ID: [jeffmccune|https://github.com/jeffmccune] * [Pull Request 2184 Discussion|https://github.com/puppetlabs/puppet/pull/2184] * [Pull Request 2184 File Diff|https://github.com/puppetlabs/puppet/pull/2184/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-546) Remove Hiera2 and bindings-based data in modules code
Title: Message Title Andrew Parker commented on an issue Re: Remove Hiera2 and bindings-based data in modules code Henrik Lindberg, I can't find a PR for this nor does it look like something has been merged in already. Add Comment Puppet / PUP-546 Remove Hiera2 and bindings-based data in modules code After a lot of discussion we have decided that this is not the right way to proceed. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1051) gem package provider is confused by platform components in version strings
Title: Message Title
Pedro Crte-Real commented on an issue
Re: gem package provider is confused by platform components in version strings
Submitted a pull request for this:
https://github.com/puppetlabs/puppet/pull/2186
Add Comment
Puppet / PUP-1051
gem package provider is confused by platform components in version strings
Using: package{'facter': ensure = latest, provider = 'gem', source = http://puppet:8808, } Produces:notice: /Stage[main]/Common_puppet::Hpux/Package[facter]/ensure: ensure changed '1.6.17' to '1.6.17 ruby' This happens on every puppet run.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title
Andrew Parker commented on an issue
Re: Hiding error details in fileserver.conf parser when this config is wrong
Merged into master in e5effa
Add Comment
Puppet / PUP-1246
Hiding error details in fileserver.conf parser when this config is wrong
When I try to apply simple manifest _test.pp_ which is just tries to copy file from puppet master using *puppet://* schema, I receive following error at client node: {code} Error: /Stage[main]//File[/tmp/example-file.txt]: Could not evaluate: Error 403 on SERVER: Forbidden request: mel4102.melesta.local(10.32.32.111) access to /file_metadata/custom_fil...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1246 Hiding error details in fileserver.conf parser when this config is wrong Change By: Andrew Parker Fix Version/s: 3.5.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-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1246 Hiding error details in fileserver.conf parser when this config is wrong Change By: Andrew Parker Sprint: Week2013-12-19to2014-1-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-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1246 Hiding error details in fileserver.conf parser when this config is wrong Change By: Andrew Parker Assignee: AlexeiRomanov 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-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu nanliu commented: In testing, we have more issues around provider suitability where it's picking up providers for no good reason on SLES: ``` Warning: Found multiple default providers for package: pe_gem, zypper; using pe_gem ``` So I'm dependent on a way to exclude suitability via :default_provider = 'false'. Seems like a core puppet bug, but haven't tracked down the root cause. Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1194) PR (2177): Add guide to running local acceptance tests. - aperiodic
Title: Message Title gepetto-bot commented on an issue Re: PR (2177): Add guide to running local acceptance tests. - aperiodic Pull request Add guide to running local acceptance tests. has been closed. Add Comment Puppet / PUP-1194 PR (2177): Add guide to running local acceptance tests. - aperiodic h2. Add guide to running local acceptance tests. * Author: Dan Lidral-Porter * Company: * Github ID: [aperiodic|https://github.com/aperiodic] * [Pull Request 2177 Discussion|https://github.com/puppetlabs/puppet/pull/2177] * [Pull Request 2177 File Diff|https://github.com/puppetlabs/puppet/pull/2177/files] h2. Pull Request Description Poin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1250) PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1250 PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 26/Dec/13 11:11 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Fix rdoc generator for Ruby 2.1.0 Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2187 Discussion Pull Request 2187 File Diff Pull Request Description Ruby 2.1.0 includes RDoc
Jira (PDB-224) PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe
Title: Message Title gepetto-bot commented on an issue Re: PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe cprice404 commented: This was closed in favor of #780 , which is rebased and addresses all of the comments on this PR. Add Comment PuppetDB / PDB-224 PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe h2. FOR REVIEW: Port PuppetDB to use trapperkeeper * Author: Nate Wolfe * Company: Puppet Labs * Github ID: [nwolfe|https://github.com/nwolfe] * [Pull Request 773 Discussion|https://github.com/puppetlabs/puppetdb/pull/773] * [Pull Request 773 File Diff|https://github.com/puppetlabs/puppetdb/pull/773/files] h2. Pull Request Description This... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-224) PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe
Title: Message Title gepetto-bot commented on an issue Re: PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe Pull request FOR REVIEW: Port PuppetDB to use trapperkeeper has been closed. Add Comment PuppetDB / PDB-224 PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe h2. FOR REVIEW: Port PuppetDB to use trapperkeeper * Author: Nate Wolfe * Company: Puppet Labs * Github ID: [nwolfe|https://github.com/nwolfe] * [Pull Request 773 Discussion|https://github.com/puppetlabs/puppetdb/pull/773] * [Pull Request 773 File Diff|https://github.com/puppetlabs/puppetdb/pull/773/files] h2. Pull Request Description This... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 created an issue PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 Issue Type: Task Assignee: Unassigned Created: 26/Dec/13 11:31 AM Labels: github Priority: Normal Reporter: gepetto-bot Refactor to trapperkeeper Author: Chris Price Company: Github ID: cprice404 Pull Request 780 Discussion Pull Request 780 File Diff Pull Request Description This PR is a replacement for #773. It is rebased onto the latest PuppetDB master branch, updated to use released versions of trapperkeeper and kitchensink, and addresses all of the comments that were made on that PR. (webhooks-id: a3ccf39d06574db7c866b4d8d08aff67)
Jira (PDB-87) Review trapperkeeper PR when it is ready
Title: Message Title Christopher Price commented on an issue Re: Review trapperkeeper PR when it is ready Pull request 780 should be good to go. It is rebased, uses non-SNAPSHOT versions of trapperkeeper and kitchensink, and addresses all of the comments that we received from the PR review. Add Comment PuppetDB / PDB-87 Review trapperkeeper PR when it is ready As per recent discussions in e-mail/hipchat, we should have a PR coming in soon that will contain a slight refactor to move PuppetDB over to the trapperkeeper framework. This ticket is just a link to the PE ticket, to make sure that this is visible on the PuppetDB side. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1144) No longer allows variables with leading underscores
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson Puppet / PUP-1144 No longer allows variables with leading underscores Change By: Eric Sorenson Assignee: HenrikLindberg EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1250) PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog Pull request (maint) Fix rdoc generator for Ruby 2.1.0 has been closed. Add Comment Puppet / PUP-1250 PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog h2. (maint) Fix rdoc generator for Ruby 2.1.0 * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2187 Discussion|https://github.com/puppetlabs/puppet/pull/2187] * [Pull Request 2187 File Diff|https://github.com/puppetlabs/puppet/pull/2187/files] h2. Pull Request Description Ruby 2.1.0 includes... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1250) PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog jeffmccune commented: Beat me to it @kylog This PR fixes the last remaining issues with the spec examples with Ruby 2.1.0 that I found. It looks good to me, I ran the suite locally on Ruby 2.1.0 and Travis ran it successfully against our other supported Ruby versions. Merged #2187 -Jeff Add Comment Puppet / PUP-1250 PR (2187): (maint) Fix rdoc generator for Ruby 2.1.0 - kylog h2. (maint) Fix rdoc generator for Ruby 2.1.0 * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2187 Discussion|https://github.com/puppetlabs/puppet/pull/2187] * [Pull Request 2187 File Diff|https://github.com/puppetlabs/puppet/pull/2187/files] h2. Pull Request Description Ruby 2.1.0 includes... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PUP-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog jpartlow commented: The thing is, if we check it prior to unpacking the artifact, we don't have access to the creator.txt which is what provides a link back to the packaging job from which we can find the pipeline jobs that failed. Add Comment Puppet / PUP-1215 PR (2180): (maint) Check package build status earlier in bootstrap - kylog h2. (maint) Check package build status earlier in bootstrap * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180] * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files] h2. Pull Request Description I thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group,
Jira (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/111/ 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-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar hlindberg commented: is_integer needs more tests. It may be of value to create a shared test since is_numeric also needs to be tested with all integer combinations. Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog zaphod42 commented: I agree with @jpartlow. Maybe just remove the `-v` from the tar command. I doubt that we ever care what is in the tarball. And if we have a question we can always look at the workspace. Add Comment Puppet / PUP-1215 PR (2180): (maint) Check package build status earlier in bootstrap - kylog h2. (maint) Check package build status earlier in bootstrap * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180] * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files] h2. Pull Request Description I thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-798) New Evaluator does not cache parse results
Title: Message Title Henrik Lindberg commented on an issue Re: New Evaluator does not cache parse results See comment on the PR. Add Comment Puppet / PUP-798 New Evaluator does not cache parse results The new evaluator does not cache parse result; everything is reparsed on every request. In the previous version the future parser also used an instance of the old parser to perform imports and to handle caching of parse results. This was obviously inefficient and was removed. The support for caching should be added. It should however not be impl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog kylog commented: Good call. Add Comment Puppet / PUP-1215 PR (2180): (maint) Check package build status earlier in bootstrap - kylog h2. (maint) Check package build status earlier in bootstrap * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180] * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files] h2. Pull Request Description I thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog Pull request (maint) Check package build status earlier in bootstrap has been closed. Add Comment Puppet / PUP-1215 PR (2180): (maint) Check package build status earlier in bootstrap - kylog h2. (maint) Check package build status earlier in bootstrap * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180] * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files] h2. Pull Request Description I thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1247) Enabling --parser future causes classes to be not found and other errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1247 Enabling --parser future causes classes to be not found and other errors Change By: Henrik Lindberg Affects Version/s: 3.4.1 Affects 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-1247) Enabling --parser future causes classes to be not found and other errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1247 Enabling --parser future causes classes to be not found and other errors Change By: Henrik Lindberg Fix Version/s: 3.5.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-1247) Enabling --parser future causes classes to be not found and other errors
Title: Message Title Henrik Lindberg commented on an issue Re: Enabling --parser future causes classes to be not found and other errors This is fixed in Puppet 3.5 --parser future. There is currently no plan to fix this for --parser future in the 3.4.x series. Add Comment Puppet / PUP-1247 Enabling --parser future causes classes to be not found and other errors (from a customer) After setting parser = future in puppet.conf, code that was working now causes errors. Sample error: undefined method `value' for Puppet::Pops::Model::AccessExpression:Puppet::Pops::Model::AccessExpression at /etc/puppetlabs/puppet/modules/.../manifests/logic.pp:24 (code sample is in the support ticket, will be linked to ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1251) PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1251 PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 26/Dec/13 12:56 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Drop -v flag when untarring acceptance artifacts Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2189 Discussion Pull Request 2189 File Diff Pull Request Description
Jira (PUP-1215) PR (2180): (maint) Check package build status earlier in bootstrap - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2180): (maint) Check package build status earlier in bootstrap - kylog kylog commented: https://github.com/puppetlabs/puppet/pull/2189 removes the `-v` Add Comment Puppet / PUP-1215 PR (2180): (maint) Check package build status earlier in bootstrap - kylog h2. (maint) Check package build status earlier in bootstrap * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2180 Discussion|https://github.com/puppetlabs/puppet/pull/2180] * [Pull Request 2180 File Diff|https://github.com/puppetlabs/puppet/pull/2180/files] h2. Pull Request Description I thi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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 (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (780): Refactor to trapperkeeper - cprice404 puppetcla commented: CLA signed by all contributors. 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 https://groups.google.com/groups/opt_out.
Jira (PUP-1252) It should be possible to assign a definition to a node in an external nodes tool
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1252
It should be possible to assign a definition to a node in an external nodes tool
Issue Type:
New Feature
Assignee:
Unassigned
Created:
26/Dec/13 1:00 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Until now, only classes/modules and parameters can be assigned to nodes in an external nodes tool.
It would be very useful to be able to assign a definition, such as:
pre node ws1 inherits webserver { apache::vhost {www.example.com}
} /pre
to a node using yaml. The only other way to do now, seems to be writing wrapper classes.
Thanks,
Pieter.
Add Comment
Jira (PUP-1251) PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1251 PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog h2. (maint) Drop -v flag when untarring acceptance artifacts * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2189 Discussion|https://github.com/puppetlabs/puppet/pull/2189] * [Pull Request 2189 File Diff|https://github.com/puppetlabs/puppet/pull/2189/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-1253) systemd service provider should support masking
Title: Message Title redmine.exporter created an issue Puppet / PUP-1253 systemd service provider should support masking Issue Type: New Feature Assignee: Unassigned Created: 26/Dec/13 3:40 PM Labels: redmine Priority: Normal Reporter: redmine.exporter systemd knows three states for a service: enabled, disabled and masked. So far, the latter state doesn't seem to be supported by puppet's systemd service provider. The difference of disabling and masking a service is as follows: a disabled service can be started as a dependency of another service or be started manually by a user. A masked service can neither. Masking is done the same way as enabling or disabling: systemctl enable|disable|mask service So kindly implement either enable = mask(ed), ensure = masked (not sure what seems more logical) or mask(ed) = true|false in the systemd service provider. Note: there's also a unmask command to systemctl. I figure ensure = enabled|disabled should always unmask the service additionally to enable|disable it. Manpage: http://0pointer.de/public/systemd-man/systemctl.html
Jira (PUP-905) PR (2117): (#22800) apply proper scoping rules to scope#to_hash - ffrank
Title: Message Title gepetto-bot commented on an issue Re: PR (2117): (#22800) apply proper scoping rules to scope#to_hash - ffrank ffrank commented: Thanks @hlindberg - I amended the spec patch accordingly. The test I had pending is now run only for the future parser. Add Comment Puppet / PUP-905 PR (2117): (#22800) apply proper scoping rules to scope#to_hash - ffrank h2. (#22800) apply proper scoping rules to scope#to_hash * Author: * Company: * Github ID: [ffrank|https://github.com/ffrank] * [Pull Request 2117 Discussion|https://github.com/puppetlabs/puppet/pull/2117] * [Pull Request 2117 File Diff|https://github.com/puppetlabs/puppet/pull/2117/files] h2. Pull Request Description The fix for #1427 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 (PUP-1251) PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog Pull request (maint) Drop -v flag when untarring acceptance artifacts has been closed. Add Comment Puppet / PUP-1251 PR (2189): (maint) Drop -v flag when untarring acceptance artifacts - kylog h2. (maint) Drop -v flag when untarring acceptance artifacts * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2189 Discussion|https://github.com/puppetlabs/puppet/pull/2189] * [Pull Request 2189 File Diff|https://github.com/puppetlabs/puppet/pull/2189/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-1015) Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368
Title: Message Title
Dominic Cleal commented on an issue
Re: Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368
Note, this wasn't released in 3.4.1 as the ticket says - 3.4.1 was a security release and this patch seems to have been held back. Presumably it'll go out in 3.4.2 instead.
Add Comment
Puppet / PUP-1015
Error: Could not intialize global default settings: undefined method `mode=' for #Puppet::Settings::AutosignSetting:0x7ff361614368
Follow-on from #23349... regression from 3.3.x to 3.4.0-rc2. This affects all Foreman users, since it's the default installer configuration (https://github.com/theforeman/puppet-puppet/blob/master/templates/puppet.conf.erb#L21). With this in puppet.conf: {code} [main] autosign = $confdir/autosign.conf { mode = 664 } {code} {code} # 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
Jira (PUP-1213) PR (2179): (maint) Provide option to 4x-3x convert to handle :undef differently - hlindberg
Title: Message Title gepetto-bot commented on an issue Re: PR (2179): (maint) Provide option to 4x-3x convert to handle :undef differently - hlindberg Pull request (maint) Provide option to 4x-3x convert to handle :undef differently has been closed. Add Comment Puppet / PUP-1213 PR (2179): (maint) Provide option to 4x-3x convert to handle :undef differently - hlindberg h2. (maint) Provide option to 4x-3x convert to handle :undef differently * Author: Henrik Lindberg * Company: Cloudsmith Inc. * Github ID: [hlindberg|https://github.com/hlindberg] * [Pull Request 2179 Discussion|https://github.com/puppetlabs/puppet/pull/2179] * [Pull Request 2179 File Diff|https://github.com/puppetlabs/puppet/pull/2179/files] h... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1254) PR (2190): Issue/master/pup 798 watched files - jpartlow
Title: Message Title gepetto-bot created an issue Puppet / PUP-1254 PR (2190): Issue/master/pup 798 watched files - jpartlow Issue Type: Task Assignee: Unassigned Components: Community Created: 26/Dec/13 7:53 PM Labels: github Priority: Normal Reporter: gepetto-bot Issue/master/pup 798 watched files Author: Josh Partlow Company: Github ID: jpartlow Pull Request 2190 Discussion Pull Request 2190 File Diff Pull Request Description A refactor of #2181
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 jpartlow commented: @hlindberg @zaphod42 I made some changes to address the concerns about how we were verifying that we had something we could call watch_file on. Henrik, I also removed the EParserAdapter, as it seemed to be unused now, but I'm wondering if you were keeping that for an --evaluator flag switch? So perhaps the last commit should should be removed from this? 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
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 puppetcla commented: CLA signed by all contributors. 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-1246) Hiding error details in fileserver.conf parser when this config is wrong
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1246 Hiding error details in fileserver.conf parser when this config is wrong Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
