Comment # 22 on bug 1217029 from Fabian Vogt

(In reply to Thomas Blume from comment #21)
> (In reply to Thomas Blume from comment #20)
> > (In reply to Fabian Vogt from comment #16)
> > > 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.
> > 
> > With the hint in comment#19 I could reproduce the issue on my local openQA
> > setup.
> > But unlike in the original test, where there is a timeout:
> > 
> > [2024-05-16T08:17:58.087198Z] [info] [pid:80064] ::: basetest::runtest: #
> > Test died: command 'systemd-run -tM node1 /bin/bash -c "zypper lr -u"' timed
> > out at /usr/lib/os-autoinst/testapi.pm line 926.
> >   	testapi::assert_script_run("systemd-run -tM node1 /bin/bash -c \"zypper
> > lr -u\"") called at opensuse/lib/networkdbase.pm line 28
> > 
> > 
> > The log shows that the systemd-run command returns with failure:
> > 
> > -->
> > [2024-06-04T11:11:21.773323Z] [info] [pid:1987] ::: basetest::runtest: #
> > Test died: command 'systemd-run -tM node1 /bin/bash -c "zypper lr -u"'
> > failed at /usr/lib/os-autoinst/testapi.pm line 926.
> >   	testapi::assert_script_run("systemd-run -tM node1 /bin/bash -c \"zypper
> > lr -u\"") called at opensuse/lib/networkdbase.pm line 28
> > --<
> > 
> > Not sure what makes this difference.
> > Investigating further.
> 
> systemd-run -tM node1 /bin/bash -c "zypper lr -u"
> 
> fails on my test setup due to a pty allocation error.

It's possible you're testing a snapshot with broken systemd: bsc#1225943

Maybe try an older snapshot where the original issue occurs.