Hi all,
I’ve been searching for two days for a solution, no luck yet. I’m trying to install a Leap 42.1 machine with autoyast and it’s supposed to be a RAID 1. I created a reference xml file from a different machine, modified it to my needs (actually not many changes as it’s supposed to be setup the same way except hostname, ip address and volume groups) and have tried several installations. The file is processed until the disk partitioning has to be done, where I always see the same message at the beginning:
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkCreateConstraints):453 increase:27392 current:0 num_pe:238466
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkCreateConstraints):493 ret:0
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] LvmVg.cc(doCreateVg):1261 ret:-4017
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] LvmVg.cc(commitChanges):1050 ret:-4017
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] Storage.cc(commitPair):5659 err at stage:1 type:LVM cont:true dest:false name:compute2
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [libstorage] Storage.cc(commitErrorPopupCb):7091 COMMIT ERROR POPUP error:-4017 last_action:Creating volume group compute2 (931.50 GiB) from /dev/md/compute2 extended_message:
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [Ruby] modules/StorageClients.rb:123 CommitErrorPopup error:-4017 last_action:Volume-Gruppe compute2 (931.50 GiB) wird aus /dev/md/compute2 erstellt extended_message:
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [Ruby] modules/StorageClients.rb:145 before getErrorString error:-4017
2016-09-09 09:20:39 <1> 192.168.160.13(3516) [Ruby] modules/StorageClients.rb:147 before getErrorString ret:LVM_PV_STILL_ADDED
LVM_PV_STILL_ADDED
If I simply confirm by clicking OK the installation finishes successfully. It seems like yast tries to create the volume group twice, because 6 seconds earlier the volume group is already created:
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] LvmVg.cc(doCreateVg):1213 Vg:compute2
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:libvirt-libxl target: map:</dev/md/compute2:5120>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:opt target: map:</dev/md/compute2:256>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:root target: map:</dev/md/compute2:512>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:swap target: map:</dev/md/compute2:512>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:tmp target: map:</dev/md/compute2:1792>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:usr target: map:</dev/md/compute2:5888>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:var target: map:</dev/md/compute2:512>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(checkConsistency):604 name:var-lib-nova target: map:</dev/md/compute2:12800>
2016-09-09 09:20:33 <1> 192.168.160.13(3516) [libstorage] PeContainer.cc(findPe):518 dev:/dev/md/compute2 ret:false
I tried several things to get rid of this message, but without success. I’m not sure if my autoinst.xml is somehow erroneous or if there’s a problem with yast. Can anyone point me to a solution? Because this is not how I imagine an automatic installation 
Please note, the rest of the installation works just fine, the final configuration after the first reboot finishes successfully, everything looks as expected, it’s only this one warning at the beginning of the installation.
If there is more information required to resolve this, I’d be happy to provide it.
Thanks in advance!