Sergei hi,

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.

Can you please open a bug with the logs ?

Also, to understand why LVM is not seeing your PV , can you run the following command and supply the ouput ?

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

Thanks,

Fred

On Tue, Jan 10, 2017 at 9:22 AM, Sergei Hanus <getallad@gmail.com> wrote:

Fred, sorry, my fault.
Now I have verified the contents.

Sergei.

On Mon, Jan 9, 2017 at 6:27 PM, Fred Rolland <frolland@redhat.com> wrote:
Sergei,

The files are empty, can you please resend ?

Thanks

On Mon, Jan 9, 2017 at 1:00 PM, Sergei Hanus <getallad@gmail.com> wrote:
Hi, Fred.
I'm using release 4.0.5.
I made a fresh redeploy today and reproduced the issue.

I'm attaching engine and vdsm log file, the time to look is around 12:15:13

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)

Appreciate any comments.

Sergei