Currently, Ohai attributes are retrieved directly from stdout. Depending on the configuration of Ohai, this may result in unrelated Ohai warnings being included when Sal attempts to parse the json.
For example, if the Ohai configuration includes ohai.log_location STDOUT Ohai's output may include something like [2019-03-22T10:56:06-07:00] WARN: Plugin Network: [inet] no ip address on utun4. When Sal attempts to parse this, it will throw an exception on the - character, which causes all of the Ohai data to be skipped.
Potentially, Sal could override the log level by passing something like -l fatal, but it might be best to leave this decision up to the admin and include a note in the wiki.
Currently, Ohai attributes are retrieved directly from stdout. Depending on the configuration of Ohai, this may result in unrelated Ohai warnings being included when Sal attempts to parse the json.
For example, if the Ohai configuration includes
ohai.log_location STDOUT
Ohai's output may include something like[2019-03-22T10:56:06-07:00] WARN: Plugin Network: [inet] no ip address on utun4
. When Sal attempts to parse this, it will throw an exception on the-
character, which causes all of the Ohai data to be skipped.Potentially, Sal could override the log level by passing something like
-l fatal
, but it might be best to leave this decision up to the admin and include a note in the wiki.