On 5/13/19 2:49 PM, Till Dörges wrote:
Am 11.05.19 um 13:00 schrieb Ludwig Nussel:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.1&build=468.7&groupid=50 https://bugzilla.opensuse.org/buglist.cgi?product=openSUSE%20Distribution&query_format=advanced&resolution=---&version=Leap%2015.1
I just tried 'zypper dup' for an existing Leap 15.0 system. No extra repos, just OSS and OSS Updates for Leap 15.1. The original 15.0 system was rather small (~ 800 RPMs).
'zypper dup' went okay up to
--- snip ---- (761/898) Installing: btrfsmaintenance-0.4.2-lp151.1.1.noarch .......<100%>[\] --- snap ---
Yes, there is some type of a race condition there or maybe some corner case. It was noticed last year already, but it's difficult to get reproducer, https://bugzilla.suse.com/show_bug.cgi?id=1110259
To me it appears as if
/usr/bin/systemctl try-restart btrfsmaintenance-refresh.service btrfsmaintenance-refresh.path btrfs-balance.service btrfs-balance.timer btrfs-defrag.service btrfs-defrag.timer btrfs-scrub.service btrfs-scrub.timer btrfs-trim.service btrfs-trim.timer
was waiting (indefinitely) for input on a pipe. After killing that systemctl, installation moved on, w/o any apparent problem.
Exactly. I've had this occur exactly 1 time in a VM and I've tried reproducing the issue and was unsuccessful. I also do not use btrfs.
Below is a bit more of my ad-hoc analysis. A quick Bugzilla search did not give me any hits.
Is this worth pursuing?
Yes :D - Adam -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org