Bug 1094771

Summary: Zypper dup stalls: 'org.freedesktop.systemd1': timed out
Product: [openSUSE] openSUSE Distribution Reporter: Carlos Robinson <carlos.e.r>
Component: Upgrade ProblemsAssignee: systemd maintainers <systemd-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: abittner, fbui
Version: Leap 15.0   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper dup output
partial message log, some commands

Description Carlos Robinson 2018-05-27 10:50:32 UTC
Created attachment 771469 [details]
zypper dup output

Hi,

I'm upgrading a virtual machine via zypper dup, from 15.0 beta to final (other people had the same problem on real iron). I get this issue:

(522/829) Installing: open-iscsi-2.0.876-lp150.8.2.x86_64
........................................................[done]
Additional rpm output:
Failed to reload daemon: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Failed to reload daemon: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

for every package since some point.

This is a virtual machine of no importance, but other people have hit the same issue on real iron and mentioned it on the mail list. I have paused the machine and took a snapshot so that you can investigate. Or I can send you the entire virtual machine if you wish.
Comment 1 Carlos Robinson 2018-05-27 10:52:17 UTC
Created attachment 771470 [details]
partial message log, some commands

See the attached p and p1 files for some more info.
Comment 2 Carlos Robinson 2018-05-27 10:54:29 UTC
This is probably a systemd issue, but I see no systemd component in Bugzilla.
Comment 3 Tomáš Chvátal 2018-05-28 09:27:50 UTC
*** Bug 1094762 has been marked as a duplicate of this bug. ***
Comment 4 Franck Bui 2018-05-28 13:52:58 UTC
Already reported.

*** This bug has been marked as a duplicate of bug 1094762 ***