Hide Forgot
Created attachment 490236 [details] vdsm & backend logs Description of problem: When guest is running with attached ISO from ISO domain and this ISO domain becomes unreachable (blocked by iptables), guest becomes Not responding. After a few mins it becomes up. Then again Non-responding and so on. Version-Release number of selected component (if applicable): sm101 vdsm22-4.5-63.25.el5_6 How reproducible: Always Steps to Reproduce: 1. Attach ISO to CD rom of running guest (tested with w2k8 r2 installed on guest) 2. Make iso export unreachable on storage server (iptables) Actual results: Guest changes status from Up to Not responding and back Expected results: Not sure Additional info: vdsm & backend log attached. Monitor response is set on -1 in case guest is in Not responding. 0 on Up state. Host is always in Up state
(In reply to comment #0) > Steps to Reproduce: > 2. Make iso export unreachable on storage server (iptables) Sorry, I made a mistake - 2. Make ISO domain unreachable
Came from test plan: "Test run for Storage - ISO domain on RHEVM-QA", https://tcms.engineering.redhat.com/run/19322/#caserun_464969 should verify if its a regression, last time test passed : was plan #14677 (build sm91).
Jakub, please help us verify if this is a true regression - would you replace vdsm (only!) with vdsm22-4.5-63.23 and retry this test? Also, with your current vdsm22-4.5-63.25.el5_6, please measure how much time does it take for vdsCleint -s 0 <vmid> monitorCommand 'info blockstats' to return when ISO export is blocked?
Reproducible on 63.23 as well. I'll try again 63.9 vdsClient command ends with Unexpected exception after a minute and 6.301 seconds
Note: Using vdsm 63.23 led to Non-Responsive data-center as well. All SDs are in Unknown status.
Please verify if similar behavior appears with rhev-2.3 (over rhel6)
Regarding the guest not-responding behavior: opened kvm-qemu BZ #695082, using vdsm22-4.5-63.9.el5 : **************************** unable to reproduce the described behavior from Comment #6 - "Using vdsm 63.23 led to Non-Responsive data-center as well. All SDs are in Unknown status."
Closing Bug, - unable to reproduce storage domains behavior from comment #6 RHEL5.6 (vdsm22-4.5-63.25.el5_6) Or using RHEL6 (vdsm-4.9-51.el6.x86_64).