Bug 711059 - [vdsm] Exception raised while attaching new storage domain directly from dialog to uninitialized data-center
Summary: [vdsm] Exception raised while attaching new storage domain directly from dial...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-06 12:33 UTC by Jakub Libosvar
Modified: 2016-04-18 06:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-06 13:16:29 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm + backend logs (521.17 KB, application/x-gzip)
2011-06-06 12:33 UTC, Jakub Libosvar
no flags Details

Description Jakub Libosvar 2011-06-06 12:33:06 UTC
Created attachment 503208 [details]
vdsm + backend logs

Description of problem:
When creating new storage domain in rhev-m and attach to storage domain is selected - vdsm throws exception Unknown pool id, pool not connected. This error is not propagated to backend and the task in rhev-m finishes successfully and both domain and data-center are functional. vdsClient -s 0 getConnectedStoragePoolsList returns pool id thrown in above mentioned exception
Thread-242::ERROR::2011-06-06 14:07:27,413::task::865::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 873, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/storage/spm.py", line 715, in public_getSpmStatus
    hsm.HSM.validateConnectedPool(spUUID)
  File "/usr/share/vdsm/storage/hsm.py", line 85, in validateConnectedPool
    raise se.StoragePoolUnknown(spUUID)
StoragePoolUnknown: Unknown pool id, pool not connected: ('22dbfbdc-dcd2-4e6a-9a6c-1477c23da067',)


Version-Release number of selected component (if applicable):
ic121
vdsm-4.9-70

How reproducible:
Always

Steps to Reproduce:
1. Create new data-center
2. Go to storage tab and start creating new storage domain
3. While new storage domain dialog is opened, select target data-center the new created data-center created in step 1.
   
Actual results:
Exceptions are risen in vdsm log
Thread-242::ERROR::2011-06-06 14:07:27,416::dispatcher::103::Storage.Dispatcher.Protect::(run) {'status': {'message': "Unknown pool id, pool not connected: ('22dbfbdc-dcd2-4e6a-9a6c-1477c23da067',)", 'code': 309}, 'args': [('22dbfbdc-dcd2-4e6a-9a6c-1477c23da067',)]}


Expected results:
Operations finish successfully and no exceptions are risen

Additional info:
Synced backend and vdsm logs are attached

This may also be a bug in new storage dialog - in case it is

Comment 2 Dan Kenigsberg 2011-06-06 13:16:17 UTC
The exception

Thread-242::ERROR::2011-06-06
14:07:27,416::dispatcher::103::Storage.Dispatcher.Protect::(run) {'status':
{'message': "Unknown pool id, pool not connected:
('22dbfbdc-dcd2-4e6a-9a6c-1477c23da067',)", 'code': 309}, 'args':
[('22dbfbdc-dcd2-4e6a-9a6c-1477c23da067',)]}


is logged since rhevm insists on running getSpmStatus before pool is connected. That's not a vdsm bug.

If there is some kind of operational problem, or that you have a funny output for vdsClient command, please reopen this bug with more information.


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