Hide Forgot
Created attachment 815347 [details] ## Logs rhevm, vdsm, libvirt, thread dump, superVdsm Description of problem: Remove Data Center action isn’t roll forward after restart “ovirt-engine” or “vdsmd” service. Version-Release number of selected component (if applicable): RHEVM 3.3 - IS19 environment: Host OS: RHEL 6.5 RHEVM: rhevm-3.3.0-0.27.beta1.el6ev.noarch PythonSDK: rhevm-sdk-python-3.3.0.16-1.el6ev.noarch VDSM: vdsm-4.13.0-0.3.beta1.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-29.el6.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.414.el6.x86_64 SANLOCK: sanlock-2.8-1.el6.x86_64 How reproducible: 100 % Steps to Reproduce: 1. Create Data Center (DC) with one Host and one Storage Domain (SD) 2. Enter SD to “Maintenance” mode 3. Remove DC 4. During remove DC action run following action: a. Reboot host - Test Case 139739 b. Restart vdsm - Test Case 139738 c. Restart jboss (ovirt-engine) - Test Case 139740 d. Restart RHEVM host - Test Case 139741 Actual results: 1. Action Fail 2. SD - become UP 3. There isn’t Roll Forward action Expected results: Action should fail and Roll Forward Impact on user: none Workaround: none
were these test cases executed and passed on 3.2 ? was it force remove ? or remove ?
(In reply to Barak from comment #2) > were these test cases executed and passed on 3.2 ? > didn't see any execution on 3.2 (no TCMS runs) - removing regression > was it force remove ? or remove ? I recheck it with remove and DC become active as well as SD. host (10.35.116.2), 1 SD (on VNX - ISCSI) remove the DC and restart vdsm on host attaching logs
Created attachment 819889 [details] engine
Created attachment 819890 [details] vdsm
does the DC still exists ?
yes
The SD became active instead remain maintenance. In case no roll forward, I expect it to remain the same.