Bug 725802 - vdsmd becomes defunct when blocking traffic between SPM to Master Storage Domain
Summary: vdsmd becomes defunct when blocking traffic between SPM to Master Storage Domain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: Kiril Nesenko
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 15:34 UTC by Rami Vaknin
Modified: 2014-07-11 00:07 UTC (History)
10 users (show)

Fixed In Version: vdsm-4.9-92
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:32:06 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm logs (737.13 KB, application/x-gzip)
2011-07-26 15:34 UTC, Rami Vaknin
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

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


Note You need to log in before you can comment on or make changes to this bug.