diff options
| author | Lamont Granquist <lamont@scriptkiddie.org> | 2019-07-24 18:36:24 -0700 |
|---|---|---|
| committer | Lamont Granquist <lamont@scriptkiddie.org> | 2019-07-24 18:36:24 -0700 |
| commit | 22fd71c2f9590967ac9d0d1e99fe1ac76b73f392 (patch) | |
| tree | 1b25de664ebf6a32a194c6c08dead20d138f4c1c | |
| parent | 81f8d729edcd5237aaad19c351dae46fd8e7c0d6 (diff) | |
| download | chef-22fd71c2f9590967ac9d0d1e99fe1ac76b73f392.tar.gz | |
drop the info message down to debug
a 404 is probably unlikely in any circumstance other than when the user
really does not intend to use the data collector at all (hosted,
automate 1, older chef servers, etc).
i don't know how you'd get into a situation where the user wanted to
setup the data collector against an automate 2 server, but the
data collector endpoint didn't exist -- presumably because they
accidentally pointed it at a valid old chef server accidentally, which
is going to be an incredibly infrequent edge condition.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
| -rw-r--r-- | lib/chef/data_collector.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/chef/data_collector.rb b/lib/chef/data_collector.rb index 47d329b2b6..931671bf50 100644 --- a/lib/chef/data_collector.rb +++ b/lib/chef/data_collector.rb @@ -198,7 +198,7 @@ class Chef if code == "404" # Make the message non-scary for folks who don't have automate: msg << " (This is normal if you do not have #{Chef::Dist::AUTOMATE})" - Chef::Log.info(msg) + Chef::Log.debug(msg) else Chef::Log.warn(msg) end |