Description of problem: When creating a Storage Domain, the available disk size is set to null, to be polled later on. When Adding a disk on a newly created domain, CDA fails on storage allocations - StorageDomainValidator.isDomainWithinThresholds. This happens since the null value is interpreted as 0 in StorageDomainDynamic.getfreeDiskInGB() . Revise when this interpretation is correct and handle when it's not (isDomainWithinThresholds, at least). Steps to Reproduce: 1. Create a new Storage Domain 2. Immediately add a disk. 3. Actual results: CDA failure - ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN . Expected results: Pass (or fail on execution due to actual lack of space, which is not the interesting case here to verify).
this ovirt bug was fixed during 3.5.1 cycle and is included in the build, and therefore should be verified.
*** Bug 1202363 has been marked as a duplicate of this bug. ***
We've encountered this issue in 3.5.1 (vt14) in automation. What is the solution implemented for this? The disk creation should fail? With what message? Right now adding a vm fails with: 'Cannot add VM. Low disk space on Storage Domain iscsi_2.'
> What is the solution implemented for this? The disk creation should fail? No, disk creation should succeed. > With what message? Right now adding a vm fails with: > > 'Cannot add VM. Low disk space on Storage Domain iscsi_2.' This is not the desired behaviour. I've verified the patch is indeed in vt14, yet I can't reproduce. For me, disk creation completes under these conditions. Please explain exactly how you reproduced, and attach logs.
Sorry Vered, I saw this issue in the previous build, not this one.
So can we try to reproduce with this build, and if we can't, move this BZ to VERIFIED?
need to verify, no needinfo needed here.
Just to clarify, my comment 3 was refering to activating the storage domain in vt14, bug 1202363. Vered reopened because that case is different from this one (different flow according to the bug description). I haven't try to verify this case, I'll do it and mark is as VERIFIED in case I can't reproduce.
(In reply to Carlos Mestre González from comment #8) > Just to clarify, my comment 3 was refering to activating the storage domain > in vt14, bug 1202363. Vered reopened because that case is different from > this one (different flow according to the bug description). > > I haven't try to verify this case, I'll do it and mark is as VERIFIED in > case I can't reproduce. Thanks for the clarification - I misunderstood that.
I have executed this scenario twice, first time before domain's creation, operation has failed because of the storage domain status was still "lock": "Cannot add Virtual Machine Disk. The relevant Storage Domain's status is Locked." Second time, right after Domain creation, on the second time the operation was successful. seems it should be verified, Carlos do you have any comments before I'm verifying this?
Carlos, has reached the same results as me via manual testing thus, verified on vt14.1
ovirt 3.5.2 was GA'd. closing current release.