[ovirt-users] Re: Health Warning: Cinnamon toxic when adding EL7 nodes as oVirt hosts

Otopi seems to generate a tarball on the host that runs the wizard from, which is then forwarded to the hosted-engine VM for execution. In that context a version comparison function (something like "CompareEVR") fails to execute, because that requires rpmUtils to be loaded. To my shame I am not a Python programmer, but it seems to be late-binding, which may be why it's not universally failing at the import of the rpmUtils, but only when Compare..EVR is called. Tracing what's going on in the dynamic context of a Pyhon program executing from an tarball, that's just been sent over an SSH wire to a VM that lies in agony... is a bit steep, especially because it takes an hour to recreate the circumstances. Perhaps I'd volunteer to try 4.4 early instead ;-) The oVirtNodes work just fine and that's what I fell back on early, when I wasn't sure about the cause. But one usage scenario involves big machine learning compute hosts running Nvidia workloads on V100 GPUs in Docker containers (or basically bare metal), while some support workloads would be managed in an oVirt corner on those same hosts. It basically anticipates where oVirt wants to go, mixing scale-in and scale-out workloads under one management framework. It's also necessary, as many current ML capable GPUs aren't actually supported inside virtual machines for market segmentation reasons. I believe the bug tracker has a native attachment facility: I was just slightly confused that I might see a different UI than everybody else. Likewise and thanks for your encouraging help so far!