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

First attempt at trying to fix issue 2476 #4099

Merged
merged 1 commit into from
Aug 6, 2014

Conversation

sneal
Copy link
Contributor

@sneal sneal commented Jun 24, 2014

One possible solution to #2476, although likely incomplete.

This addresses the error "chef is not part of the bundle" when the chef-client provisioner attempts to delete the node or client from the Chef Server. While this fixes the specific issue on my system, its likely that it does not account for all system configurations like RVM.

The Bundler.with_clean_env should probably be moved internally to Subprocess.execute, but that's a riskier change and I'd like to get some feedback before even attempting that size of change.

This addresses the error "chef is not part of the bundle" when the chef-client provisioner attempts to delete the node or client from the Chef Server. While this fixes the specific issue on my system, its likely that it does not account for all system configurations like RVM.

The Bundler.with_clean_env should probably be moved internally to Subprocess.execute, but that's a riskier change and I'd like to get some feedback before even attempting that size of change.
@sl
Copy link

sl commented Jun 26, 2014

Great to see a possible real fix for this! Good work!

@FractalizeR
Copy link

Any updates? :)

@mitchellh
Copy link
Contributor

I think this can't hurt, and looks like a good fix.

mitchellh added a commit that referenced this pull request Aug 6, 2014
…de-cleanup

provisioners/chef: clean bundle env when executing chef client
@mitchellh mitchellh merged commit 22395e5 into master Aug 6, 2014
@mitchellh mitchellh deleted the fix-issue-2476-chef-client-node-cleanup branch August 6, 2014 17:13
@mitchellh
Copy link
Contributor

I think we should add a big lock around this.

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants