Comment # 13 on bug 1137748 from Franck Bui

(In reply to Hubert Mantel from comment #12)
> I think we might see multiple issues here. Shutting down taking several
> minutes sounds like a systemd issue to me. I know that several other people
> also observed this.
> 

Again I don't see how you came to this conclusion. In fact systemd is not
involved at all when the actual suspend process starts, only the kernel is.

> Not powering off the system via suspend to RAM might be a kernel issue.
> 
> The network being non-functional after suspend from hibernate I do not know.
> And even after restarting the network manually after resume leads to virtual
> machines no longer being reachable.

Unless you're using systemd-networkd, which I doubt, your network is most
likely managed by either wicked or NM.

> So to me it boils down to not being able to use suspend at all. This is a
> clear regression as it has been working for years on Leap 42.3.

Sure and I don't dispute that.

> I'm suspending the system by simply clicking on the mini applet in the lower
> right corner of the task bar in KDE.

Can you try to suspend your system with ?

  # echo -n mem >/sys/power/state