<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 2, 2017 at 3:51 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
> Can you confirm that the host can be active when I restart vdsmd service?<br>
<br>
</span>Sure. This may abort a storage operation if one is running when you restart<br>
vdsm, but vdsm is designed so you can restart or kill it safely.<br>
<br>
For example, if you abort a disk copy in the middle, the operation will fail<br>
and the destination disk will be deleted.<br>
<br>
If you want to avoid such issue, you can put a host to maintenance, but this<br>
requires migration of vms to other hosts.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Nir<br></font></span></blockquote><div><br></div><div>OK. Created 50_thin_block_extension_rules.conf under /etc/vdsm/vdsm.conf.d and restarted vdsmd</div><div><br></div><div>One last (latest probably... ;-) question</div><div>Is it expected that if I restart vdsmd on the host that is the SPM, then SPM is shifted to another node?</div><div>Because when restarting vdsmd on the host that is not SPM I didn't get any message in web admin gui and restart of vdsmd itself was very fast.</div><div>Instead on the host with SPM, the command took several seconds and I got these events </div><div><br></div><div>Feb 2, 2017 4:01:23 PM Host ovmsrv05 power management was verified successfully.</div><div>Feb 2, 2017 4:01:23 PM Status of host ovmsrv05 was set to Up.</div><div>Feb 2, 2017 4:01:19 PM Executing power management status on Host ovmsrv05 using Proxy Host ovmsrv06 and Fence Agent ilo:10.4.192.212.</div><div>Feb 2, 2017 4:01:18 PM Storage Pool Manager runs on Host ovmsrv06 (Address: <a href="http://ovmsrv06.datacenter.polimi.it">ovmsrv06.datacenter.polimi.it</a>).</div><div>Feb 2, 2017 4:01:13 PM VDSM ovmsrv05 command failed: Recovering from crash or Initializing</div><div>Feb 2, 2017 4:01:11 PM Host ovmsrv05 is initializing. Message: Recovering from crash or Initializing</div><div>Feb 2, 2017 4:01:11 PM VDSM ovmsrv05 command failed: Recovering from crash or Initializing</div><div>Feb 2, 2017 4:01:11 PM Invalid status on Data Center Default. Setting Data Center status to Non Responsive (On host ovmsrv05, Error: Recovering from crash or Initializing).</div><div>Feb 2, 2017 4:01:11 PM VDSM ovmsrv05 command failed: Recovering from crash or Initializing</div><div>Feb 2, 2017 4:01:05 PM Host ovmsrv05 is not responding. It will stay in Connecting state for a grace period of 80 seconds and after that an attempt to fence the host will be issued.</div><div>Feb 2, 2017 4:01:05 PM Host ovmsrv05 is not responding. It will stay in Connecting state for a grace period of 80 seconds and after that an attempt to fence the host will be issued.</div><div>Feb 2, 2017 4:01:05 PM VDSM ovmsrv05 command failed: Connection reset by peer</div><div><br></div><div>Thanks</div><div>Gianluca</div></div><br></div></div>