You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zmaupin@automate-fe-02:/tmp/do_terraform$ which chef-automate
/bin/chef-automate
zmaupin@automate-fe-02:/tmp/do_terraform$ /usr/bin/chef-automate
-bash: /usr/bin/chef-automate: No such file or directory
The text was updated successfully, but these errors were encountered:
Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.
If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.
Cookbook version
3.1.2
Chef-client version
15.1.36
Platform Details
VM running Ubuntu Bionic
Scenario:
Using custom config with the
chef_automatev2
resource.Steps to Reproduce:
Use the
chef_automatev2
resource with custom config.Expected Result:
An execute resource is ran to patch the automate config.
Actual Result:
The execute resource is never ran because
/usr/bin/chef-automate
does not exist. The path is/bin/chef-automate
.The text was updated successfully, but these errors were encountered: