Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 951057 - vdsm should report the storage domain version in the statistics
vdsm should report the storage domain version in the statistics
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
3.2.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.2.0
Assigned To: Federico Simoncelli
Dafna Ron
storage
:
Depends On:
Blocks: 948448
  Show dependency treegraph
 
Reported: 2013-04-11 07:44 EDT by Federico Simoncelli
Modified: 2016-02-10 15:53 EST (History)
9 users (show)

See Also:
Fixed In Version: vdsm-4.10.2-18.0.el6ev
Doc Type: Bug Fix
Doc Text:
Previously, VDSM did not report the storage domain in the domain statistics. This made it impossible for the backend to monitor the storage domains version during upgrades. VDSM now reports the storage domain in the domain statistics.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-06-10 16:48:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 13620 None None None Never
Red Hat Product Errata RHSA-2013:0886 normal SHIPPED_LIVE Moderate: rhev 3.2 - vdsm security and bug fix update 2013-06-10 20:25:02 EDT

  None (edit)
Description Federico Simoncelli 2013-04-11 07:44:29 EDT
Description of problem:
In order to allow the backend to monitor the storage domains version during the upgrade (for all the non-master domains) VDSM should report this information in the domain statistics.

Version-Release number of selected component (if applicable):
vdsm-4.10.2-15.0.el6ev

How reproducible:
100%

Steps to Reproduce:
1. vdsClient 0 getVdsStats
2. vdsClient 0 getStoragePoolInfo <spUUID>
  
Actual results:
No domain version is reported:

# vdsClient 0 getVdsStats
[...]
storageDomains = {'5db46280-a002-4d4e-b5cf-59533f9aa36d':
   {'code': 0, 'delay': '0.0156488418579', 'lastCheck': '8.9', 'valid': True}
[...]

# vdsClient 0 getStoragePoolInfo <spUUID>
[...]
5db46280-a002-4d4e-b5cf-59533f9aa36d = {'status': 'Active', 'diskfree': '15837691904', 'alerts': [], 'disktotal': '21072183296'}
[...]

Expected results:
The domain version should be reported:

# vdsClient 0 getVdsStats
[...]
storageDomains = {'5db46280-a002-4d4e-b5cf-59533f9aa36d':
   {'code': 0, 'delay': '0.0156488418579', 'lastCheck': '8.9', 'valid': True, 'version': 3}
[...]

# vdsClient 0 getStoragePoolInfo <spUUID>
[...]
5db46280-a002-4d4e-b5cf-59533f9aa36d = {'status': 'Active', 'diskfree': '15837691904', 'alerts': [], 'version': 3, 'disktotal': '21072183296'}
[...]
Comment 3 Dafna Ron 2013-05-12 05:12:28 EDT
root@gold-vdsc ~]# vdsClient -s 0 getVdsStats |grep --color version
	storageDomains = {'4ba9a5fe-a9e7-48e0-b187-08ff11800d6d': {'delay': '0.0075409412384', 'lastCheck': '7.4', 'code': 0, 'valid': True, 'version': 0}}

[root@gold-vdsc ~]# vdsClient -s 0 getVdsStats |grep --color version
	storageDomains = {'4ba9a5fe-a9e7-48e0-b187-08ff11800d6d': {'delay': '0.00836682319641', 'lastCheck': '0.9', 'code': 0, 'valid': True, 'version': 2}}


[root@gold-vdsc ~]# vdsClient -s 0 getVdsStats |grep --color version
	storageDomains = {'4ba9a5fe-a9e7-48e0-b187-08ff11800d6d': {'delay': '0.0090320110321', 'lastCheck': '1.6', 'code': 0, 'valid': True, 'version': 3}}


[root@gold-vdsc ~]# vdsClient -s 0 getStoragePoolInfo 581763c4-8821-4112-968e-9dfac09d64ff
	name = 30
	isoprefix = 
	pool_status = connected
	lver = 0
	domains = 4ba9a5fe-a9e7-48e0-b187-08ff11800d6d:Active
	master_uuid = 4ba9a5fe-a9e7-48e0-b187-08ff11800d6d
	version = 3
	spm_id = 1
	type = ISCSI
	master_ver = 1
	4ba9a5fe-a9e7-48e0-b187-08ff11800d6d = {'status': 'Active', 'diskfree': '27648851968', 'alerts': [], 'version': 3, 'disktotal': '31809601536'}


verified on vdsm-4.10.2-18.0.el6ev.x86_64
Comment 5 errata-xmlrpc 2013-06-10 16:48:21 EDT
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/RHSA-2013-0886.html

Note You need to log in before you can comment on or make changes to this bug.