Bug 746975 - VDSM - Storage: Can't deactivate unreachable NFS domain
Summary: VDSM - Storage: Can't deactivate unreachable NFS domain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: Daniel Paikov
URL:
Whiteboard: Storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-18 13:17 UTC by Daniel Paikov
Modified: 2013-07-04 07:51 UTC (History)
8 users (show)

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

Attachments (Terms of Use)
vdsm.log (575.77 KB, application/x-gzip)
2011-10-18 13:17 UTC, Daniel Paikov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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 Daniel Paikov 2011-10-18 13:17:19 UTC 
Created attachment 528804 [details]
vdsm.log

* DC with multiple NFS domains.
* Block a non-master domain with iptables.
* RHEVM tries to deactivate the domain every few minutes and fails each time for "Timeout: Operation Stuck".
Comment 1 Igor Lvovsky 2011-10-18 15:09:32 UTC 
http://gerrit.usersys.redhat.com/#change,1044
Comment 2 Dan Kenigsberg 2011-10-19 09:31:35 UTC 
Patch is plain and simple, but I cannot justify it as a rhev-3.0 blocker. If
anyone thinks otherwise, fight back!
Comment 3 Daniel Paikov 2011-10-19 09:42:00 UTC 
What if this is applies to master domains as well? We might lose reconstructMaster functionality. This also might be a regression - I remember this working very recently.
Comment 6 Daniel Paikov 2011-10-25 16:10:14 UTC 
Checked on 4.9-109.
Comment 7 errata-xmlrpc 2011-12-06 07:29:41 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.