Bug 725802

Summary: vdsmd becomes defunct when blocking traffic between SPM to Master Storage Domain
Product: Red Hat Enterprise Linux 6 Reporter: Rami Vaknin <rvaknin>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED ERRATA QA Contact: Kiril Nesenko <knesenko>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, dfediuck, egerman, iheim, knesenko, mgoldboi, oramraz, yeylon, ykaul
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: vdsm-4.9-92 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:32:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
vdsm logs none

Description Rami Vaknin 2011-07-26 15:34:57 UTC
Created attachment 515308 [details]
vdsm logs

Env: rhevm-3.0.0_0001-18.el6.x86_64, vdsm-4.9-84.el6.x86_64

Scenario:
1 host in the data center, 1 iscsi storage domain, blocking traffic to the storage using iptables

Result:
vdsmd stopped and does not start, it becomes defunct for ~30 seconds


[root@stone-vds1 ~]# ps -ww `pgrep vdsm`
  PID TTY      STAT   TIME COMMAND
 8981 ?        S<     0:00 /usr/bin/python /usr/share/vdsm//vdsm
 8983 ?        S<     0:00 /usr/bin/python /usr/share/vdsm//vdsm
24820 ?        Z<l    0:21 [vdsm] <defunct>
[root@stone-vds1 ~]#

Comment 8 Dan Kenigsberg 2011-07-28 12:58:38 UTC
(this is yet untested, but I'm considering to retry starting vdsm even the first try after fencing fails.)

http://gerrit.usersys.redhat.com/755

Comment 11 Kiril Nesenko 2011-08-25 08:15:19 UTC
After a defunct vdsm continues to run.
Verified
ic138.1
vdsm-4.9-95.el6.x86_64

Comment 12 errata-xmlrpc 2011-12-06 07:32:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html