Comment # 5 on bug 954650 from Stakanov Schufter

I have some additional info, maybe of interest. 

I tried all available combinations of the install process and found out there
are some differences. 

a) default partitioning as proposed with btrfs xfs without lvm does work

b) default partitioning with ext4 as file system does work

c) default partitioning btrfs xfs clicking "modify proposal" selecting LVM
without encryption does fails with error 4013

d) default partitioning btrfs xfs clicking "modify proposal" selecting LVM with
encryption does fail with 4013 but interestingly in this proposal the "enlarge
swap for suspension" is greyed out and does not work. 

e) same as of above with EXT4 fails in the very same way, also here the enlarge
swap is inactive/greyed out. 

f) cancelling the default partitioning and choosing: create partition
configuration 

1) attributing the third disk entirely succeeds as mentioned before without LVM
(but messes with existing partitions if available).

2) attributing the third disk entirely choosing LVM with or without encryption
fails and furthermore, the enlarge swap is greyed out, and the size of /home is
wrongly set in the sense that without LVM it is set to the max space. With LVM
instead it is set to a quite arbitrary value of 50 GB if 90 are available,
100Gb when e.g. 190 are available. It can be corrected by resizing in expert
partitioning. But it will be irritating to a less experienced user because it
will not be modifiable through modify proposal of "create partition
configuration". In both cases 1) and 2) the install fails then with error -4013
at the end. 

g)The most curious case I had when attributing the second disk, without any
pre-existing partition.

First of all, it messes with the /boot of sda1 that it wants to format (by
default). 

With "create partitioning configuration" - use entire disk instead, (That is:
install to sdb with sdb1,sdb2(LVM without encryption)):  

If you attribute the second disk with "create partition configuration, use
entire disk", it will use sdb1/boot and sdb2/LVM as expected. There the
"enlarge swap" selection is possible, but, before even going on with the
install you get a pop up with the following error message: 
"impossible to set cypher. Error code -3014. Possible that the cypher password
is not correct." 
Now, this is curious, because it was a NOT encrypted LVM. And the existing
password of sda2 was accepted at the beginning of the process already and the
disk is visible. Moreover, the disc to install to (sdb), is empty, without any
pre-existing partition.

So whatever setup with LVM, with or without encryption does not seem to work
(at least in my case). 

Personally I am not in a hurry. I have a laptop with 13.2 that works and
Tumbleweed on the first disk. In order to report bugs I have now leap (although
not installed as I would do, intended for real use, but still). 
So for me at this point of time there is no "cata" if this is postponed to a
later point (as long as it is not "sine die"). 

Cheers.