Bug 910005 - vdsm: connect to super vdsm failed due to fail in prepareForShutDown
vdsm: connect to super vdsm failed due to fail in prepareForShutDown
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: 3.2.0
Assigned To: Yaniv Bronhaim
Dafna Ron
: Regression
: 909967 (view as bug list)
Depends On:
Blocks: 910490 915537
  Show dependency treegraph
Reported: 2013-02-11 10:52 EST by Dafna Ron
Modified: 2016-02-10 14:34 EST (History)
10 users (show)

See Also:
Fixed In Version: vdsm-4.10.2-8.0.el6ev
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 910490 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs (405.42 KB, application/x-gzip)
2013-02-11 10:52 EST, Dafna Ron
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 11932 None None None Never

  None (edit)
Description Dafna Ron 2013-02-11 10:52:37 EST
Created attachment 696148 [details]

Description of problem:

I blocked my iscsi storage domain (1 domain) from both my hosts using iptables. 
connect to super vdsm failed due to fail in prepareForShutDown and vdsm is "stuck"

MainThread::DEBUG::2013-02-11 13:58:14,051::clientIF::228::vds::(prepareForShutdown) cannot run prepareForShutdown concurrently
MainThread::DEBUG::2013-02-11 13:58:15,051::clientIF::228::vds::(prepareForShutdown) cannot run prepareForShutdown concurrently

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a pool with 1 iscsi storage domain on two host's cluster
2. block connectivity to storage from both hosts using iptables
Actual results:

connect to super vdsm failed due to fail in prepareForShutDown which leaves the vdsm "stuck" 

Expected results:

vdsm should suceed in prepareForShutdown

Additional info:logs
Comment 2 Yaniv Bronhaim 2013-02-11 11:48:26 EST
The socket file to communicate with supervdsm was not exist. I still work to figure how it happened, but it can happens as we see.

I'm so sure if it is related to the failure in prepareForShutdown because after the reset we also clean the socket file and create it again.

When the connect fails, we try again and that's it. My patch changes this process - now we'll try to communicate with supervdsm socket 3 times, and if we fail, we'll kill the process and start it again. The socket is created as part of the initialization of the process.
Comment 3 Yaniv Bronhaim 2013-02-12 05:58:27 EST
Instead of killing the process and start it again, I changed it to get vdsm into panic and kill itself. When this occurred vdsm will restart by respawn.

This senerio has never happened to me yet and if it is reproducible as mentioned in the bug description please let me know and see.
Comment 6 Dafna Ron 2013-02-20 12:34:38 EST
verified on vdsm-4.10.2-8.0.el6ev.x86_64

I can see that vdsm is still stuck but manages to recover
Comment 7 Yaniv Bronhaim 2013-06-09 04:41:57 EDT
*** Bug 909967 has been marked as a duplicate of this bug. ***
Comment 8 Itamar Heim 2013-06-11 05:40:43 EDT
3.2 has been released
Comment 9 Itamar Heim 2013-06-11 05:41:12 EDT
3.2 has been released
Comment 10 Itamar Heim 2013-06-11 05:54:01 EDT
3.2 has been released

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