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-Ingredient 2.0.1 failing to downgrade Chef-Client when newer version is installed #145

Open
FilBot3 opened this issue Apr 6, 2017 · 3 comments
Assignees
Labels
Type: Bug Does not work as expected.

Comments

@FilBot3
Copy link

FilBot3 commented Apr 6, 2017

Cookbook version

2.0.1

Chef-client version

12.19.36 attempting to downgrade to 12.13.37

Platform Details

CentOS 7.2, Vagrant Bento Box

Scenario:

Attempting to test chef_ingredient install for Chef-HA, and downgrading the Agent on Vagrant test machine to match current production.

Steps to Reproduce:

Include the desired version of Chef-Client in the version attribute for chef_ingredient. Run chef exec kitchen test

Expected Result:

successful converge

Actual Result:

https://gist.github.com/predatorian3/acb12c35ccb6b79f762830a60082dc53

@FilBot3
Copy link
Author

FilBot3 commented Apr 6, 2017

I figured I would run the downgrade again because when using the omnibus cookbook, you have to run it twice when upgrading or downgrading chef-client to force the correct version usage.

@wrightp wrightp self-assigned this Apr 6, 2017
@wrightp wrightp added the Type: Bug Does not work as expected. label Apr 17, 2017
@wrightp
Copy link

wrightp commented Apr 17, 2017

@predatorian3 Thanks for reporting this issue. I'm labeling this as a bug. I'm not certain if this will pertain to your use case, but have you checked out https://github.com/chef-cookbooks/chef_client_updater?

@FilBot3
Copy link
Author

FilBot3 commented May 10, 2017

I have heard of that recently. Thank you for the link!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Does not work as expected.
Projects
None yet
Development

No branches or pull requests

4 participants