Issue #8713 has been reported by Nikolay Sturm.

Feature #8713: Add support for defines in Given

• Author: Nikolay Sturm
• Status: Accepted
• Priority: Normal
• Assignee: Nikolay Sturm
• Category:
• Target version:
• Keywords:
• Branch:

https://github.com/nistude/cucumber-puppet/issues/10

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8713 has been updated by Nikolay Sturm.

• Description updated

Feature #8713: Add support for defines in Given

• Author: Nikolay Sturm
• Status: Accepted
• Priority: Normal
• Assignee: Nikolay Sturm
• Category:
• Target version:
• Keywords:
• Branch:

see github

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #7137 has been updated by Craig Smith.

I get the same on 2.7.2rc3 as well, which I believe is now cut from the correct branch.

Let me know if you need any further diagnostics to track this one down.

Bug #7137: useradd provider throws spurious warnings about AIX feature on non-AIX platforms.

• Author: Nigel Kersten
• Status: Merged - Pending Release
• Priority: High
• Assignee: Michael Stahnke
• Category:
• Target version:
• Affected Puppet version: 2.7.0rc1
• Keywords:
• Branch:

info: /User[nigel]: Provider useradd does not support features manages_aix_lam; not managing attribute ia_load_module

It looks to me like this is due to the combination of a required_feature and a defaultto in the type.

RC-introduced bug for 2.7.0rc1

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8714 has been reported by Ioannis Aslanidis.

Bug #8714: Changing SELinux contexts on symlinks requires the '-h' parameter in chcon

• Author: Ioannis Aslanidis
• Status: Unreviewed
• Priority: Normal
• Assignee:
• Category:
• Target version:
• Affected Puppet version: 2.6.9
• Keywords:
• Branch:

There is a problem when trying to chance SELinux contexts through puppet. Looks like puppet does not call chcon with the -h parameter.

# ls -ald /home/file/test lrwxrwxrwx 1 root root 20 Aug 1 12:23 /home/file/test -> /mnt/file/test # chcon -v -t user_home_t test failed to change context of test to system_u:object_r:user_home_t chcon: failed to change context of test to system_u:object_r:user_home_t: Operation not supported # chcon -v -h -t user_home_t test context of /home/file/test changed to system_u:object_r:user_home_t

This results in puppet trying to change the SELinux contexts on every run without success and without knowing that it actually failed.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8715 has been reported by Greg Jastrab.

Bug #8715: Update Milestone Information

• Author: Greg Jastrab
• Status: Unreviewed
• Priority: Normal
• Assignee:
• Category:
• Target version: 2.7.1
• Affected Puppet version:
• Keywords:
• Branch:

The milestone for 2.7.1 still shows incomplete tasks, yet 2.7.1 has been released..? Is the PM aspect of this going to get updated soon?

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #4409 has been updated by Stijn Hoop.

Running into this as well, which was frustrating because all I did was combine the chapter 3 and 10 of the new (and mostly excellent) Pro Puppet book. Due to the very confusing error message it took me a while to connect to this bug.

Note that while the workaround of rsyncing / symlinking the modules into the servers modulepath works, it is still necessary to restart the puppetmaster every time that module changes. That means that practically speaking I cannot really recommend putting new types/providers in modules for 2.6.x, at least when also using environments. I hope it will be fixed in 2.7.x…

Bug #4409: puppetmasterd does not find custom types for environment

• Author: Rudy Gevaert
• Status: Accepted
• Priority: Urgent
• Assignee:
• Category: plumbing
• Target version: 2.7.x
• Affected Puppet version: 2.6.0
• Keywords:
• Branch: http://github.com/MarkusQ/puppet/tree/ticket/2.6.x/4409

Hello,

I can’t get plugins in modules to work. I tried IRC and puppet-users (http://groups.google.com/group/puppet-users/browse_frm/thread/1fa5616448b1ffad) , all led to no help/solution :(. This is blocking me to deploy puppet in our infrastructure.

err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type vcsrepo at /etc/puppet/development/manifests/nodes.pp:37 on node puptest.ugent.be

I have attached several attachments that show my config.

thank you in advance

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8716 has been reported by Dan Urist.

Bug #8716: Ubuntu package should not depend on apache

• Author: Dan Urist
• Status: Unreviewed
• Priority: Normal
• Assignee:
• Category:
• Target version:
• Keywords:
• Branch:
• Affected URL:
• Affected Dashboard version:

Apache should not be a dependency for the ubuntu package. A lot of people are using other webservers these days (e.g. nginx).

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8694 has been updated by Matt Robinson.

Whatever you decide about merging, just let me know in this ticket so I can merge it to the appropriate branch (1.2rc or master) and not forget about it.

Bug #8694: Delayed Job Failures should include stack trace info

• Author: Matt Robinson
• Status: In Topic Branch Pending Merge
• Priority: Normal
• Assignee: Michael Stahnke
• Category:
• Target version: 1.2
• Keywords:
• Branch: https://github.com/mmrobins/puppet-dashboard/tree/ticket/1.2rc/8694-delayedjobfailure_backtrace
• Affected URL:
• Affected Dashboard version:

When reports fail to import it can be difficult to debug without good error messages, and goodness knows we don’t always have the best of those.

The stack trace of the import failure should also be included. Perhaps for better UI it can be something you have to click to expand and see.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #8706 has been updated by Jeff McCune.

• Status changed from In Topic Branch Pending Merge to Merged - Pending Release

Merged¶

Merged as:

commit 4b58cfa945f658679d27bac54ba49403552073b9 Merge: df2f035 8c989eb Author: Jeff McCune Date: Mon Aug 1 10:19:22 2011 -0700 Merge branch 'ticket/master/8706_fix_clopro_spec_tests' * ticket/master/8706_fix_clopro_spec_tests: Whitespace only change. (#8706) Fix spec tests of option validation

Bug #8706: Fix CloPro Faces API method signature problems

• Author: Jeff McCune
• Status: Merged - Pending Release
• Priority: Normal
• Assignee: Jeff McCune
• Category: cloudpack
• Target version: 0.6.0rc2
• Keywords: cloudpack cloudprovisioner clopro
• Branch: git <at> github.com:jeffmccune/puppetlabs-cloud-provisioner.git ticket/master/8706_fix_clopro_spec_tests

Overview¶

In 2.7.x (11e026f53966d4525afef388a2409796bc0d807f) there are a number of spec test failures related to option handling.

Failures: 1) Puppet::Face[:node, v0.0.1] option validation (node-group) should call dashboard_classify if a node_group is specif ied Failure/Error: subject.classify('server', <at> options) Mocha::ExpectationError: unexpected invocation: Puppet::CloudPack.dashboard_classify('server', {:node_group => 'webserver', :extra => {}}) unsatisfied expectations: - expected exactly once, not yet invoked: Puppet::CloudPack.dashboard_classify('server', {:node_group => 'webserv er'}) # /Users/jeff/src/modules/cloud-provisioner/lib/puppet/cloudpack.rb:312:in `classify' # ./../lib/puppet/face/node/classify.rb:18:in `classify implementation, required on Ruby 1.8' # /Users/jeff/src/puppet/lib/puppet/interface/action.rb+eval[wrapper]:203:in `__send__' # /Users/jeff/src/puppet/lib/puppet/interface/action.rb+eval[wrapper]:203:in `classify' # ./unit/puppet/face/node/classify_spec.rb:20 2) Puppet::Face[:node, v0.0.1] option validation (security-group) should split group names into an array Failure/Error: <at> options[:group].should == %w[ A B C D E ] expected: ["A", "B", "C", "D", "E"] got: "A:B:C:D:E" (using ==) Diff: <at> <at> -1,2 +1,2 <at> <at> -["A", "B", "C", "D", "E"] +A:B:C:D:E # ./unit/puppet/face/node/create_spec.rb:86 3) Puppet::Face[:node, v0.0.1] option validation (security-group) should split group names into an array Failure/Error: <at> options[:group].should == %w[ A B C D E ] expected: ["A", "B", "C", "D", "E"] got: "A:B:C:D:E" (using ==) Diff: <at> <at> -1,2 +1,2 <at> <at> -["A", "B", "C", "D", "E"] +A:B:C:D:E # ./unit/puppet/face/node/create_spec.rb:100 Finished in 4.86 seconds 90 examples, 3 failures, 7 pending

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #4428 has been updated by Michael Stahnke.

• Target version changed from 2.7.1 to 2.7.x

Bug #4428: resource titles should allow "::" without requiring quoting for parameterized class declaration

• Author: Stefan Schimanski
• Status: Accepted
• Priority: Normal
• Assignee:
• Category: parser
• Target version: 2.7.x
• Affected Puppet version:
• Keywords: parameterized classes namespaces parser parameterized_classes
• Branch:

Consider a namespace with a parameterized class:

class bla { class foo { } class bar ($x=42) { notify { "x = $x": } } }

To include the nested class into a node one would write:

node default { include bla::foo class { bla::bar: x => 42 } }

which does not work as bla::bar is not a allowed symbol by the parser. You have to quote it:

node default { include bla::foo class { "bla::bar": x => 42 } }

IMHO, Using the title attribute is very strange with this odd syntax as a consequence. Why isn’t there something like:

include bla::foo { x => 42 }

?

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.