EXIT CODES
       There are several exit codes defined for zypper built-in commands for use e.g. within scripts. These codes are defined in  header  file  src/zypper-main.h
       found  in  zypper  source  package. Codes below 100 denote an error, codes above 100 provide a specific information, 0 represents a normal successful run.
       Following is a list of these codes with descriptions:

       0 - ZYPPER_EXIT_OK
           Successful run of zypper with no special info.

       1 - ZYPPER_EXIT_ERR_BUG
           Unexpected situation occurred, probably caused by a bug.

       2 - ZYPPER_EXIT_ERR_SYNTAX
           zypper was invoked with an invalid command or option, or a bad syntax.

       3 - ZYPPER_EXIT_ERR_INVALID_ARGS
           Some of provided arguments were invalid. E.g. an invalid URI was provided to the addrepo command.

       4 - ZYPPER_EXIT_ERR_ZYPP
           A problem is reported by ZYPP library.

       5 - ZYPPER_EXIT_ERR_PRIVILEGES
           User invoking zypper has insufficient privileges for specified operation.

       6 - ZYPPER_EXIT_NO_REPOS
           No repositories are defined.

       7 - ZYPPER_EXIT_ZYPP_LOCKED
           The ZYPP library is locked, e.g. packagekit is running.

       8 - ZYPPER_EXIT_ERR_COMMIT
           An error occurred during installation or removal of packages. You may run zypper verify to repair any dependency problems.

       100 - ZYPPER_EXIT_INF_UPDATE_NEEDED
           Returned by the patch-check command if there are patches available for installation.

       101 - ZYPPER_EXIT_INF_SEC_UPDATE_NEEDED
           Returned by the patch-check command if there are security patches available for installation.

       102 - ZYPPER_EXIT_INF_REBOOT_NEEDED
           Returned after a successful installation of a patch which requires reboot of computer.

       103 - ZYPPER_EXIT_INF_RESTART_NEEDED
           Returned after a successful installation of a patch which requires restart of the package manager itself.  This  means  that  one  of  patches  to  be
           installed  affects  the  package  manager  itself  and  the command used (e.g. zypper update) needs to be executed once again to install any remaining
           patches.

       104 - ZYPPER_EXIT_INF_CAP_NOT_FOUND
           Returned by the install and the remove command in case any of the arguments does not match any of the available (or installed) package names or  other
           capabilities.

       105 - ZYPPER_EXIT_ON_SIGNAL
           Returned upon exiting after receiving a SIGINT or SIGTERM.

       106 - ZYPPER_EXIT_INF_REPOS_SKIPPED
           Some repository had to be disabled temporarily because it failed to refresh. You should check your repository configuration (e.g. zypper ref -f).

       107 - ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED
           Installation  basically succeeded, but some of the packages %post install scripts returned an error. These packages were successfully unpacked to disk
           and are registered in the rpm database, but due to the failed install script they may not work as expected. The failed  scripts  output  might  reveal
           what actually went wrong. Any scripts output is also logged to /var/log/zypp/history.

       Zypper subcommands (see section SUBCOMMANDS) may return different codes which should be described in the commands man page. Call zypper help subcommand to
       see the subcommands man page if one is provided.