Hi,
I'm bootstrapping new VMs with the version of salt-minion in the official jessie repos, currently 2014.1.3. My salt-master then deploys the
saltstack.com repos and pushes the latest Debian packages with pkg.latest during highstate. This fails with the following in dpkg.log:
2015-06-11 22:52:06 upgrade salt-minion:all 2014.1.13+ds-3 2015.5.0+ds-1~bpo8+1
2015-06-11 22:52:06 status half-configured salt-minion:all 2014.1.13+ds-3
At this point all apt-get commands fail:
# apt-get install salt-minion
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
# dpkg --configure -a
Setting up python-chardet (2.3.0-1) ...
Setting up python-support (1.0.15) ...
Setting up python-ply (3.4-5) ...
Setting up python-pyasn1 (0.1.7-1) ...
Setting up python-six (1.8.0-1) ...
dpkg: error processing package salt-minion (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
Processing triggers for man-db (2.7.0.2-5) ...
Setting up python-urllib3 (1.9.1-3) ...
Setting up python-pycparser (2.10+dfsg-3) ...
Setting up python-dateutil (2.2-2) ...
Setting up python-cffi (0.8.6-1) ...
Setting up python-requests (2.4.3-6) ...
Setting up python-cryptography (0.6.1-1) ...
Setting up python-openssl (0.14-1) ...
Setting up python-ndg-httpsclient (0.3.2-1) ...
Processing triggers for python-support (1.0.15) ...
Errors were encountered while processing:
salt-minion
After I run this command, I'm able to reinstall salt-minion by hand. However, the minion can no longer talk to the master:
2015-06-11 23:09:15,034 [salt.scripts ][WARNING ][3014] ** Restarting minion **
2015-06-11 23:09:28,089 [salt.scripts ][ERROR ][3043] [Errno 2] No such file or directory: '/etc/salt/pki/minion/minion.pub'
Everything works as expected once I recreate minion.pub from the master's PKI directory. This is reproducible with every new jessie VM, though.
Is anyone else seeing anything like this?