Description of problem: Unable to add new (first) disk to VM with error [1] Version-Release number of selected component (if applicable): ovirt-engine-4.0.4.3-0.1.el7ev.noarch How reproducible: Unknown. Happened once Steps to Reproduce: 1. Remove VM's disk 2. Add new disk to VM. Thin-provisioned, bootable Actual results: Unable to add new disk Expected results: Disk added Additional info: [1] Error while executing action: ge-ci-engine05.ci.lab.tlv.redhat.com: Cannot add Virtual Disk. Cannot find a disk profile defined on storage domain ${$storageDomainId}. [2] 2016-09-26 15:01:36,123 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-112) [5e5b1818] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f87cd3b7-bd5c-4a65-8b53-0544196afa79=<VM_DISK_BOOT, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[f87cd3b7-bd5c-4a65-8b53-0544196afa79=<VM, ACTION_TYPE_FAILED_OBJECT_LOCKED>]'}' 2016-09-26 15:01:37,358 WARN [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-112) [5e5b1818] Validation of action 'AddDisk' failed for user pzhukov. Reasons: VAR__ACTION__ADD,VAR__TYPE__DISK,ACTION_TYPE_DISK_PROFILE_NOT_FOUND_FOR_STORAGE_DOMAIN,$storageDomainId c05f309b-5460-4971-8dc2-758d8dfd6ea9 2016-09-26 15:01:37,359 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-112) [5e5b1818] Lock freed to object 'EngineLock:{exclusiveLocks='[f87cd3b7-bd5c-4a65-8b53-0544196afa79=<VM_DISK_BOOT, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='[f87cd3b7-bd5c-4a65-8b53-0544196afa79=<VM, ACTION_TYPE_FAILED_OBJECT_LOCKED>]'}'
Yanir, is it a dup of bug 1361838?
The VM was created using python SDK. So looks duplicate. Thanks Tal! *** This bug has been marked as a duplicate of bug 1361838 ***
Reopened. I've recreated the VM manualy and got same error again.
Pavel, note that the fix was in 4.0.4.4 so if you are still running on 4.0.4.3 it will still occur manually or not. Yanir, your thoughts?
(In reply to Tal Nisan from comment #4) > Pavel, note that the fix was in 4.0.4.4 so if you are still running on > 4.0.4.3 it will still occur manually or not. > Yanir, your thoughts? that's correct. this issue will not occur from 4.0.4.4 onwards
*** This bug has been marked as a duplicate of bug 1361838 ***
(In reply to Yanir from comment #5) > (In reply to Tal Nisan from comment #4) > > Pavel, note that the fix was in 4.0.4.4 so if you are still running on > > 4.0.4.3 it will still occur manually or not. > > Yanir, your thoughts? > > that's correct. this issue will not occur from 4.0.4.4 onwards Original BZ says https://bugzilla.redhat.com/show_bug.cgi?id=1361838#c8 it's related to templates/REST API We have issue with newly created VM without any templates/API involved at all. Create _new_ VM -> Create _new_ disk -> Failed. Why do you think it's same issue?
(In reply to Pavel Zhukov from comment #7) > (In reply to Yanir from comment #5) > > (In reply to Tal Nisan from comment #4) > > > Pavel, note that the fix was in 4.0.4.4 so if you are still running on > > > 4.0.4.3 it will still occur manually or not. > > > Yanir, your thoughts? > > > > that's correct. this issue will not occur from 4.0.4.4 onwards > > Original BZ says https://bugzilla.redhat.com/show_bug.cgi?id=1361838#c8 it's > related to templates/REST API > We have issue with newly created VM without any templates/API involved at > all. > Create _new_ VM -> Create _new_ disk -> Failed. > Why do you think it's same issue? this issue was an outcome of the original fix which had several cycles. the resulting issues that appeared in 4.0.4.3 were fixed in 4.0.4.4 build