Closed gfa closed 9 years ago
I was having the same problem on 2014.7.1 and after some digging it looks like the culprit is this line in archive.py:
tar_cmd = ['tar', 'x{0}'.format(tar_options), '-f', repr(filename)]
The repr(filename) part mucks with the filename. I edited archive.py in my environment to make the line read:
tar_cmd = ['tar', 'x{0}'.format(tar_options), '-f', filename]
and everything worked fine for me.
It also looks like this has been fixed by this commit, https://github.com/saltstack/salt/commit/c727e55a7f6d8e7e9bbef2da79243b267ce2d49f, althought I haven't verified that yet.
Thanks for the report. We have been seeing this issue come and go. Basically what happened was the behavior in 2014.1.x
releases was to not provide the x in the state file. However, when we released 2014.7.0
, the behavior switched, causing a regression. We marked it as a regression and then changed it back. The thought there being archive.extracted
implies an x
by default.
The quick fix here is to remove the x
from your state. That is currently the "expected behavior" of this state.
That being said, we should just make this accept either an x or no x and have the state work regardless.
@cjworden You're right! Looks like what I just stated was already fixed. Thanks for tracking that down.
@gfa The fix listed above is available in the 2014.7.2 release.
yeah this one bit me too.
I am using 'salt masterless' instructions at http://docs.saltstack.com/en/latest/topics/tutorials/quickstart.html, which retrieves install script from bootstrap.salt.com
is there an easy way to make it d/l the release i want, which does not have this bug?
what longsuffering person has to maintain a 5k-line bash script? forgive me for not digging deeply into it.
i tried
sudo sh ~/install_salt.sh git v2014.7.2
but get
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
I did the dpkg command as recommended.
vagrant@box:/opt$ salt-call --versions-report Salt: 2014.7.2 Python: 2.7.6 (default, Mar 22 2014, 22:59:56) Jinja2: 2.7.2 M2Crypto: 0.21.1 msgpack-python: 0.3.0 msgpack-pure: Not Installed pycrypto: 2.6.1 libnacl: Not Installed PyYAML: 3.10 ioflo: Not Installed PyZMQ: 14.0.1 RAET: Not Installed ZMQ: 4.0.4 Mako: 0.9.1
hurray!
@dmargrave You can find a lot of helpful information about the bootstrap script here: https://github.com/saltstack/salt-bootstrap. Some of the things that will help you out here is passing in git tags, branches, or shas, as you've mentioned above (so you could substitute v2014.7.2
with 2014.7
to install from the HEAD of the 2014.7 branch). One thing you could try is to use either a newer version of the script (not sure which one you're using...you can see the version at the top of the script, which is date-based).
Any bugs you run into the the bootstrap script should be submitted directly against that repository. Once bugs are resolved in the bootstrap's repo, the stable release gets updated, and the salt repo gets updated with the new script. @s0undt3ch is the one who usually maintains this.
this is the log
this is the state file
tar file is downloaded ok, if i manually go to the minion and cd /opt/ i can extract the file doing tar xxj -f /var/cache/salt/minion/files/base/_optmonitoring-for-openstack.tar
this worked before, 2014.7.0 and 2014.1