<div dir="ltr"><div>Sergei hi,<br><br>In the log, I can see that there is an issue in the VDSM code when parsing your PV due to the ":" in its name.<br><br></div><div>Can you please open a bug with the logs ?<br></div><div><br></div><div>Also, to understand why LVM is not seeing your PV , can you run the following command and supply the ouput ?<br></div><div></div><div><div><br><br>lvm pvs -vvvv --config ' devices { preferred_names = ["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ '\''a|/dev/mapper/SioFABRICVicinity_iqn.2015-03.com.iofabric:ovirt-master-00|'\'', '\''r|.*|'\'' ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } ' --noheadings --units b --nosuffix --separator '|' --ignoreskippedcluster -o uuid,name,size,vg_name,vg_uuid,pe_start,pe_count,pe_alloc_count,mda_count,dev_size /dev/mapper/SioFABRICVicinity_iqn.2015-03.com.iofabric:ovirt-master-00<br><br></div><div>Thanks,<br><br></div><div>Fred<br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 10, 2017 at 9:22 AM, Sergei Hanus <span dir="ltr"><<a href="mailto:getallad@gmail.com" target="_blank">getallad@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">Fred, sorry, my fault.<div>Now I have verified the contents.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div> Sergei.</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 9, 2017 at 6:27 PM, Fred Rolland <span dir="ltr"><<a href="mailto:frolland@redhat.com" target="_blank">frolland@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><div>Sergei,<br><br></div>The files are empty, can you please resend ?<br><br></div>Thanks<br></div><div class="m_-7480653123439221585HOEnZb"><div class="m_-7480653123439221585h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 9, 2017 at 1:00 PM, Sergei Hanus <span dir="ltr"><<a href="mailto:getallad@gmail.com" target="_blank">getallad@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 class="m_-7480653123439221585m_-2444350253526264177HOEnZb"><div class="m_-7480653123439221585m_-2444350253526264177h5"><div dir="ltr"><div class="gmail_extra"><div class="gmail_extra" style="font-size:12.8px">Hi, Fred.</div><div class="gmail_extra" style="font-size:12.8px">I'm using release 4.0.5.</div><div class="gmail_extra" style="font-size:12.8px">I made a fresh redeploy today and reproduced the issue.</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">I'm attaching engine and vdsm log file, the time to look is around 12:15:13</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">Also, when I try to delete storage domain from engine - it also returns error, so, this domain seems to be stuck in configuration (it is also displayed at the end of engine log)</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">Appreciate any comments.</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">Sergei</div></div></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>