Cucumber-Puppet

Nikolay,

I have cucumber-puppet 0.3.2 and Puppet 2.7.3 — is it the reason “catalog compilation” fails? The log:

$ cucumber-puppet features/catalog/policy.feature 
Feature: General policy for all catalogs
  In order to ensure applicability of a host's catalog
  As a manifest developer
  I want a catalog apply to a real node

  Scenario Outline: Compile and verify catalog for r4            # features/catalog/policy.feature:6
    Given a node specified by "features/yaml/r4.osinka.int.yaml" # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:1
    When I compile its catalog                                   # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:14
    Then compilation should succeed                              # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:38
    And all resource dependencies should resolve                 # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:18

    Examples: 
      | hostname | operatingsystem | kernel | is_virtual | domain     |
uninitialized constant Puppet::Node::Catalog
      | r4       | Debian          | Linux  | false      | osinka.int |
      exit (SystemExit)
      features/catalog/policy.feature:8:in `When I compile its catalog'

Failing Scenarios:
cucumber features/catalog/policy.feature:6 # Scenario: Compile and verify catalog for r4

1 scenario (1 failed)
4 steps (1 failed, 2 skipped, 1 passed)
0m0.009s

Hi there I’m also getting the same error under puppet-2.6.0 (sorry!) puppet-2.7.1 and cucumber-puppet-0.3.2.

$ cucumber-puppet features/catalog/policy.feature
Feature: General policy for all catalogs
In order to ensure applicability of a host's catalog
As a manifest developer
I want all catalogs to obey some general rules
Scenario Outline: Compile and verify catalog                           # features/catalog/policy.feature:6
Given a node specified by "features/yaml/<hostname>.i3-dev.net.yaml" # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:1
When I compile its catalog                                           # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:14
Then compilation should succeed                                      # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:38
And all resource dependencies should resolve                         # cucumber-puppet-0.3.2/lib/cucumber-puppet/steps.rb:18
Examples:
| hostname        |
uninitialized constant Puppet::Node::Catalog
| uuka3v-prx01    |
exit (SystemExit)
features/catalog/policy.feature:8:in `When I compile its catalog'
|uninitialized constant Puppet::Node::Catalog
uuka3v-portal01 |
exit (SystemExit)
features/catalog/policy.feature:8:in `When I compile its catalog'
Failing Scenarios:
cucumber features/catalog/policy.feature:6 # Scenario: Compile and verify catalog
cucumber features/catalog/policy.feature:6 # Scenario: Compile and verify catalog
2 scenarios (2 failed)
8 steps (2 failed, 4 skipped, 2 passed)
0m0.079s

Martin Jackson wrote:

Hi there I’m also getting the same error under puppet-2.6.0 and cucumber-puppet-0.3.2.

Are you sure you don’t have puppet 2.7 installed? I cannot reproduce this error with any 2.6 version of puppet. You might want to checkout the cucumber-puppet source and run rake puppet_version, that explicitly checks all kinds of puppet versions.

Alexander Azarov wrote:

I have cucumber-puppet 0.3.2 and Puppet 2.7.3 — is it the reason “catalog compilation” fails?

Yes, it’s the same problem. Give me a couple of days…

Sorry my bad rvm says I have puppet 2.7.1 while my rpm is 2.6.0.