![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1217029 https://bugzilla.suse.com/show_bug.cgi?id=1217029#c16 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|santiago.zarate@suse.com |systemd-maintainers@suse.de --- Comment #16 from Fabian Vogt <fvogt@suse.com> --- I had a look as well. Meanwhile it's the networkd_init module that fails: https://openqa.opensuse.org/tests/4194179#step/networkd_init/48 systemd-run -tM node1 /bin/bash -c "zypper lr -u" does not return. While it appears like zypper got stuck, this is not the case. The zypper process finishes successfully (visible in logs) and inside the container it also reports that the run-uNR.service unit finished. So it appears to be the communication issue indicated by comment 1. -- You are receiving this mail because: You are on the CC list for the bug.