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 487015[details]
vdsm log
Description of problem:
due to a rollback of transaction of attachStorageDomain of RHEVM, a mismatch in between SD status in vdsm and RHEVM has happened, when trying to reattach it (with the same parameters) command fails:
Thread-39186::INFO::2011-03-23 10:43:00,235::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: attachStorageDomain, args: ( sdUUID=43df69c6-130a-4093-b697-54cb73e34e6c spUUID=232e5637-d880-4d7c-bb0a-db62197bfc04)
StorageDomainAlreadyAttached: Storage domain already attached to pool: 'domain=43df69c6-130a-4093-b697-54cb73e34e6c, pool=232e5637-d880-4d7c-bb0a-db62197bfc04'
Version-Release number of selected component (if applicable):
vdsm-4.9-55.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
if the domain is already attached to the same pool it was given in the command, vdsm should return ok code 0.
Additional info:
verified on vdsm-4.9-57.el6.x86_64.
Had domain already attached to pool.
tried the following command from vdsClient:
vdsClient -s 0 attachStorageDomain 4fc95249-bda1384c96a5637 9e88ba05-9188-44f2-a6b4-11abca6b4181
command succeeded as vdsm returned status '0'.
flow:
Thread-1477::INFO::2011-04-05 20:31:32,625::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: attachStorageDomain, args: ( sdUUID=4fc95249-bda
2-4f6c-82bf-1384c96a5637 spUUID=9e88ba05-9188-44f2-a6b4-11abca6b4181)
Thread-1477::WARNING::2011-04-05 20:31:52,889::sp::779::Storage.StoragePool::(_attachSD) SD 9e88ba05-9188-44f2-a6b4-11abca6b4181 is already attached to SP 9e88ba05-9188-44f2-a6b4-11abca6b4181
Thread-1477::INFO::2011-04-05 20:31:53,973::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: attachStorageDomain, Return response: {'status': {'message': 'OK', 'code': 0}}
Created attachment 487015 [details] vdsm log Description of problem: due to a rollback of transaction of attachStorageDomain of RHEVM, a mismatch in between SD status in vdsm and RHEVM has happened, when trying to reattach it (with the same parameters) command fails: Thread-39186::INFO::2011-03-23 10:43:00,235::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: attachStorageDomain, args: ( sdUUID=43df69c6-130a-4093-b697-54cb73e34e6c spUUID=232e5637-d880-4d7c-bb0a-db62197bfc04) StorageDomainAlreadyAttached: Storage domain already attached to pool: 'domain=43df69c6-130a-4093-b697-54cb73e34e6c, pool=232e5637-d880-4d7c-bb0a-db62197bfc04' Version-Release number of selected component (if applicable): vdsm-4.9-55.el6.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: if the domain is already attached to the same pool it was given in the command, vdsm should return ok code 0. Additional info: