Comment # 4 on bug 1123316 from Ancor Gonzalez Sosa

(In reply to Stefan Schubert from comment #3)
> Ancor I am not a storage expert, but as far I am remembering we have already
> had some issues/discussion about "naming". Could you please check this ?
> Thanks !

I don't think this is related at all to the recent problems with
yast-storage-ng and names. The code raising that warning does not use
yast-storage-ng or libstorage-ng at all.

See 
https://github.com/yast/yast-iscsi-lio-server/blob/830663122701ec3cb21b85a0b260fd1f757192f9/src/include/iscsi-lio-server/UI_dialogs.rb#L2713

That code uses the Ruby method File.ftype to ensure the path correspond to a
real, direct file. And /dev/vg/lvol is not a block special file, but a symlink
to one (i.e. File.ftype("/dev/vg/lvol") == "link").

It will work if the user introduces something like "/dev/dm-0" (to know the
exact file, check which /dev/dm-X is pointed by /dev/vg/lvol).

So this works as designed so far (accepting only the block special file and
complaining if a symlink is provided). Whether we want to teach
yast2-iscsi-lio-server to follow symlinks, that's another question.