https://bugzilla.suse.com/show_bug.cgi?id=1181066 https://bugzilla.suse.com/show_bug.cgi?id=1181066#c10 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt@suse.com) | --- Comment #10 from Fabian Vogt <fvogt@suse.com> --- (In reply to Jos� Iv�n L�pez Gonz�lez from comment #8)
Fabian, could you please describe how to reproduce this bug? I understood that it happens in a live installer, but the bug is in yast2-update package, so it is not clear to me how to manage to reproduce it. Thank!
During the installation, sub-mounts of /run become invisible. In the live environment this manifests itself as "/run/user/1000/" appearing empty while the upgrade is in progress. It can be reproduced also outside of the live installer, by doing a submount manually: "mkdir -p /run/foo && mount -t tmpfs tmpfs /tmp/foo && touch /run/foo/bar". While the upgrade is running, "/run/foo" appears empty. (I did not actually try this). live-net-installer starts YaST in a separate mount namespace to workaround this, so I can't actually tell for sure whether YaST still does the double mount. More generally, that /run is mounted into the target system at all is also an issue. It means the RPM transaction (e.g. scriptlets and file actions) change /run of the running system. Can be reproduced by making sure "/run/utmp" exists in the inst-sys before an upgrade from 42.x to TW starts. After aaa_base got upgraded, it's gone from the inst-sys. With systemd this crashes logind (boo#1187971) -- You are receiving this mail because: You are on the CC list for the bug.