Red Hat Bugzilla – Bug 1004316
[BLOCKED]Wrong error when trying to connect an export storage domain with broken checksum
Last modified: 2016-12-06 04:22:04 EST
Description of problem:
When trying to connect a storage domain with broken checksum, the vdsm does recognize this, but engine get information, that the domain does not exist, which results in confusing error in webadmin
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have export domain
2. Change sha_checksum in metadata
3. Try to import the storage domain
Error: There is no storage domain on specified path
Error that is readable in webadmin or at least in engine.log (in engine.log there is nothing at all)
vdsm.log and engine.log in attachment, the time of event is 2013-09-04 13:36:47
Created attachment 793642 [details]
vdsm log from host
Need to see if we can differentiate between no domain and broken domain and report different errors.
I have added the RFE 1183995 -[RFE] Allow force attaching an export domain with stale pool meta-data by turning it into a data domain to be dependent on this bug
I think that once we will have the ability to transfer Export Domain to Data Domain this bug will not be relevant any more, therefore
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.