-
Notifications
You must be signed in to change notification settings - Fork 21
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
Can no longer install 12.4.1 client on Linux via ChefVMExtension #75
Comments
Hello @stuartpreston, it's an expected behavior that old extensions will be deleted as there is a limit on the number of published extensions. This is specified the Readme too at the end. However this time we had to delete a latest extension as it wasn't working fine (please refer #70 (comment)). |
Hi @NimishaS, thanks for this effort! |
@rarsan , we are working on decoupling extension version and |
👍👍 |
Extension 1210.12.100 has been published and it allows user to specify |
@NimishaS This failed for me using ARM with Ubuntu 14.04-LTS.3 image in the West Europe region, at which point the installer remains in the "installing" state (30 minutes so far and no timeout).
|
A little bit more information here. It would appear to be falling through to the place where a specific version gets installed, specifically https://github.com/chef-partners/azure-chef-extension/blob/master/ChefExtensionHandler/bin/chef-install.sh#L185-L189 But if I try all permutations manually, I do get the correct result (resolution of the correct version). Even if the version number didn't make it, we would still get the latest version for install.
I am assuming it is taking this path, based on the version being set. When I do not send bootstrap_version at all, the chef-install.sh correctly installs the latest installer. I checked that installing 12.3.0 manually via apt-get after a failed install via the extension works:
A bit hard to diagnose from here. |
@stuartpreston , can you please verify with the latest version of linux extension |
This should no longer be an issue since we're not longer relying on apt repos and using omnitruck instead. |
It appears that 1210.12.4.1000 LinuxChefClient was yanked and replaced with .2000 - is it to be expected that minor versions can get bumped without notice?
Scenario: I'm rebuilding my environment in an ARM template using '1210.12' as my version but get a different version of the client to the environment I created using the identical template two weeks ago. Therefore my environment is inconsistent with the testing I did two weeks ago on apparently the same version.
Also can we expect a 12.4.3 for (Windows) ChefClient soon?
thanks!
The text was updated successfully, but these errors were encountered: