Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1093364

Summary: Call hosted-engine --vm-status stuck when no connection to storage domain
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-hosted-engine-haAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: alukiano, dfediuck, gchaplik, gklein, iheim, mavital, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-05 13:41:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
agent broker and vdsm logs none

Description Artyom 2014-05-01 14:20:10 UTC
Created attachment 891545 [details]
agent broker and vdsm logs

Description of problem:
Call hosted-engine --vm-status stuck when no connection to storage domain, it possible just to kill process via other session.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-1.1.2-2.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Setup hosted engine environment with host, block connection from host to database(iptables -I INPUT -s ip_sd -j DROP)
2. Run hosted-engine --vm-status
3.

Actual results:
Command stuck and not possible to interrupt command via same session

Expected results:
Some error message("No connection to storage domain") without stuck

Additional info:

Comment 1 Doron Fediuck 2014-05-04 06:30:26 UTC
Was it tested with nfs or iscsi?

Comment 2 Artyom 2014-05-04 06:33:27 UTC
Storage NFS, all bugs that opened until 3.5 it for NFS

Comment 3 Jiri Moskovcak 2014-05-05 13:41:08 UTC

*** This bug has been marked as a duplicate of bug 1085523 ***