Unable to unpack tomcat tar

[CalgarySaltUser]

Hi,

I'm trying to unpack tomcat into the /opt/ directory but am getting an error. My SLS looks like this:

tomcat:

  archive:

    - extracted

    - name: /opt/

    - source: salt://apache-tomcat-8.0.20.tar.gz

    - source_hash: md5=9a3dacfbe9644d7a23699b4aa9f648df

    - archive_format: tar

    - tar_options: z

    - if_missing: /opt/apache-tomcat-8.0.20

And here is the output when I run highstate:

minion1:

----------

          ID: tomcat

    Function: archive.extracted

        Name: /opt/

      Result: False

     Comment:

     Started: 03:06:39.575338

    Duration: 36.036 ms

     Changes:

              ----------

              pid:

                  28066

              retcode:

                  2

              stderr:

                  tar (child): '/var/cache/salt/minion/files/base/_opt_apache-tomcat-8.0.20.tar': Cannot open: No such file or directory

                  tar (child): Error is not recoverable: exiting now

                  tar: Child returned status 2

                  tar: Error is not recoverable: exiting now

              stdout:

Summary

------------

Succeeded: 0 (changed=1)

Failed:    1

------------

Total states run:     1

I've confirmed that apache-tomcat-8.0.20.tar.gz does exist in my /srv/salt directory and that it is being copied over to minion1. The exact file and directory that Salt is complaining about on the minion ('/var/cache/salt/minion/files/base/_opt_apache-tomcat-8.0.20.tar') do indeed exist. Any help would be greatly appreciated!

[jack cam]

Hi Calgary,

Did you verify that tar file is located somewhere where Salt can access(file_roots: base : .... for example) ?

Example master configuration

file_roots:

  base: 

    - /salt/binaries

apache-tomcat-8.0.20.tar.gz must be located in /salt/binaries

You can try to stop minion and delete files and directory in /var/cache/salt/minion/*

Enjoy.

[CalgarySaltUser]

Hey Jack, thanks for the reply. The tar file is in /srv/salt which is where my SLS files are. Since this tar is being copied over to the mionion, I do know that Salt has access to it. The permissions on the tar are chmod 777 as well. Check out the string of commands I ran below. I stopped the minion, cleared cache on the minion, started the minion, then ran highstate again.

[root@osboxes salt]#

[root@osboxes salt]# rm -fr /var/cache/salt/minion/

[root@osboxes salt]# ls /var/cache/salt/minion/

ls: cannot access /var/cache/salt/minion/: No such file or directory

[root@osboxes salt]# ls /var/cache/salt/

master

[root@osboxes salt]# pwd

/srv/salt

[root@osboxes salt]# ls

apache-tomcat-8.0.20.tar.gz  test2.sls  tomcat.sls

custom-tomcat.sls            test.sls   top.sls

[root@osboxes salt]# cat top.sls

base:

  '*':

    - tomcat

[root@osboxes salt]# cat tomcat.sls

tomcat:

  archive:

    - extracted

    - name: /opt/

    - source: salt://apache-tomcat-8.0.20.tar.gz

    - source_hash: md5=9a3dacfbe9644d7a23699b4aa9f648df

    - archive_format: tar

    - tar_options: z

    - if_missing: /opt/apache-tomcat-8.0.20

[root@osboxes salt]#

[root@osboxes salt]# salt '*' state.highstate

minionErkan:

----------

          ID: tomcat

    Function: archive.extracted

        Name: /opt/

      Result: False

     Comment:

     Started: 12:28:56.471722

    Duration: 8523.363 ms

     Changes:

              ----------

              pid:

                  29573

              retcode:

                  2

              stderr:

                  tar (child): '/var/cache/salt/minion/files/base/_opt_apache-tomca                                                                                            t-8.0.20.tar': Cannot open: No such file or directory

                  tar (child): Error is not recoverable: exiting now

                  tar: Child returned status 2

                  tar: Error is not recoverable: exiting now

              stdout:

Summary

------------

Succeeded: 0 (changed=1)

Failed:    1

------------

Total states run:     1

[root@osboxes salt]# ls /var/cache/salt/minion/files/base/

apache-tomcat-8.0.20.tar.gz  _opt_apache-tomcat-8.0.20.tar  tomcat.sls  top.sls

[root@osboxes salt]# ls -la /var/cache/salt/minion/files/base/

total 18136

drwx------. 2 root root    4096 Mar 26 12:29 .

drwx------. 3 root root    4096 Mar 26 12:28 ..

-rw-------. 1 root root 9276758 Mar 26 12:29 apache-tomcat-8.0.20.tar.gz

-rw-r--r--. 1 root root 9276758 Mar 26 12:29 _opt_apache-tomcat-8.0.20.tar

-rw-------. 1 root root     249 Mar 26 12:28 tomcat.sls

-rw-------. 1 root root      26 Mar 26 12:28 top.sls

[root@osboxes salt]#

[jack cam]

Which salt version do you use if you use salt version >= 2014.7.2

Use this option tar_options: xz instead of tar_options: z.

If this change doesn't work please provide your master configuration

[CalgarySaltUser]

Hey Jack,

I'm using version 2014.7.1. I tried tar_options: xz but Ièm getting the same error. Please see my session below. Ive also included my master config.

[root@osboxes salt]#

[root@osboxes salt]# salt --version

salt 2014.7.1 (Helium)

[root@osboxes salt]# cat tomcat.sls

tomcat:

  archive:

    - extracted

    - name: /opt/

    - source: salt://apache-tomcat-8.0.20.tar.gz

    - source_hash: md5=9a3dacfbe9644d7a23699b4aa9f648df

    - archive_format: tar

    - tar_options: xz

    - if_missing: /opt/apache-tomcat-8.0.20

[root@osboxes salt]#

[root@osboxes salt]# salt '*' state.highstate

minionErkan:

----------

          ID: tomcat

    Function: archive.extracted

        Name: /opt/

      Result: False

     Comment:

     Started: 23:01:32.152097

    Duration: 32.51 ms

     Changes:

              ----------

              pid:

                  30253

              retcode:

                  2

              stderr:

                  tar (child): '/var/cache/salt/minion/files/base/_opt_apache-tomcat-8.0.20.tar': Cannot open: No such file or directory

                  tar (child): Error is not recoverable: exiting now

                  tar: Child returned status 2

                  tar: Error is not recoverable: exiting now

              stdout:

Summary

------------

Succeeded: 0 (changed=1)

Failed:    1

------------

Total states run:     1

[root@osboxes salt]#

[root@osboxes salt]#

[root@osboxes salt]#

[root@osboxes salt]# cat /etc/s

salt/               scl/                sestatus.conf       shadow              sos.conf            sssd/               sudoers             sysctl.d/

samba/              security/           setroubleshoot/     shadow-             speech-dispatcher/  statetab            sudoers.d/          systemd/

sane.d/             selinux/            setuptool.d/        shells              ssh/                statetab.d/         sysconfig/          system-release

sasl2/              services            sgml/               skel/               ssl/                stunnel/            sysctl.conf         system-release-cpe

[root@osboxes salt]# cat /etc/salt/master

##### Primary configuration settings #####

##########################################

# This configuration file is used to manage the behavior of the Salt Master.

# Values that are commented out but have no space after the comment are

# defaults that need not be set in the config. If there is a space after the

# comment that the value is presented as an example and is not the default.

# Per default, the master will automatically include all config files

# from master.d/*.conf (master.d is a directory in the same directory

# as the main master config file).

#default_include: master.d/*.conf

# The address of the interface to bind to:

#interface: 0.0.0.0

# Whether the master should listen for IPv6 connections. If this is set to True,

# the interface option must be adjusted, too. (For example: "interface: '::'")

#ipv6: False

# The tcp port used by the publisher:

#publish_port: 4505

# The user under which the salt master will run. Salt will update all

# permissions to allow the specified user to run the master. The exception is

# the job cache, which must be deleted if this user is changed. If the

# modified files cause conflicts, set verify_env to False.

#user: root

# Max open files

#

# Each minion connecting to the master uses AT LEAST one file descriptor, the

# master subscription connection. If enough minions connect you might start

# seeing on the console (and then salt-master crashes):

#   Too many open files (tcp_listener.cpp:335)

#   Aborted (core dumped)

#

# By default this value will be the one of `ulimit -Hn`, ie, the hard limit for

# max open files.

#

# If you wish to set a different value than the default one, uncomment and

# configure this setting. Remember that this value CANNOT be higher than the

# hard limit. Raising the hard limit depends on your OS and/or distribution,

# a good way to find the limit is to search the internet. For example:

#   raise max open files hard limit debian

#

#max_open_files: 100000

# The number of worker threads to start. These threads are used to manage

# return calls made from minions to the master. If the master seems to be

# running slowly, increase the number of threads.

#worker_threads: 5

# The port used by the communication interface. The ret (return) port is the

# interface used for the file server, authentication, job returns, etc.

#ret_port: 4506

# Specify the location of the daemon process ID file:

#pidfile: /var/run/salt-master.pid

# The root directory prepended to these options: pki_dir, cachedir,

# sock_dir, log_file, autosign_file, autoreject_file, extension_modules,

# key_logfile, pidfile:

#root_dir: /

# Directory used to store public key data:

#pki_dir: /etc/salt/pki/master

# Directory to store job and cache data:

#cachedir: /var/cache/salt/master

# Directory for custom modules. This directory can contain subdirectories for

# each of Salt's module types such as "runners", "output", "wheel", "modules",

# "states", "returners", etc.

#extension_modules: <no default>

# Verify and set permissions on configuration directories at startup:

#verify_env: True

# Set the number of hours to keep old job information in the job cache:

#keep_jobs: 24

# Set the default timeout for the salt command and api. The default is 5

# seconds.

#timeout: 5

# The loop_interval option controls the seconds for the master's maintenance

# process check cycle. This process updates file server backends, cleans the

# job cache and executes the scheduler.

#loop_interval: 60

# Set the default outputter used by the salt command. The default is "nested".

#output: nested

# By default, output is colored. To disable colored output, set the color value

# to False.

#color: True

# Do not strip off the colored output from nested results and state outputs

# (true by default).

# strip_colors: False

# Set the directory used to hold unix sockets:

#sock_dir: /var/run/salt/master

# The master can take a while to start up when lspci and/or dmidecode is used

# to populate the grains for the master. Enable if you want to see GPU hardware

# data for your master.

# enable_gpu_grains: False

# The master maintains a job cache. While this is a great addition, it can be

# a burden on the master for larger deployments (over 5000 minions).

# Disabling the job cache will make previously executed jobs unavailable to

# the jobs system and is not generally recommended.

#job_cache: True

# Cache minion grains and pillar data in the cachedir.

#minion_data_cache: True

# Passing very large events can cause the minion to consume large amounts of

# memory. This value tunes the maximum size of a message allowed onto the

# master event bus. The value is expressed in bytes.

#max_event_size: 1048576

# By default, the master AES key rotates every 24 hours. The next command

# following a key rotation will trigger a key refresh from the minion which may

# result in minions which do not respond to the first command after a key refresh.

#

# To tell the master to ping all minions immediately after an AES key refresh, set

# ping_on_rotate to True. This should mitigate the issue where a minion does not

# appear to initially respond after a key is rotated.

#

# Note that ping_on_rotate may cause high load on the master immediately after

# the key rotation event as minions reconnect. Consider this carefully if this

# salt master is managing a large number of minions.

#

# If disabled, it is recommended to handle this event by listening for the

# 'aes_key_rotate' event with the 'key' tag and acting appropriately.

# ping_on_rotate: False

# By default, the master deletes its cache of minion data when the key for that

# minion is removed. To preserve the cache after key deletion, set

# 'preserve_minion_cache' to True.

#

# WARNING: This may have security implications if compromised minions auth with

# a previous deleted minion ID.

#preserve_minion_cache: False

# If max_minions is used in large installations, the master might experience

# high-load situations because of having to check the number of connected

# minions for every authentication. This cache provides the minion-ids of

# all connected minions to all MWorker-processes and greatly improves the

# performance of max_minions.

# con_cache: False

# The master can include configuration from other files. To enable this,

# pass a list of paths to this option. The paths can be either relative or

# absolute; if relative, they are considered to be relative to the directory

# the main master configuration file lives in (this file). Paths can make use

# of shell-style globbing. If no files are matched by a path passed to this

# option, then the master will log a warning message.

#

# Include a config file from some other path:

#include: /etc/salt/extra_config

#

# Include config from several files and directories:

#include:

#  - /etc/salt/extra_config

#####        Security settings       #####

##########################################

# Enable "open mode", this mode still maintains encryption, but turns off

# authentication, this is only intended for highly secure environments or for

# the situation where your keys end up in a bad state. If you run in open mode

# you do so at your own risk!

#open_mode: False

# Enable auto_accept, this setting will automatically accept all incoming

# public keys from the minions. Note that this is insecure.

#auto_accept: False

# Time in minutes that a incomming public key with a matching name found in

# pki_dir/minion_autosign/keyid is automatically accepted. Expired autosign keys

# are removed when the master checks the minion_autosign directory.

# 0 equals no timeout

# autosign_timeout: 120

# If the autosign_file is specified, incoming keys specified in the

# autosign_file will be automatically accepted. This is insecure.  Regular

# expressions as well as globing lines are supported.

#autosign_file: /etc/salt/autosign.conf

# Works like autosign_file, but instead allows you to specify minion IDs for

# which keys will automatically be rejected. Will override both membership in

# the autosign_file and the auto_accept setting.

#autoreject_file: /etc/salt/autoreject.conf

# Enable permissive access to the salt keys. This allows you to run the

# master or minion as root, but have a non-root group be given access to

# your pki_dir. To make the access explicit, root must belong to the group

# you've given access to. This is potentially quite insecure. If an autosign_file

# is specified, enabling permissive_pki_access will allow group access to that

# specific file.

#permissive_pki_access: False

# Allow users on the master access to execute specific commands on minions.

# This setting should be treated with care since it opens up execution

# capabilities to non root users. By default this capability is completely

# disabled.

#client_acl:

#  larry:

#    - test.ping

#    - network.*

# Blacklist any of the following users or modules

#

# This example would blacklist all non sudo users, including root from

# running any commands. It would also blacklist any use of the "cmd"

# module. This is completely disabled by default.

#

#client_acl_blacklist:

#  users:

#    - root

#    - '^(?!sudo_).*$'   #  all non sudo users

#  modules:

#    - cmd

# The external auth system uses the Salt auth modules to authenticate and

# validate users to access areas of the Salt system.

#external_auth:

#  pam:

#    fred:

#      - test.*

# Time (in seconds) for a newly generated token to live. Default: 12 hours

#token_expire: 43200

# Allow minions to push files to the master. This is disabled by default, for

# security purposes.

#file_recv: False

# Set a hard-limit on the size of the files that can be pushed to the master.

# It will be interpreted as megabytes. Default: 100

#file_recv_max_size: 100

# Signature verification on messages published from the master.

# This causes the master to cryptographically sign all messages published to its event

# bus, and minions then verify that signature before acting on the message.

#

# This is False by default.

#

# Note that to facilitate interoperability with masters and minions that are different

# versions, if sign_pub_messages is True but a message is received by a minion with

# no signature, it will still be accepted, and a warning message will be logged.

# Conversely, if sign_pub_messages is False, but a minion receives a signed

# message it will be accepted, the signature will not be checked, and a warning message

# will be logged. This behavior went away in Salt 2014.1.0 and these two situations

# will cause minion to throw an exception and drop the message.

# sign_pub_messages: False

#####    Master Module Management    #####

##########################################

# Manage how master side modules are loaded.

# Add any additional locations to look for master runners:

#runner_dirs: []

# Enable Cython for master side modules:

#cython_enable: False

#####      State System settings     #####

##########################################

# The state system uses a "top" file to tell the minions what environment to

# use and what modules to use. The state_top file is defined relative to the

# root of the base environment as defined in "File Server settings" below.

#state_top: top.sls

# The master_tops option replaces the external_nodes option by creating

# a plugable system for the generation of external top data. The external_nodes

# option is deprecated by the master_tops option.

#

# To gain the capabilities of the classic external_nodes system, use the

# following configuration:

# master_tops:

#   ext_nodes: <Shell command which returns yaml>

#

#master_tops: {}

# The external_nodes option allows Salt to gather data that would normally be

# placed in a top file. The external_nodes option is the executable that will

# return the ENC data. Remember that Salt will look for external nodes AND top

# files and combine the results if both are enabled!

#external_nodes: None

# The renderer to use on the minions to render the state data

#renderer: yaml_jinja

# The Jinja renderer can strip extra carriage returns and whitespace

# See http://jinja.pocoo.org/docs/api/#high-level-api

#

# If this is set to True the first newline after a Jinja block is removed

# (block, not variable tag!). Defaults to False, corresponds to the Jinja

# environment init variable "trim_blocks".

# jinja_trim_blocks: False

#

# If this is set to True leading spaces and tabs are stripped from the start

# of a line to a block. Defaults to False, corresponds to the Jinja

# environment init variable "lstrip_blocks".

# jinja_lstrip_blocks: False

# The failhard option tells the minions to stop immediately after the first

# failure detected in the state execution, defaults to False

#failhard: False

# The state_verbose and state_output settings can be used to change the way

# state system data is printed to the display. By default all data is printed.

# The state_verbose setting can be set to True or False, when set to False

# all data that has a result of True and no changes will be suppressed.

#state_verbose: True

# The state_output setting changes if the output is the full multi line

# output for each changed state if set to 'full', but if set to 'terse'

# the output will be shortened to a single line.  If set to 'mixed', the output

# will be terse unless a state failed, in which case that output will be full.

# If set to 'changes', the output will be full unless the state didn't change.

#state_output: full

# Automatically aggregate all states that have support for mod_aggregate by

# setting to True. Or pass a list of state module names to automatically

# aggregate just those types.

#

# state_aggregate:

#   - pkg

#

#state_aggregate: False

#####      File Server settings      #####

##########################################

# Salt runs a lightweight file server written in zeromq to deliver files to

# minions. This file server is built into the master daemon and does not

# require a dedicated port.

# The file server works on environments passed to the master, each environment

# can have multiple root directories, the subdirectories in the multiple file

# roots cannot match, otherwise the downloaded files will not be able to be

# reliably ensured. A base environment is required to house the top file.

# Example:

# file_roots:

#   base:

#     - /srv/salt/

#   dev:

#     - /srv/salt/dev/services

#     - /srv/salt/dev/states

#   prod:

#     - /srv/salt/prod/services

#     - /srv/salt/prod/states

#file_roots:

#  base:

#    - /srv/salt

#    - /srv/formulas/tomcat-formula

# The hash_type is the hash to use when discovering the hash of a file on

# the master server. The default is md5, but sha1, sha224, sha256, sha384

# and sha512 are also supported.

#

# Prior to changing this value, the master should be stopped and all Salt

# caches should be cleared.

#hash_type: md5

# The buffer size in the file server can be adjusted here:

#file_buffer_size: 1048576

# A regular expression (or a list of expressions) that will be matched

# against the file path before syncing the modules and states to the minions.

# This includes files affected by the file.recurse state.

# For example, if you manage your custom modules and states in subversion

# and don't want all the '.svn' folders and content synced to your minions,

# you could set this to '/\.svn($|/)'. By default nothing is ignored.

#file_ignore_regex:

#  - '/\.svn($|/)'

#  - '/\.git($|/)'

# A file glob (or list of file globs) that will be matched against the file

# path before syncing the modules and states to the minions. This is similar

# to file_ignore_regex above, but works on globs instead of regex. By default

# nothing is ignored.

# file_ignore_glob:

#  - '*.pyc'

#  - '*/somefolder/*.bak'

#  - '*.swp'

# File Server Backend

#

# Salt supports a modular fileserver backend system, this system allows

# the salt master to link directly to third party systems to gather and

# manage the files available to minions. Multiple backends can be

# configured and will be searched for the requested file in the order in which

# they are defined here. The default setting only enables the standard backend

# "roots" which uses the "file_roots" option.

#fileserver_backend:

#  - roots

#

# To use multiple backends list them in the order they are searched:

#fileserver_backend:

#  - git

#  - roots

#

# Uncomment the line below if you do not want the file_server to follow

# symlinks when walking the filesystem tree. This is set to True

# by default. Currently this only applies to the default roots

# fileserver_backend.

#fileserver_followsymlinks: False

#

# Uncomment the line below if you do not want symlinks to be

# treated as the files they are pointing to. By default this is set to

# False. By uncommenting the line below, any detected symlink while listing

# files on the Master will not be returned to the Minion.

#fileserver_ignoresymlinks: True

#

# By default, the Salt fileserver recurses fully into all defined environments

# to attempt to find files. To limit this behavior so that the fileserver only

# traverses directories with SLS files and special Salt directories like _modules,

# enable the option below. This might be useful for installations where a file root

# has a very large number of files and performance is impacted. Default is False.

# fileserver_limit_traversal: False

#

# The fileserver can fire events off every time the fileserver is updated,

# these are disabled by default, but can be easily turned on by setting this

# flag to True

#fileserver_events: False

# Git File Server Backend Configuration

#

# Gitfs can be provided by one of two python modules: GitPython or pygit2. If

# using pygit2, both libgit2 and git must also be installed.

#gitfs_provider: gitpython

#

# When using the git fileserver backend at least one git remote needs to be

# defined. The user running the salt master will need read access to the repo.

#

# The repos will be searched in order to find the file requested by a client

# and the first repo to have the file will return it.

# When using the git backend branches and tags are translated into salt

# environments.

# Note:  file:// repos will be treated as a remote, so refs you want used must

# exist in that repo as *local* refs.

#gitfs_remotes:

#  - git://github.com/saltstack/salt-states.git

#  - file:///var/git/saltmaster

#

# The gitfs_ssl_verify option specifies whether to ignore ssl certificate

# errors when contacting the gitfs backend. You might want to set this to

# false if you're using a git backend that uses a self-signed certificate but

# keep in mind that setting this flag to anything other than the default of True

# is a security concern, you may want to try using the ssh transport.

#gitfs_ssl_verify: True

#

# The gitfs_root option gives the ability to serve files from a subdirectory

# within the repository. The path is defined relative to the root of the

# repository and defaults to the repository root.

#gitfs_root: somefolder/otherfolder

#####         Pillar settings        #####

##########################################

# Salt Pillars allow for the building of global data that can be made selectively

# available to different minions based on minion grain filtering. The Salt

# Pillar is laid out in the same fashion as the file server, with environments,

# a top file and sls files. However, pillar data does not need to be in the

# highstate format, and is generally just key/value pairs.

#pillar_roots:

#  base:

#    - /srv/pillar

#ext_pillar:

#  - hiera: /etc/hiera.yaml

#  - cmd_yaml: cat /etc/salt/yaml

# The pillar_gitfs_ssl_verify option specifies whether to ignore ssl certificate

# errors when contacting the pillar gitfs backend. You might want to set this to

# false if you're using a git backend that uses a self-signed certificate but

# keep in mind that setting this flag to anything other than the default of True

# is a security concern, you may want to try using the ssh transport.

#pillar_gitfs_ssl_verify: True

# The pillar_opts option adds the master configuration file data to a dict in

# the pillar called "master". This is used to set simple configurations in the

# master config file that can then be used on minions.

#pillar_opts: True

#####          Syndic settings       #####

##########################################

# The Salt syndic is used to pass commands through a master from a higher

# master. Using the syndic is simple, if this is a master that will have

# syndic servers(s) below it set the "order_masters" setting to True, if this

# is a master that will be running a syndic daemon for passthrough the

# "syndic_master" setting needs to be set to the location of the master server

# to receive commands from.

# Set the order_masters setting to True if this master will command lower

# masters' syndic interfaces.

#order_masters: False

# If this master will be running a salt syndic daemon, syndic_master tells

# this master where to receive commands from.

#syndic_master: masterofmaster

# This is the 'ret_port' of the MasterOfMaster:

#syndic_master_port: 4506

# PID file of the syndic daemon:

#syndic_pidfile: /var/run/salt-syndic.pid

# LOG file of the syndic daemon:

#syndic_log_file: syndic.log

#####      Peer Publish settings     #####

##########################################

# Salt minions can send commands to other minions, but only if the minion is

# allowed to. By default "Peer Publication" is disabled, and when enabled it

# is enabled for specific minions and specific commands. This allows secure

# compartmentalization of commands based on individual minions.

# The configuration uses regular expressions to match minions and then a list

# of regular expressions to match functions. The following will allow the

# minion authenticated as foo.example.com to execute functions from the test

# and pkg modules.

#peer:

#  foo.example.com:

#    - test.*

#    - pkg.*

#

# This will allow all minions to execute all commands:

#peer:

#  .*:

#    - .*

#

# This is not recommended, since it would allow anyone who gets root on any

# single minion to instantly have root on all of the minions!

# Minions can also be allowed to execute runners from the salt master.

# Since executing a runner from the minion could be considered a security risk,

# it needs to be enabled. This setting functions just like the peer setting

# except that it opens up runners instead of module functions.

#

# All peer runner support is turned off by default and must be enabled before

# using. This will enable all peer runners for all minions:

#peer_run:

#  .*:

#    - .*

#

# To enable just the manage.up runner for the minion foo.example.com:

#peer_run:

#  foo.example.com:

#    - manage.up

#####         Mine settings     #####

##########################################

# Restrict mine.get access from minions. By default any minion has a full access

# to get all mine data from master cache. In acl definion below, only pcre matches

# are allowed.

# mine_get:

#   .*:

#     - .*

#

# The example below enables minion foo.example.com to get 'network.interfaces' mine

# data only, minions web* to get all network.* and disk.* mine data and all other

# minions won't get any mine data.

# mine_get:

#   foo.example.com:

#     - network.interfaces

#   web.*:

#     - network.*

#     - disk.*

#####         Logging settings       #####

##########################################

# The location of the master log file

# The master log can be sent to a regular file, local path name, or network

# location. Remote logging works best when configured to use rsyslogd(8) (e.g.:

# ``file:///dev/log``), with rsyslogd(8) configured for network logging. The URI

# format is: <file|udp|tcp>://<host|socketpath>:<port-if-required>/<log-facility>

#log_file: /var/log/salt/master

#log_file: file:///dev/log

#log_file: udp://loghost:10514

#log_file: /var/log/salt/master

#key_logfile: /var/log/salt/key

# The level of messages to send to the console.

# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.

#log_level: warning

# The level of messages to send to the log file.

# One of 'garbage', 'trace', 'debug', info', 'warning', 'error', 'critical'.

# If using 'log_granular_levels' this must be set to the highest desired level.

#log_level_logfile: warning

# The date and time format used in log messages. Allowed date/time formating

# can be seen here: http://docs.python.org/library/time.html#time.strftime

#log_datefmt: '%H:%M:%S'

#log_datefmt_logfile: '%Y-%m-%d %H:%M:%S'

# The format of the console logging messages. Allowed formatting options can

# be seen here: http://docs.python.org/library/logging.html#logrecord-attributes

#log_fmt_console: '[%(levelname)-8s] %(message)s'

#log_fmt_logfile: '%(asctime)s,%(msecs)03.0f [%(name)-17s][%(levelname)-8s] %(message)s'

# This can be used to control logging levels more specificically.  This

# example sets the main salt library at the 'warning' level, but sets

# 'salt.modules' to log at the 'debug' level:

#   log_granular_levels:

#     'salt': 'warning'

#     'salt.modules': 'debug'

#

#log_granular_levels: {}

#####         Node Groups           #####

##########################################

# Node groups allow for logical groupings of minion nodes. A group consists of a group

# name and a compound target.

#nodegroups:

#  group1: 'L...@foo.domain.com,bar.domain.com,baz.domain.com and bl*.domain.com'

#  group2: 'G@os:Debian and foo.domain.com'

#####     Range Cluster settings     #####

##########################################

# The range server (and optional port) that serves your cluster information

# https://github.com/ytoolshed/range/wiki/%22yamlfile%22-module-file-spec

#

#range_server: range:80

#####     Windows Software Repo settings #####

##############################################

# Location of the repo on the master:

#win_repo: '/srv/salt/win/repo'

# Location of the master's repo cache file:

#win_repo_mastercachefile: '/srv/salt/win/repo/winrepo.p'

# List of git repositories to include with the local repo:

#win_gitrepos:

#  - 'https://github.com/saltstack/salt-winrepo.git'

[root@osboxes salt]#

[jack cam]

Your issue is very odd because I created the same formula and it's work for me but for tomcat 7 :

tomcat.sls (state)

{{ tomcat.prefix }}/apache-tomcat-{{ tomcat.version.full }}:

  archive:

    - extracted

    - name: {{ tomcat.prefix }}

    - source: {{ tomcat.source.url }}

    - source_hash: md5={{ tomcat.source.md5 }}

    - archive_format: tar

    - tar_options: xz

    - if_missing: {{ tomcat.prefix }}/apache-tomcat-{{ tomcat.version.full }}

    - require:

      - file: {{ tomcat.prefix }}

  {%- if 'user' in tomcat or 'group' in tomcat %}

  file.directory:

    {% if 'user' in tomcat %}

    - user: {{ tomcat.user }}

    {% endif -%}

    {% if 'group' in tomcat %}

    - group: {{ tomcat.group }}

    {% endif -%}

    - recurse:

      - user

      - group

    - watch:

      - archive: {{ tomcat.prefix }}/apache-tomcat-{{ tomcat.version.full }}

  {%- endif %}

{{ tomcat.prefix }}/tomcat{{ tomcat.version.major }}:

    file.symlink:

      {% if 'user' in tomcat %}

      - user: {{ tomcat.user }}

      {% endif -%}

      {% if 'group' in tomcat %}

      - group: {{ tomcat.group }}

      {% endif -%}

      - target: {{ tomcat.prefix }}/apache-tomcat-{{ tomcat.version.full }}

      - force: True

      - watch:

        - archive: {{ tomcat.prefix }}/apache-tomcat-{{ tomcat.version.full }}

{% endif -%}

tomcat.sls (pillar)

tomcat:

  install:

    prefix: /lsf/opt

    user: appserv

    group: appserv

    version:

      major: 7

      full: 7.0.55

    source:

      url: salt://apache-tomcat-7.0.55.tar.gz

      md5: 3c46fc0f608c1280dcd65100a983f285

[jack cam]

If you can try to update to version 2014.7.2 I'm pretty this version resolved your problem.

See this issue for more information:

https://github.com/saltstack/salt/issues/20485

https://github.com/saltstack/salt/issues/20852

[CalgarySaltUser]

Thanks Jack! That's exactly what the problem was