Don't trace on IOErrors

[s0undt3ch]

Refs #11783, #11853

[s0undt3ch]

Need to bring @basepi and @rallytime into the conversation.

[s0undt3ch]

The reason why I'm not exiting like @basepi suggests on #11783 is because, as you might see on the logs, if the configuration file is not found or readable, the configuration defaults is what's used. This has been the default behaviour thus far.

If we need to exit on unreadable configuration files, which might be an unexpected "bahaviour" change(from the user's perspective), then we should probably ask @thatch45 about this, and, as I talked about in #11852, that should be done in parsers, and would be done way sooner than that stack trace.

Thoughts?

[ghost]

Test Failed.

If the failures are unrelated to your code, don't stress, a core developer will know these apart.
In the future, if possible, please branch off a passing commit to avoid false positives.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/3226/

[ghost]

Test PASSed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/3227/

[rallytime]

@s0undt3ch - This solution looks much simpler! Looks good to me unless @thatch45 has any concerns.

[thatch45]

Thanks @s0undt3ch , this looks awesome!

[s0undt3ch]

Anytime!