<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Feb 21, 2017 at 4:17 PM, Arman Khalatyan <span dir="ltr"><<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I found in my vdsm.log something like this what does it means??<br><br>2017-02-21 14:12:17,719 INFO (upgrade/995d385) [storage.StorageDomain] Resource namespace 03_lvm_995d3855-70a0-49aa-<wbr>9370-65c5139bd129 already registered (blockSD:988)<br>2017-02-21 14:12:17,777 ERROR (upgrade/995d385) [storage.StoragePool] Unhandled exception (utils:371)<br>Traceback (most recent call last):<br> File "/usr/lib/python2.7/site-<wbr>packages/vdsm/utils.py", line 368, in wrapper<br> return f(*a, **kw)<br> File "/usr/lib/python2.7/site-<wbr>packages/vdsm/concurrent.py", line 180, in run<br> return func(*args, **kwargs)<br> File "/usr/lib/python2.7/site-<wbr>packages/vdsm/storage/<wbr>securable.py", line 79, in wrapper<br> return method(self, *args, **kwargs)<br> File "/usr/share/vdsm/storage/sp.<wbr>py", line 232, in _upgradePoolDomain<br> self._<wbr>finalizePoolUpgradeIfNeeded()<br> File "/usr/lib/python2.7/site-<wbr>packages/vdsm/storage/<wbr>securable.py", line 77, in wrapper<br> raise SecureError("Secured object is not in safe state")<br>SecureError: Secured object is not in safe state<br></div></blockquote><div><br></div><div>This is a known issue during upgrade domain flow, It should be harmless</div><div>and not related to your issue.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">2017-02-21 14:12:17,822 INFO (tasks/4) [storage.ThreadPool.<wbr>WorkerThread] FINISH task 9a5fc120-fd33-48fb-968a-<wbr>06824a178e4f (threadPool:210)<br>2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus(taskID=u'<wbr>9a5fc120-fd33-48fb-968a-<wbr>06824a178e4f', spUUID=None, options=None) (logUtils:49)<br>2017-02-21 14:12:19,202 INFO (jsonrpc/5) [dispatcher] Run and protect: getTaskStatus, Return response: {'taskStatus': {'code': 0, 'message': '1 jobs completed successfully', 'taskState': 'finished', 'taskResult': 'success', 'taskID': '9a5fc120-fd33-48fb-968a-<wbr>06824a178e4f'}} (logUtils:52)<br><br><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 21, 2017 at 3:06 PM, Arman Khalatyan <span dir="ltr"><<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thank you Nir for the suggestion, but unfortunately I cannot find the resize button at all... :(<br></div><div>Shout be the storage in maintenance or in use?<br></div><div><img src="cid:ii_izflr8mh1_15a60fd4fb8ebe19" height="524" width="561"><br><br></div></div></blockquote></div></div></div></div></blockquote><div><br></div><div>The resize button should be in the "Additional size" column when a LUN</div><div>can be resized.</div><div><br></div><div>Vdsm reports the size of each LUN and the size of the PV. If the LUN</div><div>and the PV can be resized you should see the button.</div><div><br></div><div>Nir</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div><br></div><div><br><br><br></div><br></div><div class="m_8454996957440483323HOEnZb"><div class="m_8454996957440483323h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 20, 2017 at 10:07 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Mon, Feb 20, 2017 at 11:54 AM, Arman Khalatyan <span dir="ltr"><<a href="mailto:arm2arm@gmail.com" target="_blank">arm2arm@gmail.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"><div dir="ltr"><div><div><div><div>Hi,<br></div>I just have 1TB iscsi storage with virtual machine with several disks.<br></div>After shutdown the vm I just detached storage and removed from the cluster and ovirt totally.<br></div>1) Then on the target resized the exported volume to 13TB, <br>2) iscsiadm -m node -l on the host I resized <br>iscsiadm -m node -l<br>pvresize /dev/mapper/.....<br>iscsiadm -m node -u<br><br></div><div>After importing back to the ovirt over the gui, I can see the vm is in the import field but I cannot see separate disks <br></div><div>Importing failing in the stage "Executing".</div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>are there way to fix it?<br></div><div>On the host with "lvs" I can see the disks are there.<br></div></div></blockquote><div><br></div></span><div><div>Hi Arman,</div><div><br></div><div>You don't need to remove storage from ovirt to resize a LUN, and you don't need</div><div>to resize the pv, we can do this for you.</div><div><br></div><div>To resize a LUN:</div><div><br></div><div>1. Resize the LUN on the storage server<br></div><div>2. Open the "manage domain", dialog</div><div>3. Select the LUN and click the "resize" button in the table</div><div> (we should detect the new size and display button suggesting to add 11T)</div><div>4. Click "OK"</div><div><br></div><div>The system will make sure all hosts see the new size of the LUN, and then</div><div>it will resize the PV for you, and update engine database with the new LUN</div><div>size.</div><div><br></div><div>Now, in your case, we don't have any information about the issue, but if</div><div>you restart vdsm on the SPM host your issue may be resolved.</div><div><br></div><div>If not, please attach engine and vdsm logs.</div><span class="m_8454996957440483323m_7887108961746218990HOEnZb"><font color="#888888"><div><br></div><div>Nir</div><div><br></div></font></span></div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>