Description of problem: When trying to refresh a LUN attached to a powered off VM an error raised. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.create VM 2.attach LUN 3.try to refresh the LUN without power on the VM. Actual results: the operation fails. Expected results: the refresh should be successful. Additional info:
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Continuing to bug 1810021 that was verified by me just for the 2 following ERRORS that don't appears anymore : 1)"Error while executing action: Cannot sync Virtual Disk. Operation can be performed only when Host status if UP" 2)"Error while executing action: Cannot sync Virtual Disk. Related operation is currently in progress, PLease try again later." This bug opened to fix the refresh LUN operation that it's failing now on the following ERROR: "Error while executing action: Cannot sync Virtual Disk. Invalid Host Id" Screenshot attached. 2020-10-15 15:52:34,539+03 WARN [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (default task-27) [64124a1d-8cdc-4eb2-944d-59698c8c2745] Validation of action 'SyncDirectLuns' failed for user admin@internal-authz. Reasons: VAR__ACTION__SYNC,VAR__TYPE__DISK,VDS_INVALID_SERVER_ID
Created attachment 1721819 [details] Screenshot1
This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status
I see this bug has no severity and no priority set, can you please check if this bug needs deeper verification from QE?
I think it's better to do a deep QE verification, I didn't set severity but this bug caused almost all refresh lun operations to failed so better check that the fix really solved the issue on a more complex environment with at least two DCs.
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.