Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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