LUKS on LV (LVM) reduces PV size after luksOpen lv ... !! Has anyone seen this?

Running Leap 42.2 and trying to setup LUKS over LVM, not LVM over LUKS.
I got this idea from https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#LUKS_on_LVM
where doing it this way allows one to use one vg, and choose which lv is encrypted but still have the benefits of LVM for non encrypted partitions.

The strange thing I experienced on Leap 42.2 was this:Original pv size is 1.7TB

Configured test lv #1-LUKS 500MB
Configured test lv #2 1000MB

**Once lv #1 was opened with

cryptsetup luksopen ...

the displayed PV size in YAST showed 500MB.**

I tested copying 800MB to lv #2 and sure enough I ran out of space at 500MB!

Because I did my initial attempt with YAST, I deleted the lvs, vg, pv, and partition, and did it all again from the command line. [Thank god for YAST!!]
But still I ran into this issue.

Has anyone tried LUKS over LVM on openSUSE before and seen this issue?

Is it sane to try to do what I am doing? Maybe I should go mainstream with LVM over LUKS for encrypted data, and put the non-encrypted data in it’s own LVM pv.

~ Gordon

Copy-paste your complete commands starting from the beginning and complete responses. The best is simply to record terminal session (e.g. running it under script).

arvidjaar,
Do you believe that running luks on logical volumes should work on Leap 42.2?