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.
DescriptionJaroslav Henner
2011-07-16 07:02:19 UTC
Description of problem:
Sometimes, I'm given following error message when trying to remove and format the data domain with host A. With host B it works fine. No host is SPM when trying this and error message appears.
Version-Release number of selected component (if applicable):
vdsm-4.9-81.el6.x86_64
How reproducible:
20%
Steps to Reproduce:
1. Have a data domain.
2. Remove it
Actual results:
vdsm.log
Thread-486::DEBUG::2011-07-16 08:48:53,883::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: moving from state init -> state preparing
Thread-486::DEBUG::2011-07-16 08:48:53,883::resourceManager::154::ResourceManager.Request::(__init__) ResName=`Storage.bb564256-e768-4dde-9e24-ba3fa9738b93`ReqID=`f8660b7b-eb3d-455e-a4a2-1cbc50553397`::Request was made in '/usr/share/vdsm/storage/hsm.py' line '1209' at 'public_formatStorageDomain'
Thread-486::DEBUG::2011-07-16 08:48:53,883::resourceManager::467::ResourceManager::(registerResource) Trying to register resource 'Storage.bb564256-e768-4dde-9e24-ba3fa9738b93' for lock type 'exclusive'
Thread-486::DEBUG::2011-07-16 08:48:53,884::resourceManager::508::ResourceManager::(registerResource) Resource 'Storage.bb564256-e768-4dde-9e24-ba3fa9738b93' is free. Now locking as 'exclusive' (1 active user)
Thread-486::DEBUG::2011-07-16 08:48:53,884::resourceManager::191::ResourceManager.Request::(grant) ResName=`Storage.bb564256-e768-4dde-9e24-ba3fa9738b93`ReqID=`f8660b7b-eb3d-455e-a4a2-1cbc50553397`::Granted request
Thread-486::DEBUG::2011-07-16 08:48:53,884::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: _resourcesAcquired: Storage.bb564256-e768-4dde-9e24-ba3fa9738b93 (exclusive)
Thread-486::DEBUG::2011-07-16 08:48:53,885::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 1 aborting False
Thread-486::ERROR::2011-07-16 08:48:53,885::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/hsm.py", line 1221, in public_formatStorageDomain
raise se.CannotFormatAttachedStorageDomain(sdUUID)
CannotFormatAttachedStorageDomain: Cannot format attached storage domain: ('bb564256-e768-4dde-9e24-ba3fa9738b93',)
Thread-486::DEBUG::2011-07-16 08:48:53,886::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Task._run: 8f9e7925-6558-4e22-af72-482b2c6b93ce ('bb564256-e768-4dde-9e24-ba3fa9738b93',) {} failed - stopping task
Thread-486::DEBUG::2011-07-16 08:48:53,886::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: stopping in state preparing (force False)
Thread-486::DEBUG::2011-07-16 08:48:53,887::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 1 aborting True
Thread-486::INFO::2011-07-16 08:48:53,887::task::1177::TaskManager.Task::(prepare) aborting: Task is aborted: 'Cannot format attached storage domain' - code 391
Thread-486::DEBUG::2011-07-16 08:48:53,887::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Prepare: aborted: Cannot format attached storage domain
Thread-486::DEBUG::2011-07-16 08:48:53,888::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 0 aborting True
Thread-486::DEBUG::2011-07-16 08:48:53,888::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Task._doAbort: force False
Thread-486::DEBUG::2011-07-16 08:48:53,888::resourceManager::821::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {}
Expected results:
Storage domain gone and formatted.
Additional info:
How did you get to remove a data domain which is still attached to its pool?
Please give details on your setup (how many hosts? how many storage domains?), the perceived state of your storage domains - and relevant logs.
(In reply to comment #2)
> How did you get to remove a data domain which is still attached to its pool?
It was not. It was in detached state. However I removed the pool just before I removed the SD.
> Please give details on your setup (how many hosts?
two
> how many storage domains?
I had one storage pool, one export domain there, which I removed fine. Also one data domain -- the one that caused the problems. There was a template imported from the export domain to the data domain and couple of machines from VM pool from that template. I removed all of that and after that I was removing the storage domain and went to this issue.
> the perceived state of your storage domains - and relevant logs.
Which log would you like? You have vdsm log up there. How can I know what's relevant?
Please attach vdsm.log files (bugzilla would thank you if you use compression) from both hosts, from the time that you started dismantling the storage pool.
Created attachment 513503[details]
logs
23:00:54,517 There was an error when attaching the export domain to the pool.
23:22:27,940 There was an error when removing the data domain.
Note there is Bug 722699 - Failed to attach Storage due to an error on the Data Center master Storage Domain. Now it seems that it very probably is related.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2011-1782.html
Description of problem: Sometimes, I'm given following error message when trying to remove and format the data domain with host A. With host B it works fine. No host is SPM when trying this and error message appears. Version-Release number of selected component (if applicable): vdsm-4.9-81.el6.x86_64 How reproducible: 20% Steps to Reproduce: 1. Have a data domain. 2. Remove it Actual results: vdsm.log Thread-486::DEBUG::2011-07-16 08:48:53,883::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: moving from state init -> state preparing Thread-486::DEBUG::2011-07-16 08:48:53,883::resourceManager::154::ResourceManager.Request::(__init__) ResName=`Storage.bb564256-e768-4dde-9e24-ba3fa9738b93`ReqID=`f8660b7b-eb3d-455e-a4a2-1cbc50553397`::Request was made in '/usr/share/vdsm/storage/hsm.py' line '1209' at 'public_formatStorageDomain' Thread-486::DEBUG::2011-07-16 08:48:53,883::resourceManager::467::ResourceManager::(registerResource) Trying to register resource 'Storage.bb564256-e768-4dde-9e24-ba3fa9738b93' for lock type 'exclusive' Thread-486::DEBUG::2011-07-16 08:48:53,884::resourceManager::508::ResourceManager::(registerResource) Resource 'Storage.bb564256-e768-4dde-9e24-ba3fa9738b93' is free. Now locking as 'exclusive' (1 active user) Thread-486::DEBUG::2011-07-16 08:48:53,884::resourceManager::191::ResourceManager.Request::(grant) ResName=`Storage.bb564256-e768-4dde-9e24-ba3fa9738b93`ReqID=`f8660b7b-eb3d-455e-a4a2-1cbc50553397`::Granted request Thread-486::DEBUG::2011-07-16 08:48:53,884::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: _resourcesAcquired: Storage.bb564256-e768-4dde-9e24-ba3fa9738b93 (exclusive) Thread-486::DEBUG::2011-07-16 08:48:53,885::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 1 aborting False Thread-486::ERROR::2011-07-16 08:48:53,885::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/hsm.py", line 1221, in public_formatStorageDomain raise se.CannotFormatAttachedStorageDomain(sdUUID) CannotFormatAttachedStorageDomain: Cannot format attached storage domain: ('bb564256-e768-4dde-9e24-ba3fa9738b93',) Thread-486::DEBUG::2011-07-16 08:48:53,886::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Task._run: 8f9e7925-6558-4e22-af72-482b2c6b93ce ('bb564256-e768-4dde-9e24-ba3fa9738b93',) {} failed - stopping task Thread-486::DEBUG::2011-07-16 08:48:53,886::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: stopping in state preparing (force False) Thread-486::DEBUG::2011-07-16 08:48:53,887::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 1 aborting True Thread-486::INFO::2011-07-16 08:48:53,887::task::1177::TaskManager.Task::(prepare) aborting: Task is aborted: 'Cannot format attached storage domain' - code 391 Thread-486::DEBUG::2011-07-16 08:48:53,887::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Prepare: aborted: Cannot format attached storage domain Thread-486::DEBUG::2011-07-16 08:48:53,888::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: ref 0 aborting True Thread-486::DEBUG::2011-07-16 08:48:53,888::task::492::TaskManager.Task::(_debug) Task 8f9e7925-6558-4e22-af72-482b2c6b93ce: Task._doAbort: force False Thread-486::DEBUG::2011-07-16 08:48:53,888::resourceManager::821::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {} Expected results: Storage domain gone and formatted. Additional info: