| Summary: | [vdsm] Exception raised while attaching new storage domain directly from dialog to uninitialized data-center | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jakub Libosvar <jlibosva> | ||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | yeylon <yeylon> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1 | CC: | abaron, bazulay, iheim, srevivo, ykaul | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-06 13:16:29 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
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.
|
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