http://bugzilla.opensuse.org/show_bug.cgi?id=1045396 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- 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#c2 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com --- Comment #2 from Franck Bui --- (In reply to Dominique Leuenberger from comment #1)

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#c4 --- Comment #4 from Dominique Leuenberger --- (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) -- 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 --- Reproducing here...I can see this from the logs:

( 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#c9 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |libzypp --- Comment #9 from Dominique Leuenberger --- I see two valid ways out of it, one seemingly a bit 'hacky', the other one introducing a cycle which we could only hope that zypp breaks it up at the right point Option 1 (a small hack): have libcryptsetup4 conflict with device-mapper < 1.02.97 option 2: have libdevmapper1_03 conflict with device-mapper < %{version} Option 1 is obviously tailored at exactly this issue seen, there might be other libs suffering from the same fallout at any point in time Option 2: is already implemented, but zypp seems not to handle the installation of the two pckages in a timely fashion to have the system is a broken state as short as poossible (II'd expect the two to be updated alongside) @zypp folkgs: did I miss something? (moving off systemd's queue - systemd is only the poor messener that broke) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045396 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |zypp-maintainers@forge.prov | |o.novell.com -- 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 #11)

(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#c14 --- Comment #14 from Dominique Leuenberger --- Hm.. but libcryptsetup4 does not require device-manager at all and that would be totally wrong in any case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1045396 zhen ren changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tchvatal@suse.com, | |zren@suse.com -- You are receiving this mail because: You are on the CC list for the bug.