[Bug 1045396] New: [Build 20170620] openQA test fails in network_configuration - network.service is unknown
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396 Bug ID: 1045396 Summary: [Build 20170620] openQA test fails in network_configuration - network.service is unknown Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/426354/modules/networ k_configuration/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- ## 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/...) ## 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) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c1
--- Comment #1 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c2
Franck Bui
Then I tried to update the base disk image to 0620 directly - and that resulted in no network again (systemctl status network.service gives service unknown)
Just to make sure I understand the current issue: if you upgrade from 13.1 to 0620 directly (which includes systemd v233), /etc/systemd/system/network.service symlink is missing and "systemctl show -pId network.service" fails ? If so do you still have the rpm logs of this upgrade ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c3
--- Comment #3 from Dominique Leuenberger
Just to make sure I understand the current issue: if you upgrade from 13.1 to 0620 directly (which includes systemd v233), /etc/systemd/system/network.service symlink is missing
yes, that link is missing
and "systemctl show -pId network.service" fails ?
Sadly, no.. systemctl show -pId ENOTEXIST.service Id=ENOTEXIST.service systemctl returns success on non-existing services -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c4
--- Comment #4 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c5
--- Comment #5 from Franck Bui
(currently only have disk images with 0619 and and that one dup'ed further to 0620 - the situation that worked; but I can easily recreate the 0620-from-13.1 situation)
I'm trying to reproduce here with: http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-oss-i586-x86_64-S... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c7
--- Comment #7 from Franck Bui
( 612/1932) Installing: wicked-service-0.6.40-1.2 [....done] Additional rpm output: /usr/bin/systemctl: /lib64/libdevmapper.so.1.03: version `DM_1_02_97' not found (required by /usr/lib64/libcryptsetup.so.4) /usr/bin/systemctl: /lib64/libdevmapper.so.1.03: version `DM_1_02_97' not found (required by /usr/lib64/libcryptsetup.so.4) /usr/bin/systemctl: /lib64/libdevmapper.so.1.03: version `DM_1_02_97' not found (required by /usr/lib64/libcryptsetup.so.4) /usr/bin/systemctl: /lib64/libdevmapper.so.1.03: version `DM_1_02_97' not found (required by /usr/lib64/libcryptsetup.so.4) systemctl: /lib64/libdevmapper.so.1.03: version `DM_1_02_97' not found (required by /usr/lib64/libcryptsetup.so.4) /etc/init.d/network is disabled, can't find any another service enabled as the network.service.
So basically systemctl is broken at that point... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c8
--- Comment #8 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c9
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c10
--- Comment #10 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c11
--- Comment #11 from Dominique Leuenberger
Option 1 (a small hack): have libcryptsetup4 conflict with device-mapper < 1.02.97
has been tested and seemed not to work neither to get a more suitable order of installs -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c12
--- Comment #12 from Michael Andres
(In reply to Dominique Leuenberger from comment #9)
Option 1 (a small hack): have libcryptsetup4 conflict with device-mapper < 1.02.97
has been tested and seemed not to work neither to get a more suitable order of installs
If libcryptsetup4 requires device-mapper >= 1.02.97, device-mapper should be installed before, unless you have cyclic deps, then it depends on where the cycle is broken up. (the conflict does not influence the order). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c13
--- Comment #13 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c14
--- Comment #14 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396#c15
--- Comment #15 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1045396
zhen ren
participants (1)
-
bugzilla_noreply@novell.com