- Users - oVirt List Archives

LDAP - not able to find members of groups
by Timmi 09 May '19

09 May '19

Hi oVirt List, I manage to connect oVirt to my LDAP and I'm able to search for users and groups. I'm using openLDAP within a ClearOS installation and it looks like this is a bit different to the standard openLDAP. Inside the LDAP groups there is an attribute with is calls "member". Example: member cn=Timmi,ou=Users,ou=Accounts,dc=domain,dc=com Is someone able to help me how to make sure that oVirt is able to join the users to the groups? Best regards Timmi

2 2

Logical interface naming issues
by Tom Edwards 09 May '19

09 May '19

Hello oVirt community, Seems lik a bug. I don't have more than one environment to test on so I can't be 100% sure and didn't want to file a report (but didn't know where else to report this). I have a fresh install self hosted ovirt cluster 4.3.1.1-1.el7. When I build any logical network adapter with a "-" in the name ex "guest-network-01" the network interface names appear on the hosts (using ip addr command) as garbled names like on8cd19bc011414. They still appear to work, but when you try to make a VNic profile based on the broken name the VMs fail to boot, the VM has to be killed via command line on each host afterwards (they try to boot and hang on all hosts in the cluster corrupting the disk of the VM) because it can't find the parent logical network interface by name. Example errors: VM Security-Onion is down with error. Exit message: (1, 'Cannot find device "guest-dmz-ne"\n', ['/sbin/tc', 'qdisc', 'add', 'dev', 'guest-dmz-network', 'ingress']). VDSM ovirt-2 command DestroyVDS failed: General Exception: ('(1, \'Cannot find device "guest-dmz-ne"\\n\', [\'/sbin/tc\', \'filter\', \'show\', \'dev\', \'guest-dmz-network\', \'parent\', \'ffff:\'])',) That took me a very long time to figure out and broke many vms in the process =(

2 1

many 4.2 leftovers after upgrade 4.3.3
by Arman Khalatyan 09 May '19

09 May '19

Hello everybody, after the upgrade of ovirt-engine node I have several packages still pointing from 4.2 repo. Actually everything is working as expected. yum clean all&& yum upgrade does not find any updates, but reinstall bringing same packages from the 4.3 repo for example: *yum reinstall safelease.x86_64 Loaded plugins: changelog, fastestmirror, langpacks, vdsmupgrade, versionlockRepository centos-sclo-rh-release is listed more than once in the configurationLoading mirror speeds from cached hostfile * base: centos.mirrors.as250.net <http://centos.mirrors.as250.net> * centos-qemu-ev: ftp.rz.uni-frankfurt.de <http://ftp.rz.uni-frankfurt.de> * extras: ftp.rrzn.uni-hannover.de <http://ftp.rrzn.uni-hannover.de> * ovirt-4.3: ftp.nluug.nl <http://ftp.nluug.nl> * ovirt-4.3-epel: mirror.infonline.de <http://mirror.infonline.de> * updates: centos.mirrors.as250.net <http://centos.mirrors.as250.net>Resolving Dependencies--> Running transaction check---> Package safelease.x86_64 0:1.0-7.el7 will be reinstalled--> Finished Dependency ResolutionDependencies Resolved============================================================================================================================================================================================== Package Arch Version Repository Size==============================================================================================================================================================================================Reinstalling: safelease x86_64 1.0-7.el7 ovirt-4.3-centos-ovirt43 21 kTransaction Summary==============================================================================================================================================================================================Reinstall 1 PackageTotal download size: 21 kInstalled size: 43 kIs this ok [y/d/N]: * But we have many others, should I reinstall them manually to get right packages? *yum list installed | grep ovirt-4.2Repository centos-sclo-rh-release is listed more than once in the configurationcollectd.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-disk.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-postgresql.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-write_http.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolscollectd-write_syslog.x86_64 5.8.1-4.el7 @ovirt-4.2-centos-opstoolsgdeploy.noarch 2.0.8-1.el7 @ovirt-4.2-centos-gluster312nbdkit.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-python-common.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-python2.x86_64 1.2.7-2.el7 @ovirt-4.2-epelnbdkit-plugin-vddk.x86_64 1.2.7-2.el7 @ovirt-4.2-epelovirt-ansible-disaster-recovery.noarch 1.1.4-1.el7 @ovirt-4.2ovirt-ansible-image-template.noarch 1.1.9-1.el7 @ovirt-4.2ovirt-ansible-manageiq.noarch 1.1.13-1.el7 @ovirt-4.2ovirt-ansible-roles.noarch 1.1.6-1.el7 @ovirt-4.2ovirt-engine-cli.noarch 3.6.9.2-1.el7.centos @ovirt-4.2ovirt-js-dependencies.noarch 1.2.0-3.1.el7.centos @ovirt-4.2python-linecache2.noarch 1.0.0-1.el7 @ovirt-4.2-centos-ovirt42python-testtools.noarch 1.8.0-2.el7 @ovirt-4.2-centos-ovirt42python2-asn1crypto.noarch 0.23.0-2.el7 @ovirt-4.2-centos-ovirt42python2-cffi.x86_64 1.11.2-1.el7 @ovirt-4.2-centos-ovirt42python2-chardet.noarch 3.0.4-7.el7 @ovirt-4.2-centos-opstoolspython2-crypto.x86_64 2.6.1-16.el7 @ovirt-4.2-epelpython2-cryptography.x86_64 2.1.4-2.el7 @ovirt-4.2-centos-ovirt42python2-ecdsa.noarch 0.13-10.el7 @ovirt-4.2-epelpython2-extras.noarch 1.0.0-2.el7 @ovirt-4.2-centos-ovirt42python2-fixtures.noarch 3.0.0-7.el7 @ovirt-4.2-centos-ovirt42python2-idna.noarch 2.5-1.el7 @ovirt-4.2-centos-opstoolspython2-pyOpenSSL.noarch 17.3.0-3.el7 @ovirt-4.2-centos-ovirt42python2-pysocks.noarch 1.5.6-3.el7 @ovirt-4.2-centos-opstoolspython2-requests.noarch 2.19.1-4.el7 @ovirt-4.2-centos-opstoolspython2-traceback2.noarch 1.4.0-14.el7 @ovirt-4.2-centos-ovirt42python2-urllib3.noarch 1.21.1-1.el7 @ovirt-4.2-centos-opstoolssafelease.x86_64 1.0-7.el7 @ovirt-4.2-centos-ovirt42vdsm-jsonrpc-java.noarch 1.4.15-1.el7 @ovirt-4.2* Thanks,Arman.

2 2

EVENT_ID not generated for VM Reboot
by Sigbjorn Lie-Soland 08 May '19

08 May '19

Hi list, When a user powers down a VM from within the VM operating system (poweroff), a "moved from 'Up' --> 'Down'" message is written to engine.log, and a EVENT_ID: VM_DOWN is created -- 2019-05-08 20:53:03,495+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'Down' 2019-05-08 20:53:03,550+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: VM_DOWN(61), VM vmname1 is down. Exit message: User shut down from within the guest -- When a user starts a VM from the webadmin, a "moved from 'WaitForLaunch' --> 'PoweringUp'" and "'PoweringUp' --> 'Up'" is written to engine.log, and the events EVENT_ID: USER_STARTED_VM and EVENT_ID: USER_RUN_VM is created. -- 2019-05-08 20:53:20,976+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1388598) [xxxxxxxx-da2d-452d-a604-xxxxxxxxxxxx] EVENT_ID: USER_STARTED_VM(153), VM vmname1 was started by adminuser@ipadomain (Host: hypervisor1). 2019-05-08 20:53:24,091+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'WaitForLaunch' --> 'PoweringUp' 2019-05-08 20:53:45,140+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'PoweringUp' --> 'Up' 2019-05-08 20:53:45,238+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: USER_RUN_VM(32), VM vmname1 started on Host hypervisor1 -- However when a user reboots a VM from within the VM operating system, the messages "moved from 'Up' --> 'RebootInProgress'" and "moved from 'RebootInProgress' --> 'Up'" is written to the engine.log, but no EVENT_ID is generated. -- -- 2019-05-08 20:52:27,367+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'RebootInProgress' 2019-05-08 20:52:49,926+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'RebootInProgress' --> 'Up' -- So systems like CloudForms/ManageIQ which reads the manager event log via the manager REST API is not notified when a VM is rebooted, and is therefore unable to perform any EmsEvent when the VM reboots. Why is there no EVENT_ID generated when a VM reboots? Is it possible to enable EVENT_ID's to be created for VM reboot events? Regards, Siggi

1 0

[Urgent] USB passthrough
by Juan Pablo Lorier 08 May '19

08 May '19

Hi, I'm trying to attach an USB device to a VM but although the host detects the USB device (is shown in lsusb), the host device tab in the VM is not showing that device. It show all other but not that one. Is there something I should do to update ovrit host devices? Regards

1 0

Re: Creating Thin-provisioned disks on a gluster volume
by Strahil 08 May '19

08 May '19

I have already opened a bug for that. If you are not in a hurry - postpone the migration. Best Regards, Strahil NikolovOn May 8, 2019 00:49, Dmitry Filonov <filonov(a)hkl.hms.harvard.edu> wrote: > > Hi - > We want to migrate our aging oVirt cluster to a new one and decided to go for the hyperconverged setup with Gluster and hosted engine. Got 3 new machines, set everything up, did a test VM migration and were almost ready to do final migration of our VMs when I notice one really weird thing. > When migrating VMs from NFS storage onto Gluster they stay thin provisioned. But if I try creating new disk image from the oVirt GUI - I get preallocated volume. No matter if I select "thin provision" or "Preallocated" I always get preallocated volume created. > > The engine.log says - > 2019-05-07 17:14:20,562-04 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default task-20) [bbd94792-2f86-44eb-9334-807dd44d0742] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{storagePoolId='43550c2c-7100-11e9-9b45-00163e4babb7', ignoreFailoverLimit='false', storageDomainId='1de2f7ac-ee52-43fb-89ac-f86b62f73b9a', imageGroupId='86c5c5e9-6533-4caf-a5a5-401556a5059a', imageSizeInBytes='21474836480', volumeFormat='RAW', newImageId='470b8035-9380-408d-a644-96e8d74c4e8e', imageType='Preallocated', newImageDescription='{"DiskAlias":"test","DiskDescription":""}', imageInitialSizeInBytes='0'}), log id: 228ddfd5 > > Is there any tweak I didn't notice to make things actually what it suppose to be doing? > > oVirt 4.3.3.5-1.el7 > glusterfs 5.5-1.el7 > CentOS Linux release 7.6.1810 > > Thank you! > > -- > Dmitry Filonov > Linux Administrator > SBGrid Core | Harvard Medical School > 250 Longwood Ave, SGM-114 > Boston, MA 02115

1 0

Best arquitecture for 2 location
by raul.caballero.girol＠gmail.com 08 May '19

08 May '19

Hi everybody, I have 2 location separate geographically. I want to deploy an ovirt installation. Evary location has 3 host with a storage system. What is the best arquitecture for this scenario?. My problem is that I don know how to recover the manager if its storage is down. With a backup/recover? How I remove the old manager when I recover the storage? Cheers

2 4

Creating Thin-provisioned disks on a gluster volume
by Dmitry Filonov 08 May '19

08 May '19

Hi - We want to migrate our aging oVirt cluster to a new one and decided to go for the hyperconverged setup with Gluster and hosted engine. Got 3 new machines, set everything up, did a test VM migration and were almost ready to do final migration of our VMs when I notice one really weird thing. When migrating VMs from NFS storage onto Gluster they stay thin provisioned. But if I try creating new disk image from the oVirt GUI - I get preallocated volume. No matter if I select "thin provision" or "Preallocated" I always get preallocated volume created. The engine.log says - 2019-05-07 17:14:20,562-04 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (default task-20) [bbd94792-2f86-44eb-9334-807dd44d0742] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{storagePoolId='43550c2c-7100-11e9-9b45-00163e4babb7', ignoreFailoverLimit='false', storageDomainId='1de2f7ac-ee52-43fb-89ac-f86b62f73b9a', imageGroupId='86c5c5e9-6533-4caf-a5a5-401556a5059a', imageSizeInBytes='21474836480', volumeFormat='RAW', newImageId='470b8035-9380-408d-a644-96e8d74c4e8e',* imageType='Preallocated', *newImageDescription='{"DiskAlias":"test","DiskDescription":""}', imageInitialSizeInBytes='0'}), log id: 228ddfd5 Is there any tweak I didn't notice to make things actually what it suppose to be doing? oVirt 4.3.3.5-1.el7 glusterfs 5.5-1.el7 CentOS Linux release 7.6.1810 Thank you! -- Dmitry Filonov Linux Administrator SBGrid Core | Harvard Medical School 250 Longwood Ave, SGM-114 Boston, MA 02115

2 2

Hosted engine restore went very wrong
by Andreas Elvers 07 May '19

07 May '19

I really feel like an idiot. I tried to move our hosted engine from our Default datacenter to our Ceph Datacenter. I ran intro problems which were correctly addressed. see: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/ZFCLFWRN6XR6KM… It was in case a race condition. I was able to bring back the engine to our Default Cluster. And then I tried to do the move again to our Ceph Datacenter. I got the error "The target Data Center does not contain the Virtual Disk" twice yesterday. Because it was late, I decided to do it in the next morning. I did a new backup from the engine. Copied it over to the new node of the Ceph Datacenter and started the hosted-engine --deploy. But I FORGET TO SHUTDOWN the other engine! Oh man. The deploy script errored out with: [ ERROR ] fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} [ ERROR ] fatal: [localhost -> engine.infra.solutions.work]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned accord Then I realised something was different this time. I shutdown and undefined the Local Engine. The node is now in a degraded state. Is it possible to start the deployment again on a degraded node? I started the old engine again, but I'm not able to reach the login page. Any Idea what to do next?

1 5

Re: All Windows vms report "Actual timezone in guest doesn't match configuration"
by michael＠wanderingmad.com 07 May '19

07 May '19

I got my questions mixed up, restarting guest services does nothing.

6 9