Comment # 97 on bug 1094762 from andreas bittner

Woot ;) i have a repro! Sigh...

with that iso image 
comment 87 / 94

#boo1094762#c94
#boo1094762#c87

first to write down my thoughts briefly:
timestamp: around exactly 13:59.00 CEST to be able to find this later in the
logs

package (install) number 760 was systemd. took long and gave immediately
afterwards those 250000000ms timeout...

... few packages later package number 774 was some other package trying to talk
to systemd and brought the same timeouts 2500000000000000ms ;)

it is still ongoing.

Details:

simple seasobed (dualcore) amd64 based machine, single ata disk (think it is
even parallel ata even)

what i did: install this iso:
sha256sum  openSUSE-Leap-15.0-DVD-x86_64-Build206.1-Media.iso
c38df426959dc69475090f0567ce6661826266f7095d3127e30aac19fdc859c3 
openSUSE-Leap-15.0-DVD-x86_64-Build206.1-Media.iso

boot this .iso from usb stick. select install. have no network (ethernet cable
unplugged) connected.

configure network for ethernet interface (during install time) to later be dhcp
both ipv4 and ipv6

cable not connected while installing this 206.1.iso

install on whole disk, partition /swap (2gig), / = 40gig, /home (rest, some
hundred gigs)

go for ext4 filesystem for / and /home

i unselected some bloat stuff like huge packages libreoffice, k3b and whatnot.
nothing special.

kde plasma type of install (desktop).

added one single testuser/test123 during install, and same password for root.

let it install and complete the whole process. no troubles seen here.

boot the installed 206.1 machine (still no network cable).

takes a while as wicked tries to start the network and waits for dhcp probably
or something.

log into the kde desktop with the testuser/test123

open a single Konsole there (via alt+f2, konsole)

plug in the ethernet cable now, can ping6 and ping various stuff, networking
works.

all the default repos that come via the default install, so 15-oss, 15-non-oss,
15-update-oss, 15-update-nonoss or these things

leave these default repos.

su -

I then applied that

systemd-analyze set-log-level debug

command and then continued. I didnt set kernel variables for crashes or
something, as you guys said it wasnt about crashes.

then:
switch to root
screen -d -R 
there

create some subterminals or whatever they are called (ctrl+a, c, several times)

inside the screen, one of the created subterminals (whatever the naming) do

zypper ref --force

zypper dup --download-in-advance

I created a second tab in Konsole, by clicking next to the single existing tab
(where the su - session is being shown inside), and stayed as default testuser,
and only went for a watch -n 1 date, to be able to tell when select packages
and stuff happens inside the other Konsole tab in the zypper progress......

that was all... first it fetched all the packages (around 16xx), then it did
the file check, then it started the dup process....

at package 760, systemd main package was being handled.... immediately after
that one (already this one), the timeouts about 250xxxxxxxxms were shown....

some few packages later, another affected package (udevd or something).... was
showing the same effects.....


---------------

now what?
i hope someone can very much the same way repro this stuff again.
in fact, i will just try to do this very same procedure over once more to see
if the outcome is the same.......

any more hints? requests?