can't find entry point of lava-tool 0.2 after using lava-deployment-tool

[Spring Zhang]

lava-tool version is 0.3 in fact.

Before the installation, the lava-tool cmd can work. But after it, see the logs:

<BPARK> imp@Mybuntu:~/lava-img$ lava-tool submit-job http://lava@192.168.1.222/lava-server/RPC2/ gpu.json
<BPARK> Traceback (most recent call last):
<BPARK> File "/usr/local/bin/lava-tool", line 5, in <module>
<BPARK> from pkg_resources import load_entry_point
<BPARK> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2676, in <module>
<BPARK> parse_requirements(__requires__), Environment()
<BPARK> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 552, in resolve
<BPARK> raise DistributionNotFound(req)
<BPARK> pkg_resources.DistributionNotFound: lava-tool==0.2
<BPARK> imp@Mybuntu:~/lava-img$

[Zygmunt Krynicki (zyga)]

This error message means that whatever lava-tool used to be loading is no longer available (the actual module is gone)

What is the PATH you have on that machine? (when you say which lava-tool, what is the output)

Normally it's 100% safe to mix client side tools from debian packages and any number of lava-deployment-tool instances with any software as they don't interact in any way and are 100% isolated from each other. The downside is that you need to explicitly "ask" for an instance version by using the full path to the binary.

[Spring Zhang (qzhang)]

I cleaned up my lava-tool installation of apt-get and pip, now using one way, it's ok now, thanks.