Updating salt-minion from 2014.1.13 to 2015.5.0 on Debian jessie fails

136 views
Skip to first unread message

Starchy Grant

unread,
Jun 11, 2015, 7:12:18 PM6/11/15
to salt-...@googlegroups.com
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?

Colton Myers

unread,
Jun 16, 2015, 1:11:17 PM6/16/15
to salt-...@googlegroups.com, Joe Healy
Hey Starchy,

I think you'll be better off if you install from the jessie repo from the start rather than installing jessie official first, which is quite out of date. Just add this apt source:

deb http://debian.saltstack.com/debian jessie-saltstack main

And then do an update and install the `salt-minion` and/or `salt-master`.

I also CC'd Joe Healy, our Debian packager, he may have some insight as to why your upgrade from the 2014.1 version in jessie official to the 2015.5.0 didn't go well.

--
Colton Myers
Platform Engineer, SaltStack
@basepi on Twitter/Github/IRC

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Starchy

unread,
Jun 30, 2015, 6:52:23 PM6/30/15
to salt-...@googlegroups.com
Thanks Colton, this does seem to work a bit better, but I still see the
"No such file or directory: '/etc/salt/pki/minion/minion.pub'" when I
start the 2015.5 salt-minion process. Could it be that 2015.5 doesn't
like having only the private key pre-seeded and expects the public key
to also be dropped in "by hand" even though 2014.1 and 2014.7 were OK
with it?

On 06/16/2015 10:10 AM, Colton Myers wrote:
> Hey Starchy,
>
> I think you'll be better off if you install from the jessie repo from
> the start rather than installing jessie official first, which is quite
> out of date. Just add this apt source:
>
> deb http://debian.saltstack.com/debian jessie-saltstack main
>
> And then do an update and install the `salt-minion` and/or `salt-master`.
>
> I also CC'd Joe Healy, our Debian packager, he may have some insight as
> to why your upgrade from the 2014.1 version in jessie official to the
> 2015.5.0 didn't go well.
>
> --
> Colton Myers
> Platform Engineer, SaltStack
> @basepi on Twitter/Github/IRC
>
> On Thu, Jun 11, 2015 at 5:12 PM, Starchy Grant <sta...@gmail.com
> <mailto:sta...@gmail.com>> wrote:
>
> 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 <http://saltstack.com> repos and pushes
> <mailto:salt-users+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Salt-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/salt-users/73z70NUgkpw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> salt-users+...@googlegroups.com
> <mailto:salt-users+...@googlegroups.com>.

Colton Myers

unread,
Jul 14, 2015, 6:35:01 PM7/14/15
to salt-...@googlegroups.com
That may be the case. I'm actually surprised that 2014.1 and 2014.7 didn't complain about only having a private key. That may be worth filing an issue.

--
Colton Myers
Platform Engineer, SaltStack
@basepi on Twitter/Github/IRC
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages