Hello,
I'm facing an issue where, in a new fresh installed Oracle OLVM - Ovirt 4.5.4,
self-hosted engine with NFS shared storage.
That an .OVA file cannot be imported.
Steps to reproduce:
- Created test virtual machine in an NFS storage domain, installed it, allright working
fine.
- Shutdown test VM
- Export test VM to a purposedly created directory /home/vdsm, whose owner is vdsm:kvm
with full permissions.
- Export .OVA file concludes successfully and the file is created at that location
Then, in the exact same server, same datacenter.
- Rename source VM so it doesn't conflict because the same name (same result if I
delete the source VM)
- try to import the .OVA. using the GUI. It finds successfully the file at the specified
location and begins the procedure
-# up to a given point, it fails without more indications at the web GUI. No more info at
the "events" than "Failed to import vm Test to Datacenter".
Fiddling into the logs, I was able to find in the hosted-engine VM, at
/var/log/ovirt-engine/ova the log that goes by
"ovirt-ova-external-data-ansible-DATE-HostFQDN-uuid.log" an error that
specifiies
stdout_lines" : [ "tput: No value for $TERM and no -T specified",
"tput: No value for $TERM and no -T specified", "tput: No value for $TERM
and no -T specified"
I tinkered with the ansible role that calls a python script called
"get_ova_data.py" (located at
/usr/share/ovirt-engine/ansible-runner-service-project/project/roles-/ovirt-ova-external-data/)
I tried to define the variable TERM into null or into xterm but then it fails in another
manner complaining about that variable.
By surfing the webs, it seems something calls "tput" like if it was in console
mode but then it breaks.
Can I have some help with this, please?
Thanks
Show replies by date