Skip to content
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

dokken provisioner is based on chef_zero and is expecting to load the chef_zero file, which has been renamed to chef_infra in test-kitchen #226

Open
i5pranay93 opened this issue Mar 24, 2021 · 0 comments

Comments

@i5pranay93
Copy link

👻 Brief Description

The feature change in test-kitchen repo which, needed rename of chef-zero provisioner to chef-infra has led to failing of integration test in test-kitchen.

Version

Test Kitchen version: 2.10.

Environment

Linux with ruby 2.5
Linux with ruby 2.6
Linux with ruby 2.7

Scenario

Integration Test of test-kitchen in the azure pipeline

Steps to Reproduce

Pushing code will automatically run this test in the test-kitchen repo.

Expected Result

Integration Tests should pass

Actual Result

-----> Starting Test Kitchen (v2.11.1)
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ClientError
>>>>>> Message: Could not load the 'dokken' provisioner from the load path.cannot load such file -- kitchen/provisioner/chef_zero
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

➕ Additional context

Issue- test-kitchen/test-kitchen#1708
PR- test-kitchen/test-kitchen#1730

@i5pranay93 i5pranay93 changed the title dokken provisioner is based on chef_zero and is expecting to load the chef_zero file, which has been renamed to chef_infra dokken provisioner is based on chef_zero and is expecting to load the chef_zero file, which has been renamed to chef_infra in test-kitchen Mar 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant