- Users - oVirt List Archives

gnome keyring and ssh passphrase?
by Gianluca Cecchi 21 May '18

21 May '18

Hello, I'm starting here in F28 to use gnome session again, after some Fedora versions... I was in Mate up to some days ago and the ssh passphrase was in need to be inserted only once in mater-terminal, because I had this in my .bashrc (I think) export SSH_ASKPASS="/usr/bin/ksshaskpass" Now I see that my gnome-terminal continues to ask my passhprase without giving chance to save it into its keyring. I read this https://wiki.gnome.org/Projects/GnomeKeyring/Ssh but I haven't completely understood it (if it is current) It seems gnome-keyring-daemon is running [g.cecchi@ope46 ~]$ ps -ef|grep keyr g.cecchi 1972 1 0 08:44 ? 00:00:13 /usr/bin/gnome-keyring-daemon --daemonize --login g.cecchi 16480 14954 0 15:11 pts/8 00:00:00 grep --color=auto keyr [g.cecchi@ope46 ~]$ but is there any other setting to do not to insert every time my passhrase? Thanks, Gianluca

1 1

hosted-engine ovirt-engine server not run
by dhy336＠sina.com 21 May '18

21 May '18

Hi I deploy hosted-engine with two nodes, when I power off the node that engine is runing, other node can run VM after about 3 minutes.but ovirt-engine server could not normally run. but systemctrl resetart ovirt-engine. ovirt-engine server can run. this is VM engine logs.

2 1

vGPU VM not starting
by Callum Smith 21 May '18

21 May '18

Dear All, Our vGPU installation is progressing, though the VM is failing to start. 2018-05-16 22:57:34,328+0100 ERROR (vm/1bc9dae8) [virt.vm] (vmId='1bc9dae8-a0ea-44b3-9103-5805100648d0') The vm start process failed (vm:943) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2872, in _run dom.createWithFlags(flags) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in createWithFlags if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) libvirtError: Cannot get interface MTU on '': No such device That's the specific error, some other information. It seems the GPU 'allocation' of uuid against the nvidia-xx mdev type is proceeding correctly, and the device is being created by the VM instantiation but the VM does not succeed in going up with this error. Any other logs or information relevant to help diagnose? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

3 4

User & Roles
by Simon Coter 21 May '18

21 May '18

Hi, I'm looking how-to create roles/users and give them access to specific datacenter/host(s). I looked on the documentation but I hadn't been able to find the proper section; anyone that can give me an help ? Thanks Simon

3 3

Preventing users to see other VMs
by Aziz 21 May '18

21 May '18

Hi list, I'm trying to remove the default "everyone" user from Ovirt, so that each user can have access to its own interface to manage a unique VM. I wonder if this is possible, because so far I'm unable to remove everyone user. Thank you

4 11

offsite data replication
by ovirt＠fateknollogee.com 21 May '18

21 May '18

I read somewhere that RHEL 7.5 makes "offsite data replication" easy to do. Is this feature available in oVirt?

2 2

Hosted Engine Setup error (oVirt v4.2.3)
by ovirt＠fateknollogee.com 21 May '18

21 May '18

Engine network config error Following this blog post: https://www.ovirt.org/blog/2018/02/up-and-running-with-ovirt-4-2-and-gluste… I get an error saying the hosted engine setup is "trying" to use vibr0 (192.168.xxx.x) even though I have the bridge interface set to "eno1" Regardless of whether the Edit Hosts File is checked or unchecked, it overwrites my engine IP entry from 10.50.235.x to 192.168.xxx.x The same thing happens whether I set the engine IP to Static or DHCP (I don't have DNS, I'm using static entries in /etc/hosts). Any ideas it "insists" on using "vibr0" instead of "eno1"? **also posted this on IRC

5 33

oVirt Gluster storage hardware
by ovirt＠fateknollogee.com 21 May '18

21 May '18

For those folks using SSD with Gluster, are you doing RAID or HBA? Which is recommended for performance. (I've asked this question before, not sure I got a good answer)

1 0

Unable to start VM after 4.2 upgrade
by Ernest Beinrohr 21 May '18

21 May '18

Hi, I updated my engine and 1 host to 4.2 from 4.1 and now I cannot start a VM and get this error: "UnsupportedType: Unsupported {} for ioTune". My other 6 4.1 hosts are able to start VM normally with the new 4.2 engine. My VM has this inside: <iotune read_bytes_sec="0" read_iops_sec="100" total_bytes_sec="0" total_iops_sec="0" write_bytes_sec="0" write_iops_sec="100"/> error: 1. 2018-05-17 14:30:38,006+0200 ERROR (vm/0d53dd5d) [virt.vm] (vmId='0d53dd5d-ef16-4763-bbdc-2dc173087bf5') The vm start process failed (vm:943) 2. Traceback (most recent call last): 3. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872, in _startUnderlyingVm 4. self._run() 5. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2882, in _run 6. self._domDependentInit() 7. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2458, in _domDependentInit 8. self._vmDependentInit() 9. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2495, in _vmDependentInit 10. self._sync_metadata() 11. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5158, in _sync_metadata 12. self._md_desc.dump(self._dom) 13. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 509, in dump 14. md_xml = self._build_xml() 15. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 721, in _build_xml 16. md_elem = self._build_tree(namespace, namespace_uri) 17. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 711, in _build_tree 18. dev_elem = _dump_device(metadata_obj, data) 19. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 800, in _dump_device 20. elems.append(_dump_device_spec_params(md_obj, value)) 21. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 866, in _dump_device_spec_params 22. spec_params_elem = md_obj.dump(_SPEC_PARAMS, **value) 23. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 229, in dump 24. _keyvalue_to_elem(self._add_ns(key), value, elem) 25. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 916, in _keyvalue_to_elem 26. raise UnsupportedType(key, value) 27. UnsupportedType: Unsupported {} for ioTune 28. 2018-05-17 14:30:38,006+0200 INFO (vm/0d53dd5d) [virt.vm] (vmId='0d53dd5d-ef16-4763-bbdc-2dc173087bf5') Changed state to Down: Unsupported {} for ioTune (code=1) (vm:1683) 29. 2018-05-17 14:30:38,007+0200 ERROR (vm/0d53dd5d) [root] FINISH thread <Thread(vm/0d53dd5d, stopped daemon 140237644748544)> failed (concurrent:201) 30. Traceback (most recent call last): 31. File "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 194, in run 32. ret = func(*args, **kwargs) 33. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 944, in _startUnderlyingVm 34. self.setDownStatus(ERROR, vmexitreason.GENERIC_ERROR, str(e)) 35. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 1685, in setDownStatus 36. self._update_metadata() 37. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5145, in _update_metadata 38. self._sync_metadata() 39. File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5158, in _sync_metadata 40. self._md_desc.dump(self._dom) 41. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 509, in dump 42. md_xml = self._build_xml() 43. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 721, in _build_xml 44. md_elem = self._build_tree(namespace, namespace_uri) 45. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 711, in _build_tree 46. dev_elem = _dump_device(metadata_obj, data) 47. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 800, in _dump_device 48. elems.append(_dump_device_spec_params(md_obj, value)) 49. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 866, in _dump_device_spec_params 50. spec_params_elem = md_obj.dump(_SPEC_PARAMS, **value) 51. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 229, in dump 52. _keyvalue_to_elem(self._add_ns(key), value, elem) 53. File "/usr/lib/python2.7/site-packages/vdsm/virt/metadata.py", line 916, in _keyvalue_to_elem 54. raise UnsupportedType(key, value) 55. UnsupportedType: Unsupported {} for ioTune

2 3

Upgrade from 4.1.9 to 4.2.3 fails to upgrade postgresql
by Ian Fraser 21 May '18

21 May '18

Hi, Could someone please provide advice on a production oVirt instance that fails to upgrade to 4.2.3? Engine and hosts are all running CentOS 7 As per the upgrade instructions in the release notes I run: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm # yum update "ovirt-*-setup*" # engine-setup Then I answer the questions and it fails with: ... [ INFO ] Upgrading PostgreSQL [ ERROR ] Failed to execute stage 'Misc configuration': Command '/opt/rh/rh-postgresql95/root/usr/bin/postgresql-setup' failed to execute [ INFO ] Yum Performing yum transaction rollback [ INFO ] Rolling back to the previous PostgreSQL instance (postgresql). [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20180516231622-3giicb.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20180516231735-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed When I check /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database user is the install user ok Checking database connection settings ok Checking for prepared transactions ok Checking for reg* system OID user data types ok Checking for contrib/isn with bigint-passing mismatch ok Checking for invalid "line" user columns ok Creating dump of global objects ok Creating dump of database schemas engine ovirt_engine_history postgres template1 ok lc_collate values for database "postgres" do not match: old "en_GB.UTF-8", new "en_US.UTF-8" Failure, exiting I have tried running the script here: https://gist.github.com/turboladen/6790847 and rerunning engine-setup but it fails with the same error. Can anyone offer any other suggestions? Best regards Ian Fraser Systems Administrator | Agency Sector Management (UK) Limited | www.asm.org.uk [t] +44 (0)1784 242200 | [f] +44 (0)1784 242012 | [e] Ian.Fraser(a)asm.org.uk Registered in England No. 2053849 | Registered address: Ashford House 41-45 Church Road Ashford Middx TW15 2TQ Follow us on twitter @asmukltd<https://twitter.com/asmukltd>

4 5