[ovirt-users] Re: 4.2.8: NPE starting a specific VM
There was a NIC that was Up + Unplugged. I have removed all NICs and recreated them. The NPE remains. On Sat, Jul 6, 2019 at 10:00 PM Arik Hadas wrote: > On Fri, Jul 5, 2019 at 7:44 PM Richard Chan > wrote: > >> This VM and interface cause NPE >> >> id | vm_guid >>| vmt_guid | mac_addr | name | speed | type | >> _create_date | _update_date | linked | >> vnic_profile_id >> >> --+--+--+---+--+---+--+---+---++-- >> 29c09fc1-1ddf-40e1-8355-1acbdd84f913 | >> cb5dee7e-5bc6-4eb3-88a9-614a90ebfd71 | | 00:1a:4a:2f:48:83 | nic1 >> | 1 |3 | 2017-04-26 23:31:58.662743+08 | 2019-07-06 >> 00:35:27.401616+08 | t | 0f1c7d97-a156-416c-a62a-ed7d5bc3dc0e >> (1 row) >> >> On Fri, Jul 5, 2019 at 7:03 PM Dominik Holler wrote: >> >>> Can you please share the output of >>> /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select * from >>> vm_interface" >>> ? You are welcme to restrict like >>> /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select * from >>> vm_interface where vm_guid='xxx' " >>> if you know the id of the vm. >>> >>> >>> On Fri, Jul 5, 2019 at 9:46 AM Richard Chan < >>> rich...@treeboxsolutions.com> wrote: >>> Encountering a NPE on 4.2.8. This is the first start after a 4.1 to 4.2 upgrade. 2019-07-05 15:36:56,912+08 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-45700) [64500cdd-b623-4bb1-a7a1-841 6b4e6723b] Failed to create VM: java.lang.NullPointerException at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$26(LibvirtVmXmlBuilder.java:1198) [vdsbroker.jar:] at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469) [rt.jar:1.8.0_212] at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355) [rt.jar:1.8.0_212] at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_212] at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_212] at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348) [rt.jar:1.8.0_212] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483) [rt.jar:1.8.0_212] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) [rt.jar:1.8.0_212] at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) [rt.jar:1.8.0_212] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) [rt.jar:1.8.0_212] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) [rt.jar:1.8.0_212] at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) [rt.jar:1.8.0_212] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeInterfaces(LibvirtVmXmlBuilder.java:1199) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.writeDevices(LibvirtVmXmlBuilder.java:1045) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.buildCreateVm(LibvirtVmXmlBuilder.java:254) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.generateDomainXml(CreateBrokerVDSCommand.java:93) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.createInfo(CreateBrokerVDSCommand.java:50) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand.executeVdsBrokerCommand(CreateBrokerVDSCommand.java:42) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] This leads to Failed to run VM message. Any ideas? >>> > Looks similar to [1]. > Could you please check in the VM-devices tab of the VM if there are > unmanaged+plugged NICs and managed+unplugged NICs? > > [1] https://lists.ovirt.org/pipermail/users/2018-March/087481.html > > >> Thanks
[ovirt-users] Re: UI - cannot remove disk whiel system is running
Everything ended well - despite the warning 'do not shutdown' I powered off and powered on the VM. This action allowed me to trigger a snapshot deletion (again) and it completed successfully. Removing the disk of interest also completed successfully. So, I got a happy ending. Best Regards, Strahil NikolovOn Jul 7, 2019 17:41, Strahil wrote: > > I think I'm getting closer. > > It seems the snapshot of the VM did not get deleted and that might be the > problem. > > Can someone give me a hint how to remove the snapshot as I get an error: > > Cannot remove Snapshot. The following disks are in ILLEGAL status: > uyuni-OS-Disk1 - please remove them and try again. > > Yet, removal of the disk cannot happen as I got: > Cannot detach Virtual Disk. The disk is already configured in a snapshot. In > order to detach it, remove the disk's snapshot. > > This seems like 'Catch 22' . > > Best Regards, > Strahil Nikolov > > On Jul 7, 2019 17:30, Strahil wrote: >> >> Hello All, >> >> I have changed my system layout and the old disk is removed (echo 1 > >> /sys/block/sdX/device/delete) from OS, but UI complains when I try to >> remove with the following error: >> >> Error while executing action: Cannot remove Virtual Disk. At least one of >> the VMs is not down. >> >> Is it a limitation of oVirt ? If so, I will open an enhancement entry in >> bugzilla. >> >> As far as I remember KVM allowed me to make such stuff without any issues >> so far. >> >> Best Regards, >> Strahil Nikolov___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/6QMYQVH4NWKXSYY67DEHLNT3OPHAA353/
[ovirt-users] Re: UI - cannot remove disk whiel system is running
I think I'm getting closer. It seems the snapshot of the VM did not get deleted and that might be the problem. Can someone give me a hint how to remove the snapshot as I get an error: Cannot remove Snapshot. The following disks are in ILLEGAL status: uyuni-OS-Disk1 - please remove them and try again. Yet, removal of the disk cannot happen as I got: Cannot detach Virtual Disk. The disk is already configured in a snapshot. In order to detach it, remove the disk's snapshot. This seems like 'Catch 22' . Best Regards, Strahil NikolovOn Jul 7, 2019 17:30, Strahil wrote: > > Hello All, > > I have changed my system layout and the old disk is removed (echo 1 > > /sys/block/sdX/device/delete) from OS, but UI complains when I try to remove > with the following error: > > Error while executing action: Cannot remove Virtual Disk. At least one of > the VMs is not down. > > Is it a limitation of oVirt ? If so, I will open an enhancement entry in > bugzilla. > > As far as I remember KVM allowed me to make such stuff without any issues > so far. > > Best Regards, > Strahil Nikolov___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/JTDRR2Y3655K67BYEFDHAUXL24QI4OAJ/
[ovirt-users] UI - cannot remove disk whiel system is running
Hello All, I have changed my system layout and the old disk is removed (echo 1 > /sys/block/sdX/device/delete) from OS, but UI complains when I try to remove with the following error: Error while executing action: Cannot remove Virtual Disk. At least one of the VMs is not down. Is it a limitation of oVirt ? If so, I will open an enhancement entry in bugzilla. As far as I remember KVM allowed me to make such stuff without any issues so far. Best Regards, Strahil Nikolov___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/OM5E3JTIPPN3B6YU6LLPTYAVDQXRXNUW/
[ovirt-users] Re: VM snapshot - some info needed
On Wed, Jul 3, 2019 at 8:11 PM Strahil Nikolov wrote: > I have noticed that if I want a VM snapshot with memory - I get a warning "The > VM will be paused while saving the memory" . > Is there a way to make snapshot without pausing the VM for the whole > duration ? > No, this is expected. Denis was working on background snapshot which will remove this limitation: https://www.youtube.com/watch?v=fKj4j8lw8pU Nir > I have noticed that it doesn't matter if VM has qemu-guest-agent or > ovirt-guest-agent. > > Thanks in advance for sharing your thoughts. > > Best Regards, > Strahil Nikolov > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/users@ovirt.org/message/7VFMZRGF57WXTFTZ44W55MDX6BJES5TX/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/GFG47UKCGCNP5R2P7RDSNY5X2KTIUCZG/
[ovirt-users] Re: Experience 4.1.x -> 4.2.8 -> 4.3.4 upgrade lessons
On Sat, Jul 6, 2019 at 4:58 AM Richard Chan wrote: > Hi oVirters, > > Did a 4.1 - > 4.2.8 -> 4.3.4 upgrade in two hops. Here is my experience, > hope it can save you some pain. > > Gotchas > 1. For shutdown VMs, their disks were deactivated (though still attached) > 2. For shutdown VMs, their NICs were "Up" but "Unplugged" > 3. VM Custom Compatibility Version is hard to find. (If it is too old say > 3.6, 4.1) they won't start up. The location is: VM -> Edit -> System -> > Advanced Parameters (click this) > > "Advanced Parameters" is an expandable widget that is quite small when > collapsed. When it is expanded then you will see "Custom Compatibility > Version" > > 4. Storage Domain migration to V5: I use a NFS storoage domain. This is > migrated to the "V5" format and a lot of cleanup is done. If you have stray > files or images not owned by 36:36 (vdsm:kvm on my NFS server), the V5 > upgrade will fail, there will be no SPM, and the Data Center will oscillate > between Non-responsive and Contending. > > Why would there be non 36:36 uid/gid files? This is a long story, but from > the older 3.x days when there was less functionality, we would sometimes > directly manipulate the filesystem and/or qcow2 images using guestfish or > equivalent tools which would change the owner to qemu:qemu. Forgetting to > chown back to vdsm:kvm is a recipe for pain. > Bad permission are expected to cause failures when converting a domain, since we need to modify domain and volumes metadata. This will also cause failures to use volumes or in some other storage operations. Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/WAC4OPM73HWACWVHWZQOPX7RUWOWPJHK/
[ovirt-users] Re: Upgraded to 4.3: getting SpmStart failure
On Fri, Jul 5, 2019 at 6:45 PM Richard Chan wrote: > Unfortunately, this is a separate engine running external to the oVirt > cluster. > The main error on the hosts is: any idea what this Volume is referring to? > I have 3 existings storage domains > ISO EXPORT and DATA all upgraded to 4.3 > None have this UUID. > > > VolumeDoesNotExist: Volume does not exist: > (u'1d1b6dfd-197a-4583-8398-6b941dbca854',) > > 2019-07-05 23:02:15,954+0800 ERROR (tasks/0) [storage.StoragePool] failed: > Volume does not exist: (u'1d1b6dfd-197a-4583-8398-6b941dbca854',) (sp:384) > 2019-07-05 23:02:15,954+0800 INFO (tasks/0) [storage.SANLock] Releasing > Lease(name='SDM', > path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases', > offset=1048576) (clusterlock:488) > 2019-07-05 23:02:15,955+0800 INFO (tasks/0) [storage.SANLock] > Successfully released Lease(name='SDM', > path=u'/rhev/data-center/mnt/192.168.88.40:_genie_ovirt_data/f9aaa65a-0ac7-4c61-a27d-15af39016419/dom_md/leases', > offset=1048576) (clusterlock:497) > 2019-07-05 23:02:15,955+0800 ERROR (tasks/0) [storage.TaskManager.Task] > (Task='159b9026-7034-43c2-9587-8fec036e92ba') Unexpected error (task:875) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, > in _run > return fn(*args, **kargs) > File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, > in run > return self.cmd(*self.argslist, **self.argsdict) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 333, in > startSpm > self._upgradePool(expectedDomVersion, __securityOverride=True) > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line > 79, in wrapper > return method(self, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 484, in > _upgradePool > str(targetDomVersion)) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1108, > in _convertDomain > targetFormat) > File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py", > line 447, in convert > converter(repoPath, hostId, imageRepo, isMsd) > File "/usr/lib/python2.7/site-packages/vdsm/storage/formatconverter.py", > line 405, in v5DomainConverter > domain.convert_volumes_metadata(target_version) > File "/usr/lib/python2.7/site-packages/vdsm/storage/fileSD.py", line > 813, in convert_volumes_metadata > for vol in self.iter_volumes(): > File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 764, in > iter_volumes > yield self.produceVolume(img_id, vol_id) > File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 846, in > produceVolume > volUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line > 817, in __init__ > self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID, volUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line > 71, in __init__ > volUUID) > File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 86, > in __init__ > self.validate() > File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line > 112, in validate > self.validateVolumePath() > File "/usr/lib/python2.7/site-packages/vdsm/storage/fileVolume.py", line > 131, in validateVolumePath > raise se.VolumeDoesNotExist(self.volUUID) > This usually means the volume does not have the right permissions. 130 if not self.oop.fileUtils.pathExists(volPath): 131 raise se.VolumeDoesNotExist(self.volUUID) oop.fileUtils.pathExists() is: 130 if not self.oop.fileUtils.pathExists(volPath): 131 raise se.VolumeDoesNotExist(self.volUUID) IOProcess.pathExists() is: 482 def pathExists(self, filename, writable=False): 483 check = os.R_OK 484 485 if writable: 486 check |= os.W_OK 487 488 if self.access(filename, check): 489 return True 490 491 return self.access(filename, check) Bad permissions would fail converting a domain of course, so this real fix is to fix the bad permissions. Nir > > On Fri, Jul 5, 2019 at 11:31 PM Strahil wrote: > >> Can you run the engine manually on another server ? >> hosted-engine --vm-start >> >> Best Regards, >> Strahil Nikolov >> On Jul 5, 2019 18:05, Richard Chan wrote: >> >> My engine is getting SpmStart failure. >> >> What is the best way to troubleshoot this? >> >> >> -- >> Richard Chan >> >> > > -- > Richard Chan > Chief Architect > > TreeBox Solutions Pte Ltd > 1 Commonwealth Lane #03-01 > Singapore 149544 > Tel: 6570 3725 > http://www.treeboxsolutions.com > > Co.Reg.No. 201100585R > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: >
[ovirt-users] Re: Can't unsubscribe myself from here
Try this: https://lists.ovirt.org/admin/lists/users.ovirt.org/ HTH /tony On Thu, 2019-07-04 at 06:07 +, csi-la...@cisco.com wrote: > Hi, > I sent a mail in order to unsubsribe my mailer team "csi-laser@cisco. > com", and I'm still getting e-mails. > I already sent mails to "'users-le...@ovirt.org' > > > Who should I talk more in order it'll stop ?? > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/communit > y-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/ > message/46LBDXVX2W4TCIRL2DYXX5DSO7R34GZS/ -- Tony Albers - Systems Architect - IT Development Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142 ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/users@ovirt.org/message/MJ3R5DGR537GCDR5Y4YRWPMNNUDZQY5P/
[ovirt-users] Re: Managed Block Storage
Hi, Any chance you can setup gdb[1] so we can find out where it's stuck exactly? Also, which version of ovirt are you using? Can you also check the ceph logs for anything suspicious? [1] - https://wiki.python.org/moin/DebuggingWithGdb $ gdb python then `py-bt` On Thu, Jul 4, 2019 at 7:00 PM wrote: > > Can you provide logs? mainly engine.log and cinderlib.log > > (/var/log/ovirt-engine/cinderlib/cinderlib.log > > > If I create two volumes, the first one succeeds successfully, the second > one hangs. If I look in the processlist after creating the second volume > which doesn't succceed, I see the python ./cinderlib-client.py > create_volume [...] command still running. > > On the ceph side, I can see only the one rbd volume. > > Logs below: > > > > --- cinderlib.log -- > > 2019-07-04 16:46:30,863 - cinderlib-client - INFO - Fetch backend stats > [b07698bb-1688-472f-841b-70a9d52a250d] > 2019-07-04 16:46:56,308 - cinderlib-client - INFO - Creating volume > '236285cc-ac01-4239-821c-4beadd66923f', with size '2' GB > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] > 2019-07-04 16:47:21,671 - cinderlib-client - INFO - Creating volume > '84886485-554a-44ca-964c-9758b4a16aae', with size '2' GB > [a793bfc9-fc37-4711-a144-d74c100cc75b] > > --- engine.log --- > > 2019-07-04 16:46:54,062+01 INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-22) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] Running command: AddDiskCommand > internal: false. Entities affected : ID: > 31536d80-ff45-496b-9820-15441d505924 Type: StorageAction group CREATE_DISK > with role type USER > 2019-07-04 16:46:54,150+01 INFO > [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-1) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] Running command: > AddManagedBlockStorageDiskCommand internal: true. > 2019-07-04 16:46:56,863+01 INFO > [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] > (EE-ManagedThreadFactory-commandCoordinator-Thread-1) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] cinderlib output: > 2019-07-04 16:46:56,912+01 INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-22) [] EVENT_ID: USER_ADD_DISK_FINISHED_SUCCESS(2,021), The > disk 'test0' was successfully added. > 2019-07-04 16:47:00,126+01 INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-95) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] Command 'AddDisk' id: > '15fe157d-7adb-4031-9e81-f51aa0b6528f' child commands > '[d056397a-7ed9-4c01-b880-dd518421a2c6]' executions were completed, status > 'SUCCEEDED' > 2019-07-04 16:47:01,136+01 INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-99) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] Ending command > 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' successfully. > 2019-07-04 16:47:01,141+01 INFO > [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-99) > [0b0f0d6f-cb20-440a-bacb-7f5ead2b4b4d] Ending command > 'org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand' > successfully. > 2019-07-04 16:47:01,145+01 WARN > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-99) [] VM is null - no > unlocking > 2019-07-04 16:47:01,186+01 INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-99) [] EVENT_ID: > USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'test0' was successfully > added. > 2019-07-04 16:47:19,446+01 INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-22) > [a793bfc9-fc37-4711-a144-d74c100cc75b] Running command: AddDiskCommand > internal: false. Entities affected : ID: > 31536d80-ff45-496b-9820-15441d505924 Type: StorageAction group CREATE_DISK > with role type USER > 2019-07-04 16:47:19,464+01 INFO > [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-2) > [a793bfc9-fc37-4711-a144-d74c100cc75b] Running command: > AddManagedBlockStorageDiskCommand internal: true. > 2019-07-04 16:48:19,501+01 INFO > [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] > (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool > 'commandCoordinator' is using 1 threads out of 10, 1 threads waiting for > tasks. > 2019-07-04 16:48:19,501+01 INFO > [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] > (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool > 'default' is using 0 threads out of 1, 5 threads waiting for tasks. > 2019-07-04 16:48:19,501+01 INFO > [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >
