Comment 2 for bug 1570580

This is conflict with previous bug reports. So originally / earlier in xenial release cycle we were shipping udev rules to automatically activate all discovered LVM groups and volumes. This then resulted in disk drives to be already in use, and failure to e.g. dasdfmt a dasd drive. There was no way to deactivate existing bug reports. My understanding was that there is / was a d-i way to pressed or activate all the available volume groups, I shall double check that. At the moment, I am inclined to say it is more important to keep the use-case "wipe any old install, install with new partitioning layouts", where old install may or may not have lvm based installation.

Are you performing manual installations, or are you preseeding automated installations and want to reuse lvm groups/volumes? If you are automating this advance setup I highly recommend to add relevant shell commands in partman/early_command as described in the installation guide at https://help.ubuntu.com/16.04/installation-guide/s390x/apbs05.html#preseed-hooks

Why is this bug report filed at severity-high? Has hws signed-off on this? "bugproxy" is not really authorised to open bug reports at severity high, they should be escalated to high, via PM coordination between hws and lou.

We are effectively past final freeze now, thus everything from now on should be filed as targetmilestone-inin1610, with expectation that it can only be SRUed into xenial.