Bug 671154

Summary: VDSM: getStoragePoolInfo fails due to missing POOL_DESCRIPTION in metadata
Product: Red Hat Enterprise Linux 6 Reporter: Ofer Schreiber <oschreib>
Component: vdsmAssignee: Eduardo Warszawski <ewarszaw>
Status: CLOSED CURRENTRELEASE QA Contact: yeylon <yeylon>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: abaron, bazulay, danken, dnaori, dpaikov, ewarszaw, iheim, srevivo
Target Milestone: rc   
Target Release: 6.1   
Hardware: Unspecified   
OS: Linux   
Whiteboard: Storage
Fixed In Version: vdsm-4.9-46 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 676582 (view as bug list) Environment:
Last Closed: 2011-08-19 15:12:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 676582    
Attachments:
Description Flags
vdsm log
none
second log none

Description Ofer Schreiber 2011-01-20 15:48:05 UTC
Created attachment 474481 [details]
vdsm log

Description of problem:
Master storage domain becomes unavailable due to wired metadata corruption

Version-Release number of selected component (if applicable):
vdsm-4.9-42.el6.x86_64

Additional info:
hread-1782::INFO::2011-01-20 16:03:59,353::dispatcher::95::Storage.Dispatcher.Protect::(run) Run and protect: getStoragePoolInfo, args: ( spUUID=306f74e4-03
6e-49d6-855e-0a8a0ea9fbe2)
Thread-1782::DEBUG::2011-01-20 16:03:59,353::task::491::TaskManager.Task::(_debug) Task 776612f2-3f80-49f2-aeec-2a15b47809f1: moving from state init -> state
 preparing
Thread-1782::DEBUG::2011-01-20 16:03:59,354::resourceManager::154::ResourceManager.Request::(__init__) ResName=`Storage.306f74e4-036e-49d6-855e-0a8a0ea9fbe2`
ReqID=`0b6deaa0-9875-4f67-ba71-fce0a00dcb93`::Request was made in '/usr/share/vdsm/storage/hsm.py' line '1132' at 'public_getStoragePoolInfo'
Thread-1782::DEBUG::2011-01-20 16:03:59,354::resourceManager::467::ResourceManager::(registerResource) Trying to register resource 'Storage.306f74e4-036e-49d
6-855e-0a8a0ea9fbe2' for lock type 'shared'
Thread-1782::DEBUG::2011-01-20 16:03:59,354::resourceManager::508::ResourceManager::(registerResource) Resource 'Storage.306f74e4-036e-49d6-855e-0a8a0ea9fbe2
' is free. Now locking as 'shared' (1 active user)
Thread-1782::DEBUG::2011-01-20 16:03:59,355::resourceManager::191::ResourceManager.Request::(grant) ResName=`Storage.306f74e4-036e-49d6-855e-0a8a0ea9fbe2`Req
ID=`0b6deaa0-9875-4f67-ba71-fce0a00dcb93`::Granted request
Thread-1782::DEBUG::2011-01-20 16:03:59,355::task::491::TaskManager.Task::(_debug) Task 776612f2-3f80-49f2-aeec-2a15b47809f1: _resourcesAcquired: Storage.306
f74e4-036e-49d6-855e-0a8a0ea9fbe2 (shared)
Thread-1782::DEBUG::2011-01-20 16:03:59,356::task::491::TaskManager.Task::(_debug) Task 776612f2-3f80-49f2-aeec-2a15b47809f1: ref 1 aborting False
Thread-1782::ERROR::2011-01-20 16:03:59,356::sp::1154::Storage.StoragePool::(getInfo) Pool metadata error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/sp.py", line 1148, in getInfo
    info['name'] = metadata[sd.POOL_DESCRIPTION]
KeyError: 'POOL_DESCRIPTION'
Thread-1782::ERROR::2011-01-20 16:03:59,357::task::854::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 862, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/storage/hsm.py", line 1133, in public_getStoragePoolInfo
    return self.getPool(spUUID).getInfo()
  File "/usr/share/vdsm/storage/sp.py", line 1155, in getInfo
    raise se.StoragePoolActionError(self.spUUID)
StoragePoolActionError: Error storage pool action: ('306f74e4-036e-49d6-855e-0a8a0ea9fbe2',)

Comment 1 Ofer Schreiber 2011-01-20 15:51:46 UTC
Created attachment 474483 [details]
second log

Comment 2 Ofer Schreiber 2011-01-20 16:17:10 UTC
This issue appears to be reproduced only when two hosts are connected to the same Data-Center.

Comment 3 Eduardo Warszawski 2011-01-20 17:00:41 UTC
Was verified that POOL_DESCRIPTION is not in the metadata keys.

Comment 4 Ayal Baron 2011-02-10 07:42:05 UTC
Should be fixed in 46

Comment 5 Ayal Baron 2011-02-10 07:43:32 UTC
Reproduce steps:
1. Get setup to work and have an SPM up.
2. setDescription of a domain

Comment 6 David Naori 2011-02-20 12:04:26 UTC
Followed reproduce steps.

after setting pools description and domain description getStoragePoolInfo returns Successfully with the new Description. 

Thread-1688::INFO::2011-02-20 13:57:32,039::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: getStoragePoolInfo, Return response: {'status': {'message': 'OK',
 'code': 0}, 'info': {'spm_id': '2', 'master_uuid': '3afc595e-3d0a-4fa7-8c22-c72688a1ff01', 'name': 'david', 'version': 0, 'domains': '231f7bb3-0b77-481c-8dc8-9b32271e09fe:Attac
hed,6b9feadd-7bbb-4605-bf3b-dd425227e568:Attached,8ebeceaa-e7ac-4606-8506-704c3fc805f8:Attached,3afc595e-3d0a-4fa7-8c22-c72688a1ff01:Active', 'pool_status': 'connected', 'isopre
fix': '', 'type': 'ISCSI', 'master_ver': '4', 'lver': '4'}, 'dominfo': {'231f7bb3-0b77-481c-8dc8-9b32271e09fe': {'status': 'Attached'}, '8ebeceaa-e7ac-4606-8506-704c3fc805f8': {
'status': 'Attached'}, '6b9feadd-7bbb-4605-bf3b-dd425227e568': {'status': 'Attached'}, '3afc595e-3d0a-4fa7-8c22-c72688a1ff01': {'status': 'Active', 'diskfree': '87308632064', 'd
isktotal': '107105746944'}}}