On Wed, Jun 20, 2018 at 10:31 AM, Viktor VM Mihajlovski <mihajlov@linux.vnet.ibm.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? Not sure whether this is the same issue, but I had to install the 'yum'
On 20.06.2018 00:21, Nir Soffer wrote: package manually on the host (even on F27)
Indeed. But this wasn't good, and only happened by an accident, if you ask me. You then entered a state that you had both dnf and yum installed, each having its own db etc (e.g. check 'yum history' and 'dnf history'). I emailed about this some time ago.
to be able to add it to 4.2 engine. However, on F28 the ansible task to configure the firewall will fail since there seems to be no python-2 binding for it.
Didn't check the details, but we made a decision to stop going this path, of trying to use python2 on fedora. We currently (on master branch) do build for both 2 and 3, and I don't mind adding minimal testing to make sure 2 continues to work, but default to 3 on fedora, and working on making all the relevant tools work with 3 as well. The code itself will remain compatible with 2, of course, as we use it also on el7. So if anyone wants to try and make otopi/host-deploy/etc use (optionally!) python2 on fedora and make it work this way, I don't mind getting patches. But the future seems to be python3, no reason to fight that...
I must have a host when I can build and test virt-v2v upstream from source, and virt-v2v requires python 3. So I need some workaround to get the host connected to engine.
Nir
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AJRHHOSCNGUO3V...
-- Regards, Viktor Mihajlovski _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZBLGMDJNLB77K7...
-- Didi