Upgrading salt on my master caused dependency issues

[Auha]

I don't know exactly where to report this or put it, but we can go from here.

System: Ubuntu 14.04
PPA: Saltstack and Chris-Lea/zeromq

I did a normal upgrade and upgraded my saltstack via apt-get. The upgrade went okay, but I was unable to run salt commands correctly. It kept on throwing issues because it could not find the correct zmq. pyzmq was installed correctly.

I found out the version was incorrect. I had to back out my pyzmq package from Ubuntu and push in the correct package from pypi.

I would consider this a low issue as there are workarounds.

[thatch45]

What version of pyzmq did you have before? We should not hard dep on a new pyzmq...

[Auha]

I don't know what version of pyzmq I had before. I just did an apt-get
upgrade and it broke salt. I just did some troubleshooting and it seemed
that my version of pyzmq was too "new"

~Jonathan C.

On Tue, Nov 25, 2014 at 10:07 AM, Thomas S Hatch notifications@github.com
wrote:

What version of pyzmq did you have before? We should not hard dep on a new
pyzmq...

—
Reply to this email directly or view it on GitHub
#18476 (comment).

[rallytime]

@Auha Does the salt --versions-report work for you? Can you post the output of that command so we can see what you've got for your new pyzmq version and various other packages?

[rallytime]

This looks similar to #18465.

[wwentland]

@Auha Could you try removing the PPA and downgrading to the official packages in the Ubuntu repository of libzmq3 and python-zmq? I guess that that would fix your issue and you don't need that PPA anyway.

[Auha]

So I uninstalled and removed the PPA. When I pulled in the python-zmq from the normal Ubuntu Repos I still had the same issues that it was still too "new."

What I ended up having to do was to uninstall all of it. Do a pip install from Pypi at version 13, and it finally worked after that.

@rallytime I'm sorry, but I don't have the version report of when the issue occurred. But here it is now:

           Salt: 2014.7.0
         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: 13.0.0
           RAET: Not Installed
            ZMQ: 3.2.2
           Mako: 0.9.1

PyZMQ when I first did the install was around 14.4. The regular ubuntu repos it was at 14.0.1 I believe. I downgraded using pip to 13.0.0.

Do note that my version of ubuntu is 14.04 and have the saltstack PPA added.

[joehealy]

This is coming from (probably broken) packages from the clea ppa. Our instructions on installation are unclear, but can be read as recommending installing the packages from there. The instructions need to be modified and we need to get updated zmq packages in our ppa. I'm happy to do the zmq backporting.

[rallytime]

I think this issue was caused by some unclear information in our documentation, as @joehealy pointed out. I've submitted a pull request to clear up the discrepancy. @Auha Does that help resolve this issue for you? Can this be closed?

@joehealy When ZMQ4 packages are backported for other Ubuntu releases earlier than Utopic, we can adjust those instructions.

[joehealy]

Sounds good.

On Tue, Dec 2, 2014 at 5:53 AM, Nicole Thomas notifications@github.com
wrote:

I think this issue was caused by some unclear information in our
documentation, as @joehealy https://github.com/joehealy pointed out.
I've submitted a pull request to clear up the discrepancy. @Auha
https://github.com/Auha Does that help resolve this issue for you? Can
this be closed?

@joehealy https://github.com/joehealy When ZMQ4 packages are backported
for other Ubuntu releases earlier than Utopic, we can adjust those
instructions.

—
Reply to this email directly or view it on GitHub
#18476 (comment).