You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two bugs in current testAccCheckDiskAttachmentDestroy function:
It's using rs.Primary.ID as the disk ID to fetch a disk through oVirt engine API. But in this case, the rs.Primary.ID is combined with vmID and diskID, in the format of df736600-b8be-4029-be98-4b0611be6be4:5bd12e84-025a-0171-03aa-0000000003d6, so the code logic will always treat this resource as already removed, regardless of whether it exists in reality.
Actually, the destroy of a disk attachment indicates it has been detached from a VM and the relevant disk probably still exist in oVirt. While current code uses the result of the existence of the disk and it will surely be incorrect.
The text was updated successfully, but these errors were encountered:
There are two bugs in current
testAccCheckDiskAttachmentDestroy
function:rs.Primary.ID
as the disk ID to fetch a disk through oVirt engine API. But in this case, thers.Primary.ID
is combined with vmID and diskID, in the format ofdf736600-b8be-4029-be98-4b0611be6be4:5bd12e84-025a-0171-03aa-0000000003d6
, so the code logic will always treat this resource as already removed, regardless of whether it exists in reality.The text was updated successfully, but these errors were encountered: