(In reply to andreas bittner from comment #43) > If you give me detailed instructions on how to set loglevels that will help > you, I have still that one unupgraded machine here, I need to do something > about it. If you want to enable systemd debug logs at runtime you can use "systemd-analyze set-log-level debug". > > I dont know though if the machine will be affected though. > > What comes to my mind maybe is, is it possible that non-rebooted machines > that e.g. had updates on 42.3 level (systemd and other stuff lately, not yet > replaced and activated all files in use, e.g. non rebooted yet) and then > going for a zypper dup with repositories swapped over to 15.0 URL addresses > Hmm is this scenario supported ? I mean should such upgrade are supposed to be done offline ? To answer your question I dont think it's related because Marcos seems to reproduce the issue when simply updating Leap15 Beta to Leap 15.0.