## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-13.1-gnome@64bit
fails in
[network_configuration](http://openqa.opensuse.org/tests/426354/modules/network_configuration/steps/7)


## Reproducible

Fails since (at least) Build
[20170620](http://openqa.opensuse.org/tests/425994)


## Expected result

Last good: [20170619](http://openqa.opensuse.org/tests/424720) (or more recent)


## Further details

Always latest result in this scenario:
[latest](http://openqa.opensuse.org/tests/latest?distri=opensuse&version=Tumbleweed&flavor=NET&machine=64bit&test=zdup-13.1-gnome&arch=x86_64)


## Further debugging

I did the entire upgrade scenario from 13.1 to TW (using the same base image
and repo) in a local VM - and it turns out 'network' is completely disabled
after this upgrade now.

one has to go to YaST / lan and re-enable networking, then it works again.

/usr/sbin/ifup uses the command

> systemctl --no-pager -p Id show network.service

to find out what is managing the network.

as 'network.service. does not actually exist on this setup, ifup might not only
treak 'wicked.service and "" as "do not abort", but actually also handle the
same code path for "network.service"

This issue definitively needs more analysis to find the difference between the
behavior in snapshot 0619 and 0620 (systemd is one of the base involved
components that was updated, hence assigning, for now, to systemd)