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

notifies from within rvm_shell doesn't trigger #68

cswilliams opened this issue Jan 26, 2012 · 3 comments

notifies from within rvm_shell doesn't trigger #68

cswilliams opened this issue Jan 26, 2012 · 3 comments


Copy link

@cswilliams cswilliams commented Jan 26, 2012

I am trying to use notifies from within rvm_shell but having trouble.

For example:

ruby_block "a block" do
block do"my block ran")

action :nothing


rvm_shell "a command" do
code "echo foobar"
notifies :create, "ruby_block[a block]", :immediately

results in the output:
[Thu, 26 Jan 2012 00:49:14 -0800] INFO: Starting Chef Run (Version 0.9.12)
[Thu, 26 Jan 2012 00:50:07 -0800] INFO: Ran script[a command] successfully
[Thu, 26 Jan 2012 00:50:08 -0800] INFO: Chef Run complete in 14.732362 seconds
[Thu, 26 Jan 2012 00:50:08 -0800] INFO: cleaning the checksum cache
[Thu, 26 Jan 2012 00:50:09 -0800] INFO: Running report handlers
[Thu, 26 Jan 2012 00:50:09 -0800] INFO: Report handlers complete

Copy link

@fnichol fnichol commented Mar 12, 2012

Looks like I've neglected to set new_resource.updated_by_last_action(true) in all the LWRPs. I'll need to fix each of these which should solve the resource notifications. Thank you Foodcritic

Copy link

@damacus damacus commented May 31, 2019

Closing due to inactivity.

If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!


@damacus damacus closed this May 31, 2019
Copy link

@lock lock bot commented Jun 24, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants