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 480748[details]
logs
Description of problem:
run-once stateless VM running on spm and migrated because of storage disconnection will pause due to I/O errors after reconnecting storage and running VM normally on source again.
log show the following:
QMon-193::INFO::2011-02-24 14:48:02,753::vm::959::vds.vmlog.3d98f3d4-cb8b-44fa-bda6-55866039dbcd::abnormal vm stop device ide0-hd0 error Operation not permitted
QMon-193::DEBUG::2011-02-24 14:48:02,753::QemuMonitor::317::vds.vmlog.3d98f3d4-cb8b-44fa-bda6-55866039dbcd::# VM is stopped due to disk write error: ide0-hd0: Operation not perm
itted
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. run stateless VM on run-once on SPM and block communication between host and storage
2. after VM migrate stop VM
3. run the VM on the source host (not in run once stateless)
Actual results:
the VM will pause due to I/O errors
Expected results:
the VM should run normally.
Additional info:
logs
(In reply to comment #1)
> Migrating due to storage failure is not supported.
> Correct behaviour is not to migrate the VM at all.
> Moving to backend.
If the host disconnects from a data SD it changes it's status to non operational state and the VMs are migrated not according to user defined policy.
That is the supported behaviour, no issue to handle in backend.
Ayal I think the issue is not about migrating or not but the pause VM behaviour which i am not sure is wrong.
Please review again and if you don't see issues with the VDSM behaviour you can close this.
Created attachment 480748 [details] logs Description of problem: run-once stateless VM running on spm and migrated because of storage disconnection will pause due to I/O errors after reconnecting storage and running VM normally on source again. log show the following: QMon-193::INFO::2011-02-24 14:48:02,753::vm::959::vds.vmlog.3d98f3d4-cb8b-44fa-bda6-55866039dbcd::abnormal vm stop device ide0-hd0 error Operation not permitted QMon-193::DEBUG::2011-02-24 14:48:02,753::QemuMonitor::317::vds.vmlog.3d98f3d4-cb8b-44fa-bda6-55866039dbcd::# VM is stopped due to disk write error: ide0-hd0: Operation not perm itted Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. run stateless VM on run-once on SPM and block communication between host and storage 2. after VM migrate stop VM 3. run the VM on the source host (not in run once stateless) Actual results: the VM will pause due to I/O errors Expected results: the VM should run normally. Additional info: logs