New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert kitchen-vagrant to v0.21.1 #78

Merged
merged 1 commit into from Feb 13, 2017

Conversation

Projects
None yet
1 participant
@4-20ma
Owner

4-20ma commented Feb 13, 2017

  • reverting version resolves following error:

    -----> Starting Kitchen (v1.15.0)

    ------Exception-------
    Class: Kitchen::ClientError
    Message: Could not load the 'vagrant' driver from the load path.
    Please ensure that your driver is installed as a gem or
    included in your Gemfile if using Bundler.

    Please see .kitchen/logs/kitchen.log for more details
    Also try running kitchen diagnose --all for configuration

Revert kitchen-vagrant to 0.21.1
- reverting version resolves following error:

  -----> Starting Kitchen (v1.15.0)
  >>>>>> ------Exception-------
  >>>>>> Class: Kitchen::ClientError
  >>>>>> Message: Could not load the 'vagrant' driver from the load path.
                  Please ensure that your driver is installed as a gem or
                  included in your Gemfile if using Bundler.
  >>>>>> ----------------------
  >>>>>> Please see .kitchen/logs/kitchen.log for more details
  >>>>>> Also try running `kitchen diagnose --all` for configuration

@4-20ma 4-20ma self-assigned this Feb 13, 2017

@4-20ma 4-20ma merged commit af88bef into master Feb 13, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@4-20ma 4-20ma deleted the revert-kitchen-vagrant-0211 branch Feb 13, 2017

@4-20ma 4-20ma added the Type: Bug label Feb 19, 2017

@4-20ma 4-20ma changed the title from Revert kitchen-vagrant to 0.21.1 to Revert kitchen-vagrant to v0.21.1 Feb 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment