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

Minitest to serverspec #106

Closed
wants to merge 2 commits into from
Closed

Minitest to serverspec #106

wants to merge 2 commits into from

Conversation

someara
Copy link

@someara someara commented Apr 12, 2015

No description provided.

Sean OMeara added 2 commits April 11, 2015 22:54
…ser.

- Makes it easier to tell if resources update on 2nd and 3rd runs
- Integration tests not run in context of initial converge
- Utilize test-kitchen bussers

Current status:
- `kitchen test -c` completes across Digital Ocean and AWS in

- Platforms that do not pass are commented out of the .kitchen.cloud.yml
- centos-7 - Sticks on plain-defaults, looping forever waiting for /etc/service/plain-defaults/supervise
- debian-7 - Explodes attempting to start the first service
- fedora-21 - Converges, but serverspec service resource gets confused, because systemd.
@someara someara mentioned this pull request Apr 12, 2015
@luckymike
Copy link
Contributor

Please see my comment on #95. At this time this needs a Gemfile update as well, to support non-DK users. However, a much, much better solution would be patching kitchen so that it looks for all dep-solvers. That way you can include a berksfile, and it will just work if you have DK, or you can use bundler for something else, and it will also just work.

I've discussed this with @fnichol multiple times. Perhaps some additional internal encouragement will help :)

@luckymike
Copy link
Contributor

michael@luckymike ~/Development/hw/cookbooks/runit (someara-minitest_to_serverspec) $ be kitchen test service-ubuntu-1204
-----> Starting Kitchen (v1.3.1)
-----> Cleaning up any prior instances of <service-ubuntu-1204>
-----> Destroying <service-ubuntu-1204>...
       Finished destroying <service-ubuntu-1204> (0m0.00s).
-----> Testing <service-ubuntu-1204>
-----> Creating <service-ubuntu-1204>...
       Bringing machine 'default' up with 'virtualbox' provider...
       ==> default: Importing base box 'opscode-ubuntu-12.04'...
==> default: Matching MAC address for NAT networking...
       ==> default: Setting the name of the VM: kitchen-runit-service-ubuntu-1204_default_1428943529023_43942
       ==> default: Clearing any previously set network interfaces...
       ==> default: Preparing network interfaces based on configuration...
           default: Adapter 1: nat
       ==> default: Forwarding ports...
           default: 22 => 2222 (adapter 1)
       ==> default: Booting VM...
       ==> default: Waiting for machine to boot. This may take a few minutes...    default: SSH address: 127.0.0.1:2222
           default: SSH username: vagrant
           default: SSH auth method: private key    default: Warning: Connection timeout. Retrying...
       ==> default: Machine booted and ready!
       ==> default: Checking for guest additions in VM...
       ==> default: Setting hostname...
       ==> default: Machine not provisioning because `--no-provision` is specified.
       Vagrant instance <service-ubuntu-1204> created.
       Finished creating <service-ubuntu-1204> (0m35.81s).
-----> Converging <service-ubuntu-1204>...
       Preparing files for transfer
       Preparing dna.json
       Resolving cookbook dependencies with Berkshelf 2.0.18...
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #converge action: [Berkshelf::BerksfileReadError]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

@luckymike
Copy link
Contributor

I just realized that's a different issue and that Berks is in the Gemfile...

@luckymike
Copy link
Contributor

Realizing now that an older Berks version is pinned in the Gemfile, it seems reasonable to update that to ~> 3.0 and accept this, though if Berks users aren't typically going to use bundler, it would be nice to resolve the above issues. I've tracked that here, since there didn't appear to be an actual open issue: test-kitchen/test-kitchen#686

@someara someara closed this Apr 14, 2015
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 this pull request may close these issues.

2 participants