On Wed, Jun 20, 2018 at 1:21 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
I'm trying to add a host running Fedora 28 to engine 4.2, and
installation
fails with:
2018-06-20 01:14:26,137+0300 DEBUG otopi.context context._executeMethod:143
method exception
Traceback (most recent call last):
File "/tmp/ovirt-Z5BGYej3Qa/pythonlib/otopi/context.py", line 133, in
_executeMethod
method['method']()
File
"/tmp/ovirt-Z5BGYej3Qa/otopi-plugins/ovirt-host-deploy/vdsm/vdsmid.py", line
84, in _packages
self.packager.install(('dmidecode',))
File "/tmp/ovirt-Z5BGYej3Qa/pythonlib/otopi/packager.py", line 102, in
install
raise NotImplementedError(_('Packager install not implemented'))
NotImplementedError: Packager install not implemented
2018-06-20 01:14:26,138+0300 ERROR otopi.context context._executeMethod:152
Failed to execute stage 'Environment packages setup': Packager install not
implemented
Do we have a way to workaround this?
Which version of otopi?
Gal (added) is currently working on fedora/python3 support for the stuff
we (integration-development team) maintain, including otopi. Several
relevant patches were merged in recent weeks, please update.
That said, I still do not consider fedora 28/python 3 "supported" -
in particular, I have no idea what the status of host-deploy is.
I must have a host when I can build and test virt-v2v upstream from source,
and virt-v2v requires python 3.
Must it have /usr/bin/python be python3?
So I need some workaround to get the host
connected to engine.
Must this be on fedora?
You can have python 3(.4) on el7 from epel.
You can have even newer ones from SCL.
If you do want/need fedora, please update to latest otopi
on your engine machine, make sure the bundle is updated, e.g. by removing it:
rm /var/cache/ovirt-engine/ovirt-host-deploy.tar
Then try to add the host, and share the host-deploy log. Thanks.
--
Didi