Bug 1415723 - After upgrade storage domain fail to activate
Summary: After upgrade storage domain fail to activate
Keywords:
Status: CLOSED DUPLICATE of bug 1410036
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0.2
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: ovirt-4.1.0-beta
: ---
Assignee: Fred Rolland
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-23 14:37 UTC by guy chen
Modified: 2017-01-23 16:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 16:51:58 UTC
oVirt Team: Storage
rule-engine: ovirt-4.1+
rule-engine: blocker+


Attachments (Terms of Use)

Description guy chen 2017-01-23 14:37:46 UTC
Description of problem:

I have upgraded engine and host from version 4.1 build 4 to build 8, after  upgrade storage domain fail to activate

Version-Release number of selected component (if applicable):

ovirt-engine-4.1.0.2-0.1.el7.noarch
vdsm-4.19.2-2.el7ev.x86_64

Steps to Reproduce:
1.upgraded engine and host from version 4.1 build 4 to build 8
2.Activate storage domain
3.SD fail to activate with error message "Failed to activate Storage Domain"

Actual results:

SD fail to activate with error message "Failed to activate Storage Domain"

Expected results:

SD will succeed activating

Additional info:

the errors from from vdsm log :


2017-01-23 16:26:47,451 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='65850ab5-b302-4a81-b162-5aa8d7951c84') Unexpected error (task:870)
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 877, in _run
    return fn(*args, **kargs)
  File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 1218, in activateStorageDomain
    pool.activateSD(sdUUID)
  File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper
    return method(self, *args, **kwargs)
  File "/usr/share/vdsm/storage/sp.py", line 1089, in activateSD
    dom = sdCache.produce(sdUUID)
  File "/usr/share/vdsm/storage/sdc.py", line 112, in produce
    domain.getRealDomain()
  File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain
    return self._cache._realProduce(self._sdUUID)
  File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce
    domain = self._findDomain(sdUUID)
  File "/usr/share/vdsm/storage/sdc.py", line 155, in _findDomain
    dom = findMethod(sdUUID)
  File "/usr/share/vdsm/storage/blockSD.py", line 1598, in findDomain
    return BlockStorageDomain(BlockStorageDomain.findDomainPath(sdUUID))
  File "/usr/share/vdsm/storage/blockSD.py", line 951, in __init__
    lvm.activateLVs(self.sdUUID, special_lvs)
  File "/usr/share/vdsm/storage/lvm.py", line 1299, in activateLVs
    _setLVAvailability(vgName, inactive, "y")
  File "/usr/share/vdsm/storage/lvm.py", line 846, in _setLVAvailability
    raise error(str(e))
CannotActivateLogicalVolumes: Cannot activate Logical Volumes: ('General Storage Exception: (\'5 [] [\\\'  Failed to find logical volume "70e79239-983a-4376-9cde-d1744488334c/xleases"\\\']\\n70e79239-983a-4376-9cde-d1744488334c/[\\\'xleases\\\']\',)',)
2017-01-23 16:26:47,452 INFO  (jsonrpc/4) [storage.TaskManager.Task] (Task='65850ab5-b302-4a81-b162-5aa8d7951c84') aborting: Task is aborted: 'Cannot activate Logical Volumes' - code 570 (task:1175)
2017-01-23 16:26:47,452 ERROR (jsonrpc/4) [storage.Dispatcher] {'status': {'message': 'Cannot activate Logical Volumes: (\'General Storage Exception: (\\\'5 [] [\\\\\\\'  Failed to find logical volume "70e79239-983a-4376-9cde-d1744488334c/xleases"\\\\\\\']\\\\n70e79239-983a-4376-9cde-d1744488334c/[\\\\\\\'xleases\\\\\\\']\\\',)\',)', 'code': 570}} (dispatcher:77)

Comment 2 Nisim Simsolo 2017-01-23 14:47:56 UTC
Same issue occurred also on my setup.

Comment 3 Nir Soffer 2017-01-23 16:47:55 UTC
This is a duplicate of bug 1410036

Comment 4 Fred Rolland 2017-01-23 16:51:58 UTC

*** This bug has been marked as a duplicate of bug 1410036 ***


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