From 0422211faa0a76c423ec52142caa3f3fe185b89c Mon Sep 17 00:00:00 2001 From: Thomas H Jones II Date: Thu, 22 Jun 2023 12:55:37 -0400 Subject: [PATCH] Update docs/troubleshooting/Linux/salt_call.debug.log.md Co-authored-by: Loren Gordon --- docs/troubleshooting/Linux/salt_call.debug.log.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting/Linux/salt_call.debug.log.md b/docs/troubleshooting/Linux/salt_call.debug.log.md index 4e25f436a..815a77faf 100644 --- a/docs/troubleshooting/Linux/salt_call.debug.log.md +++ b/docs/troubleshooting/Linux/salt_call.debug.log.md @@ -66,7 +66,7 @@ The most frequent causes of errors, once `watchmaker` has caused `Saltstack` sta The next most frequent errors are already-existing configuration problems in the OS that `watchmaker` is configuring. These include things like: - Failures accessing RPM repositories (especially problematic with repositories that require client-cert authentication where there are certificate-expiration problems between the RPM client and repository server) - Too little storage in critical partitions -- The `watchmaker` activities running after something else has changed a resource-configuration that `watchmaker` expects to managed but finds the resource in an unanticipated state +- The `watchmaker` activities running after something else has changed a resource-configuration that `watchmaker` expects to manage but finds the resource in an unanticipated state The least frequent cause of errors is related to the SaltStack code itself. Usually, this is caught in pre-release testing, but "bugs happen". While states are typically coded to try to gracefully handle errors encountered – they'll typically still fail, but at least try to provide meaningful error-output. Usually, the "bugs happen" errors are resultant of environment-to-environment deltas that were not adequately specified to the code-maintainers or the requisite logic-branching was not able to be adequately exercised across the various environments.