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

no port found in cookbook url - can't download cookbooks unless listening on port 80 #5

Closed
reset opened this issue May 4, 2013 · 5 comments

Comments

@reset
Copy link
Contributor

reset commented May 4, 2013

After uploading a cookbook to the ChefZero server the URL of each cookbook file does not contain the port of the running ChefZero server.

This means that when you attempt to download the cookbook, unless you started ChefZero on port 80, you'll receive a connection error.

Here's the "resources" collection of a cookbook in the ChefZero server:

{:resources=>[#<Hashie::Mash checksum="b70ba735f3af47e5d6fc71b91775b34c" name="defresource.rb" path="resources/defresource.rb" specificity="default" url="http://localhost/file_store/b70ba735f3af47e5d6fc71b91775b34c">]

You'll notice that the url is http://localhost/file_store/b70ba735f3af47e5d6fc71b91775b34c but the ChefZero server is actually running on 8889

@jkeiser
Copy link
Contributor

jkeiser commented May 6, 2013

That's weird, what version of chef are you running? This isn't happening for me (I can download cookbooks).

@reset
Copy link
Contributor Author

reset commented May 6, 2013

0.9.7. This is the test case which I was exercising when I hit it: https://github.com/RiotGames/ridley/blob/master/spec/unit/ridley/resources/cookbook_resource_spec.rb#L15-L19

@reset
Copy link
Contributor Author

reset commented May 6, 2013

@jkeiser it might be worth noting that the URL comes back without a port on my end. This doesn't you can't download them, it just means that if you don't inject the port into the URL coming back from the sandbox that you wont' be able to download it

@sethvargo
Copy link
Contributor

@jkeiser confirming this

@jkeiser
Copy link
Contributor

jkeiser commented May 16, 2013

After much fun, we figured out Ridley was sending the wrong port: berkshelf/ridley#139

Thanks @sethvargo for helping find the issue and @reset for fixing it :)

@jkeiser jkeiser closed this as completed May 16, 2013
@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants