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

After enabling the New Relic add-on and running chef it remains in a crashed state #345

Open
radamanthus opened this issue Apr 20, 2018 · 0 comments

Comments

@radamanthus
Copy link
Contributor

Steps to replicate:

  • Create a new environment
  • Add the New Relic Infrastructure recipe to the environment recipes
  • Do not enable the New Relic add-on for the environment
  • Boot the environment

Result:
New Relic will be installed, but will be in a crashed state

Even after enabling the add-on for the environment, New Relic remains in a crashed state

I'm opening this issue to start the discussion on this.

Should the New Relic Infrastructure recipe include a restart of New Relic? This will solve the issue, but the downside is that there will be the New Relic restart that is unnecessary for 99.99% of chef runs.

Should there be a restart_newrelic_flag? It will introduce complexity to the recipe.

Should we just document this in the recipe README?

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

No branches or pull requests

1 participant