Yes kevin,
I am using acceptance tests using beaker-rspec.

beaker (1.19.1)
beaker-rspec (3.0.0)

By the way, now that Josh clarified I understand why agent did not work.

Thanks for sparing time though to look at the problem.
:-)

Regards,
Manish


On Tuesday, October 28, 2014 11:57:07 PM UTC+5:30, Kevin Imber wrote:
>
> Hi Manish,
>
> I'm having some trouble reproducing the problem that you're seeing.  This 
> is working for me with the tests given using generic beaker, although I'm 
> using a different hypervisor at the moment.
>
> Are you using beaker-rspec and the modules acceptance tests?
>
> Thanks,
> Kevin
>
>
>
> On Tuesday, October 28, 2014 2:10:11 AM UTC-7, Manish Sapariya wrote:
>>
>> Hi,
>> I have the nodeset definition as follows..
>>
>> ---------- Some of the attributes removed for clarity 
>> ----------------------
>> HOSTS:
>>   kpointvm1.zencite.com:
>>     roles:
>>       - master
>>     hypervisor : vagrant
>>   kpointvm2.zencite.com:
>>     roles:
>>       - agent
>>     hypervisor : vagrant
>> ----------------------
>>
>> When I run the tests it fails with following stack trace
>>
>> ----------------------
>> /opt/manish/kpoint_beaker/spec/spec_helper_acceptance.rb:28:in `<top 
>> (required)>': undefined local variable or method `agent' for main:Object 
>> (NameError)
>>         from 
>> /usr/local/rvm/rubies/ruby-1.9.3-p545/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in
>>  
>> `require'
>>         from 
>> /usr/local/rvm/rubies/ruby-1.9.3-p545/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in
>>  
>> `require'
>>         from 
>> /opt/manish/kpoint_beaker/spec/acceptance/001_basic_spec.rb:1:in `<top 
>> (required)>'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in
>>  
>> `load'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in
>>  
>> `block in load_spec_files'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in
>>  
>> `each'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/configuration.rb:1105:in
>>  
>> `load_spec_files'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:96:in
>>  
>> `setup'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:84:in
>>  
>> `run'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:69:in
>>  
>> `run'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib/rspec/core/runner.rb:37:in
>>  
>> `invoke'
>>         from 
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec:4:in 
>> `<main>'
>> /usr/local/rvm/rubies/ruby-1.9.3-p545/bin/ruby 
>> -I/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-support-3.1.0/lib:/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib
>>  
>> /usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec 
>> spec/acceptance --color failed
>> ----------------------
>>
>> Following is the on call ...
>>
>> on agent, "mkdir -p /tmp/I-am-the-agent"
>>
>>
>> Surprisingly, if I change role to either master/dashboard/database it 
>> runs without
>> any problem.
>>
>> I thought "agent" may be a reserved word, though documentation uses it,
>> I tried with other roles, but that fails too.
>>
>> My environment is
>> ----------------------
>> ruby 1.9.3p545 (2014-02-24 revision 45159) [x86_64-linux] (Running in RVM)
>> beaker (1.19.1)
>> ----------------------
>>
>> Any idea?
>>
>> Thanks and Regards,
>> Manish
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/73d027ea-a459-4d3c-bf78-ddf0b9fe2cbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to