Created attachment 1002274 [details] engine log Description of problem: When activating a storage domain, for a few seconds it's size and available size are not available and that's considerd as "Low disk space on Storage Domain" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. activate storage domain 2. look at it's size and available size 3. Actual results: size and available size are [N/A] Expected results: Additional info: In the engine.log attached search for "2015-03-14 02:46:13"
Regarding the actual results: Rest API doesn't return available/used properties (only committed) for the storage domain. This is an issue since in automation because the scenario of activating the storage domain and immediately after the this storage domain is 'Active', create a vm/disk, this action will fail with: -> Cannot add VM. Low disk space on Storage Domain iscsi_2. even though the domain is active.
How reproducible: 10% ? This happens to certain luns and not others (from the same storage server group), but I don't see any difference. This is a setup that has being up running for weeks different tests amount of tests, I'm not sure is that has to do with anything (some corruption?).
Created attachment 1002828 [details] vdsm.log This setup contains 3 nfs domains and 3 iscsi domains (nfs_X and iscsi_x). From 2015-03-17 15:51:37 the test starts, deactivating the master domain and activating again (iscsi_2). For ~ ten seconds afer the domains is 'active' the available size and used size properties in rest API (N/A Webui) are missing (15:52:27 -> 15:52:38)
There are three separate issues here: 1. The domain's size being reported as unknown (null) until domain monitoring is run. This issue has been in place since RHEVM 3.0, at least, and frankly, it's not worth the effort to fix. It would require an extensive overhauling to the domain monitoring, for a really small gain, as the issue self corrects in a few minutes. 2. The fact you cannot create a disk until the size is updated. This issue has already been addressed in oVirt 3.5.2 (see bug 1177147), which RHEV 3.5.1 was rebased on. According to the report, this bug reproduced in 3.5.0, which is expected. If it also reproduces in the latest build of 3.5.1, please set bug 1177147 as Failed QA. 3. The fact that a warning is issues while the domain's size is not updated. This too was handled in bug 1177147. I'm closing this bug as a duplicate. *** This bug has been marked as a duplicate of bug 1177147 ***
(In reply to Allon Mureinik from comment #4) > There are three separate issues here: > > 1. The domain's size being reported as unknown (null) until domain > monitoring is run. This issue has been in place since RHEVM 3.0, at least, > and frankly, it's not worth the effort to fix. It would require an extensive > overhauling to the domain monitoring, for a really small gain, as the issue > self corrects in a few minutes. > > 2. The fact you cannot create a disk until the size is updated. This issue > has already been addressed in oVirt 3.5.2 (see bug 1177147), which RHEV > 3.5.1 was rebased on. According to the report, this bug reproduced in 3.5.0, > which is expected. If it also reproduces in the latest build of 3.5.1, > please set bug 1177147 as Failed QA. > > 3. The fact that a warning is issues while the domain's size is not updated. > This too was handled in bug 1177147. > > I'm closing this bug as a duplicate. > > *** This bug has been marked as a duplicate of bug 1177147 *** bz1177147 fixed the problematic flow in creating a new domain. This looks like a different flow concerning activating a domain, reopening in order to handle issue no.2 .
Carlos, regarding bz1177147#8, does this mean this flow was verified without the patch as well?
This issue is still happening in vt14.
Carlos, We have no issue with not showing available size and used size properties in rest API. This is the desired behaviour in this case. Not be able to add disks in this scenario is indeed an issue. Our fix to this will cause the above properties not be displayed in more scenarios (all concerning connectivity to domains). Would you like to run your automation test with the patch before we're merging it?
The issue indeed is not being able to create disks even though the storage domain is active. Could you clarify what scenarios are those when it will not be displayed? We're not going to have much problems in automation test, only for those test that indeed check those values, but we can always wait for the engine to report them.
(In reply to Carlos Mestre González from comment #9) > Could you clarify what scenarios are those when it will not be displayed? 1. Right after creating a new storage domain, for several seconds until the values are polled. 2. After recovery from connectivity issues or activation of a domain.
The patch that aims to fix this issue is built and is closely coupled with two other patches, touching the same areas, and is not complete without them. Adding them to external trackers.
Vered, can you add the doctext for this bz please?
Copied doctext from the zstream clone (bug #1211057).
Verified on 3.6.0.3
RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE