Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

chef-provisioning fails, bad chef_server_url, should be updated to latest 'master' branch #297

Closed
Cytrian opened this issue Jan 21, 2015 · 4 comments
Labels

Comments

@Cytrian
Copy link

Cytrian commented Jan 21, 2015

As soon as I started creating a vagrant-lxc-box with newest chefdk-0.3.6, convergence failed,
because the ssh-forwarded chef-zero-server wasn't reachable. It chef_server_url
was like 'http::8889' (not 'http://localhost:8889').

This has been fixed in the latest master of the chef-provisioning gem. Please update immediately!

@afiune
Copy link
Contributor

afiune commented Jan 27, 2015

@Cytrian Quick fix to let you continue with your development is to downgrade ChefDK to version 0.3.5

@irvingpop
Copy link

Yep, this is an issue caused by net-ssh 2.9.2 that has been biting everyone who uses chef-provisioning. Has anyone tried to address this with the net-ssh maintainers?

@esciara
Copy link

esciara commented Jan 30, 2015

@danielsdeleo
Copy link
Contributor

I think this was fixed in ChefDK 0.4.0, so I'm going to close this but please let me know if I'm wrong and I'll reopen.

@thommay thommay added Type: Bug Doesn't work as expected. and removed Bug labels Feb 1, 2017
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

6 participants