projectatomic / vagrant-service-manager

To provide the user a CLI to configure the ADB/CDK for different use cases and to provide glue between ADB/CDK and the user's developer environment.
GNU General Public License v2.0
18 stars 16 forks source link

Kubernetes acceptance test is failing #374

Closed coolbrg closed 8 years ago

coolbrg commented 8 years ago

It seems that kubernetes acceptance test is failing.

Logs below:

vagrant-service-manager git:(fix-kubernetes-test) ✗ be rake features FEATURE=features/kubernetes.feature
-Using existing ADB box (version 2.2.2) in /home/budhram/redhat/vagrant-service-manager/.boxes
|/home/budhram/.rvm/rubies/ruby-2.1.2/bin/ruby -S bundle exec cucumber features/kubernetes.feature
Using the default and html profiles...
...F-----------<<-STDOUT
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'adb' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'adb' (v0) for provider: virtualbox
    default: Unpacking necessary files from: file:///home/budhram/redhat/vagrant-service-manager/.boxes/adb-virtualbox.box
==> default: Successfully added box 'adb' (v0) for 'virtualbox'!

STDOUT

<<-STDERR
There are errors in the configuration of this machine. Please fix
the following errors and try again:

Vagrant:
* Unknown configuration section 'registration'.

STDERR

<<-STDOUT
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'adb' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'adb' (v0) for provider: virtualbox
    default: Unpacking necessary files from: file:///home/budhram/redhat/vagrant-service-manager/.boxes/adb-virtualbox.box
==> default: Successfully added box 'adb' (v0) for 'virtualbox'!

STDOUT

<<-STDERR
There are errors in the configuration of this machine. Please fix
the following errors and try again:

Vagrant:
* Unknown configuration section 'registration'.

STDERR

---------------

(::) failed steps (::)

expected "bundle exec vagrant up --provider virtualbox" to be successfully executed (RSpec::Expectations::ExpectationNotMetError)
/home/budhram/.rvm/gems/ruby-2.1.2/gems/rspec-support-3.5.0/lib/rspec/support.rb:87:in `block in <module:Support>'
/home/budhram/.rvm/gems/ruby-2.1.2/gems/rspec-support-3.5.0/lib/rspec/support.rb:96:in `call'
/home/budhram/.rvm/gems/ruby-2.1.2/gems/rspec-support-3.5.0/lib/rspec/support.rb:96:in `notify_failure'
/home/budhram/.rvm/gems/ruby-2.1.2/gems/rspec-expectations-3.5.0/lib/rspec/expectations/fail_with.rb:27:in `fail_with'
/home/budhram/.rvm/gems/ruby-2.1.2/gems/rspec-expectations-3.5.0/lib/rspec/expectations/handler.rb:40:in `handle_failure'
........
/home/budhram/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
/home/budhram/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'
features/kubernetes.feature:44:in `When I successfully run `bundle exec vagrant up --provider virtualbox`'
features/kubernetes.feature:26:in `When I successfully run `bundle exec vagrant up --provider <provider>`'

Failing Scenarios:
cucumber -p html features/kubernetes.feature:44 # Scenario Outline: Boot and execute commands, Examples (#1)

2 scenarios (1 failed, 1 skipped)
30 steps (1 failed, 26 skipped, 3 passed)
0m4.643s