This module is a central location for all salt exceptions
Used when an invalid argument was passed to a command execution
If sha256 signature fails during decryption
Thrown when runner or wheel execution fails due to permissions
Used when a check fails
Raised when an error ocurs while getting or setting the windows code page
Used when a module runs a command which returns an error and wants to show the user the output gracefully instead of dying
Used in modules or grains when a required binary is not available
Thrown when eauth authentication fails
Used when an error occurs obtaining a file lock
Used when invalid fileserver settings are detected
Raised when an uncaught error occurs in the midst of obtaining an update/checkout lock in salt.utils.gitfs.
NOTE: While this uses the errno param similar to an OSError, this exception class is not as subclass of OSError. This is done intentionally, so that this exception class can be caught in a try/except without being caught as an OSError.
Used by GitFS to denote a problem with the existence of the "origin" remote or part of its configuration
Used when the config is invalid
Used when an entity fails validation
Raised when we encounter an invalid RSA key.
Problems loading the right renderer
Raised when we encounter an error while logging
Rise when the master exits
Minion problems reading uris such as salt:// or http://
Raised when no smb library is found.
Used when a module runs a command which returns an error and wants to show the user the output gracefully instead of dying
NX-OS Cli Error raised when Cli command rejected by the NX-OS device
NX-OS Client Error raised for problems connecting to the NX-OS device
NX-OS Base Exception class
Raised for unsupported client requests
Used when of the pkg modules cannot correctly parse the output from the CLI tool (pacman, yum, apt, aptitude, etc)
Problems encountered when trying to publish a command
Thrown when a problem was encountered trying to read or write from the salt cache
Problem reading the master root key
Thrown when a job sent through one of the Client interfaces times out
Takes the jid
as a parameter
Raised when a configuration setting is not found and should exist.
Generic Salt Cloud Exception
Raised when too much failures have occurred while querying/waiting for data.
Raised when too much time has passed while querying/waiting for data.
Raised when some cloud provider function cannot find what's being searched.
Raise when virtual terminal password input failed
This exception is raised when the execution should be stopped.
Configuration error
Throw when a running master/minion/syndic is not running but is needed to perform the requested operation (e.g., eauth).
Thrown when salt cannot deserialize data.
Base exception class; all Salt-specific exceptions should subclass this
Pack this exception into a serializable dictionary that is safe for transport via msgpack
Used when the wrong number of arguments are sent to modules or invalid arguments are specified on the command line
Problem reading the master root key
Problem resolving the name of the Salt master
An attempt to retrieve a list of minions failed
Used when a renderer needs to raise an explicit error. If a line number and buffer string are passed, get_context will be invoked to get the location of the error.
Thrown when a salt master request call fails to return within the timeout
Problem in runner
Problem while proxying a request in the syndication master
This exception is raised when an unsolvable problem is found. There's nothing else to do, salt should just exit.
Problem in wheel
Used when a custom error is triggered in a template
Thrown when a timed subprocess does not terminate within the timeout, or if the specified timeout is not an int or a float
Thrown when an opration cannot be completet within a given time limit.
Thrown when token authentication fails
Used when representing a generic VMware API error
Used when the client fails to connect to a either a VMware vCenter server or to a ESXi host
Used when representing a generic VMware error if a file not found
Used when multiple objects were retrieved (and one was expected)
Used when a VMware object was not found
Used when a VMware object already exists
Used when a VMware object was not found
Used when a VMware object cannot be retrieved
Used when error occurred during power on
Used when a runtime error is encountered when communicating with the vCenter
Used when a VMware object cannot be retrieved
Used when representing a generic VMware system error
Used when a configuration parameter is incorrect
Used when a configuration parameter is incorrect
Get human readable message from Python Exception