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

Chef installation doesn't work if an x.y.z version is specified #32

Closed
4min opened this issue Aug 13, 2015 · 2 comments
Closed

Chef installation doesn't work if an x.y.z version is specified #32

4min opened this issue Aug 13, 2015 · 2 comments

Comments

@4min
Copy link

4min commented Aug 13, 2015

Chef 11.18.10+ installation doesn't work if version is specified. Apparently Chef has changed URLs for MSIs to this format:
https://opscode-omnibus-packages.s3.amazonaws.com/windows/2008r2/x86_64/chef-client-11.18.10-1.msi
That happened during the release of 11.18.10

This can't be fixed by passing a custom URL variable via Makefile.local either, because only "CM" and "CM_VERSION" get passed through to the VM.

Overall, for all versions: CM_VERSION syntax does not match the one described in readme:

  • The value of CM_VERSION should have the form x.y or x.y.z, such as CM_VERSION := 11.12.4

In fact the only value that would work right now would be "11.12.4-1". We can safely add "-1" to simplify interface, for all the released versions of Chef-client with the following exceptions:

@4min
Copy link
Author

4min commented Aug 13, 2015

Submitted a pull request with fix ^^

@annawake
Copy link
Contributor

Rather than hardcoding the versions, try getting a result from the omnitruck API: https://docs.chef.io/api_omnitruck.html

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.

3 participants