[Engine-devel] ovirt-shell problem on F16 and nightly builds

Itamar Heim iheim at redhat.com
Fri Mar 16 11:11:58 UTC 2012


On 03/16/2012 12:23 PM, Gianluca Cecchi wrote:
> Hello,
> sorry if this is a -devel mailing list. Let me know please if I have to
> send to another list.

users mailing list probably more relevant.
any reason you are taking nightly, rather than published/tested versions 
(nightly builds is not necessarily tested/stable)
http://lists.ovirt.org/pipermail/users/2012-March/001158.html
http://lists.ovirt.org/pipermail/users/2012-March/001159.html

>
> Would like to test ovirt-shell against an RH EV 3.0 installation.
> My system is based on F16 x86_64.
> Installed from nightly builds directory:
>
> Mar 16 11:02:30 Installed: python-lxml-2.3-1.fc16.x86_64
> Mar 16 11:02:30 Installed: ovirt-engine-sdk-1.6.1-1.fc16.noarch
> Mar 16 11:02:30 Installed: pexpect-2.3-6.fc15.noarch
> Mar 16 11:02:30 Installed: python-ply-3.3-5.fc15.noarch
> Mar 16 11:02:30 Installed: ovirt-engine-cli-2.1.2-1.fc16.noarch
>
> But
>
> $ ovirt-shell --help
> Traceback (most recent call last):
>    File "/usr/bin/ovirt-shell", line 9, in <module>
>      load_entry_point('ovirt-shell==2.1.2-SNAPSHOT', 'console_scripts',
> 'ovirt-shell')()
>    File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 337,
> in load_entry_point
>      return get_distribution(dist).load_entry_point(group, name)
>    File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2279,
> in load_entry_point
>      return ep.load()
>    File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1989,
> in load
>      entry = __import__(self.module_name, globals(),globals(), ['__name__'])
>    File "/usr/lib/python2.7/site-packages/ovirtcli/main.py", line 20, in
> <module>
>      from ovirtcli.context import OvirtCliExecutionContext
>    File "/usr/lib/python2.7/site-packages/ovirtcli/context.py", line 18,
> in <module>
>      from cli.command import *
>    File "/usr/lib/python2.7/site-packages/cli/command/__init__.py", line
> 2, in <module>
>      from cli.command.command import Command
>    File "/usr/lib/python2.7/site-packages/cli/command/command.py", line
> 21, in <module>
>      from ovirtcli.utils.methodhelper import MethodHelper
>    File
> "/usr/lib/python2.7/site-packages/ovirtcli/utils/methodhelper.py", line
> 20, in <module>
>      from codegen.doc.documentation import Documentation
> ImportError: No module named codegen.doc.documentation
>
> Probably it is something stupid I miss?
> I installed them with
> sudo yum localinstall ovirt-engine-cli-2.1.2-1.fc16.noarch.rpm
> ovirt-engine-sdk-1.6.1-1.fc16.noarch.rpm
>
> and got:
> Loaded plugins: auto-update-debuginfo, downloadonly, langpacks, presto,
> refresh-packagekit
> Setting up Local Package Process
> Examining ovirt-engine-cli-2.1.2-1.fc16.noarch.rpm:
> ovirt-engine-cli-2.1.2-1.fc16.noarch
> Marking ovirt-engine-cli-2.1.2-1.fc16.noarch.rpm to be installed
> Examining ovirt-engine-sdk-1.6.1-1.fc16.noarch.rpm:
> ovirt-engine-sdk-1.6.1-1.fc16.noarch
> Marking ovirt-engine-sdk-1.6.1-1.fc16.noarch.rpm to be installed
> Resolving Dependencies
> --> Running transaction check
> ---> Package ovirt-engine-cli.noarch 0:2.1.2-1.fc16 will be installed
> --> Processing Dependency: pexpect for package:
> ovirt-engine-cli-2.1.2-1.fc16.noarch
> --> Processing Dependency: python-ply for package:
> ovirt-engine-cli-2.1.2-1.fc16.noarch
> ---> Package ovirt-engine-sdk.noarch 0:1.6.1-1.fc16 will be installed
> --> Processing Dependency: python-lxml for package:
> ovirt-engine-sdk-1.6.1-1.fc16.noarch
> --> Running transaction check
> ---> Package pexpect.noarch 0:2.3-6.fc15 will be installed
> ---> Package python-lxml.x86_64 0:2.3-1.fc16 will be installed
> ---> Package python-ply.noarch 0:3.3-5.fc15 will be installed
> --> Finished Dependency Resolution
>
> Dependencies Resolved
>
> possibly any dependency problem in rpm composition?
> Thanks in advance,
> Gianluca
>
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel




More information about the Engine-devel mailing list