This repository was archived by the owner on Oct 21, 2022. It is now read-only.
This repository was archived by the owner on Oct 21, 2022. It is now read-only.
Be specific to errors when verify fails due to missing spec directory #22
Description
With no test fixture for my specific suite, verify fails with cryptic message..
$ tree test
test
└── integration
├── default
│ └── serverspec
│ ├── dependencies_spec.rb
│ ├── install_server_spec.rb
│ └── users_spec.rb
└── helpers
└── serverspec
└── spec_helper.rb
11 directories, 11 files
$ kitchen verify default-w-stig-centos-67-vbox-sftp-transport
-----> Starting Kitchen (v1.8.0)
-----> Verifying <default-w-stig-centos-67-vbox-sftp-transport>...
Preparing files for transfer
Transferring files to <default-w-stig-centos-67-vbox-sftp-transport>
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #verify action: [Net::SFTP::StatusException (2, "no such file")]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration
When adding the proper testing directory, works fine..
$ tree test
test
└── integration
├── default
│ └── serverspec
│ ├── dependencies_spec.rb
│ ├── install_server_spec.rb
│ └── users_spec.rb
├── default-w-stig
│ └── serverspec
│ ├── dependencies_spec.rb
│ ├── install_server_spec.rb
│ └── users_spec.rb
└── helpers
└── serverspec
└── spec_helper.rb
$ kitchen verify default-w-stig-centos-67-vbox-sftp-transport
-----> Starting Kitchen (v1.8.0)
-----> Verifying <default-w-stig-centos-67-vbox-sftp-transport>...
Preparing files for transfer
-----> Installing Busser (busser)
Fetching: thor-0.19.0.gem (100%)
Successfully installed thor-0.19.0
Fetching: busser-0.7.1.gem (100%)
Successfully installed busser-0.7.1
2 gems installed
Installing Busser plugins: busser-serverspec
Plugin serverspec installed (version 0.5.9)
-----> Running postinstall for serverspec plugin
[...]
The error indication does not provide the information needed to fix the issue. Not sure if this is the responsibility of this plugin or not.