Description of problem: vdsm should be able to monitor domains also when not connected to a pool. E.g.: startMonitoringDomain() should be added for monitoring a storage domain without being connected to the pool and getting and ID for such SD lockspace. stopMonitoringDomain() should stops the monitoring and releases the ID. Monitoring results could be gathered with repoStats().
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Is it only for hosted engine? How can I reach this state from the UI? What are the reproduction steps?
Verified on IS29: [root@master-vds13 ~]# vdsClient -s 0 getStorageDomainsList 12bfef7f-15bc-4196-9cb4-1b09b211f5a4 65027b13-6b68-4d0e-a048-e003b10c2b22 3b2e987b-aa57-4713-832a-2c57bbf29204 [root@master-vds13 ~]# vdsClient -s 0 getConnectedStoragePoolsList [root@master-vds13 ~]# vdsClient -s 0 repoStats [root@master-vds13 ~]# vdsClient -s 0 getConnectedStoragePoolsList [root@master-vds13 ~]# vdsClient -s 0 startMonitoringDomain 65027b13-6b68-4d0e-a048-e003b10c2b22 9 OK [root@master-vds13 ~]# vdsClient -s 0 repoStats Domain 65027b13-6b68-4d0e-a048-e003b10c2b22 {'code': 0, 'version': 3, 'acquired': False, 'delay': '0.000752342', 'lastCheck': '4.0', 'valid': True} [root@master-vds13 ~]# vdsClient -s 0 getConnectedStoragePoolsList [root@master-vds13 ~]# vdsClient -s 0 stopMonitoringDomain 65027b13-6b68-4d0e-a048-e003b10c2b22 OK [root@master-vds13 ~]# vdsClient -s 0 repoStats [root@master-vds13 ~]# vdsClient -s 0 getConnectedStoragePoolsList
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0040.html