bnc#902086 is marked as fixed, but the fix did not make it into 13.2 (or, to be more precise, the 13.2 install medium/repo), correct?
I'm asking because what I see is that 1. Once I add an <add-on> section to my 13.2 profile, the installation grinds to a halt. 2. The fix for #902086 isn't in /usr/lib/systemd/system/YaST2-Second-Stage.service outside the chroot. 3. When I add the fix for #902086 as a workaround pre-script to my profile to change /usr/lib/systemd/system/YaST2-Second-Stage.service outside the chroot and re-include my <add-on> section in the profile, the problem still occurs, that is, the installation grinds to a halt. 4. When I try to add the fix to the chroot, either as postpartitioning-script or chroot-script with chrooted=false, the problem still occurs. (The postpartitioning-script seems to be too early, the chroot-script too late.)
: It stops during the step "Performing installation", showing an empty package list pane and empty "Actions performed" pane. The upper progress bar says "Adding entry for mount point / to /etc/fstab" (which finishes sucessfully AFAICT, but the message isn't changed to reflect what the current step really is) and the lower, "Installing packages" progress bar halts at or somewhere near the 27% mark, depending on the specifics of my AutoYAST profile. When I wait some time between 15 and 60 minutes (I did not time this), YaST (y2base) is killed with an OOM.
I'm going to fall back to the 13.1 workaround for bnc#846011 that we used, which manually adds the add-ons later.
Before I report this as a new bug or add it to bnc#902086: Has anybody encountered this issue? (Joschi: Your <remove-packages> workaround doesn't work for me either. )c; )