Bug 661401

Summary: open-iscsi: systemd requires init scripts with different names (it strips the "boot." prefix)
Product: [openSUSE] openSUSE 12.1 Reporter: Duncan Mac-Vicar <dmacvicar>
Component: BasesystemAssignee: Thomas Fehr <fehr>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P1 - Urgent CC: aj, auxsvr, coolo, fcrozat, hare, lmuelle, per, RBrownCCB
Version: RC 1Flags: coolo: SHIP_STOPPER+
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.4   
Whiteboard:
Found By: Community User Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: dmesg

Description Duncan Mac-Vicar 2010-12-24 15:38:27 UTC
Login into the desktop as a user fails because ConsoleKit. It gets fixed after doing "systemctl start dbus.service" and login again.

Same happens with network.
Comment 1 Kay Sievers 2010-12-24 16:51:33 UTC
D-Bus can not even be disabled or configured with systemd. There seems something seriously wrong on that box.

Please try:
  rpm -e --nodeps systemd systemd-sysvinit
and check that there is nothing left in /etc/systemd/ /lib/systemd/ that isn't from other packages. /etc/systemd/ should be almost empty.

Then please install the factory systemd version again.

If that does not change anything, please remove:
  quiet
from the kernel commandline and add:
  systemd.log_level=debug systemd.log_target=kmsg
and paste the output of:
  dmesg
here.

Thanks!
Comment 2 Duncan Mac-Vicar 2010-12-25 17:39:15 UTC
Happened also on another laptop and workstation. Same effect. No network and no dbus.

systemd-sysvinit is not installed in this box.

I checked and all files belong to a package. Some to two, for example dbus.service belongs to dbus-1-32bit as well.

I will try rebooting and setting the loglevel
Comment 3 Duncan Mac-Vicar 2010-12-25 20:07:37 UTC
Created attachment 406250 [details]
dmesg

dmesg with debug enabled
Comment 4 Kay Sievers 2010-12-25 20:34:40 UTC
Any chance to de-install the iscsi stuff and try again? It might be that it has broken/invalid LSB headers which need to be fixed:

systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Walked on cycle path to sockets.target/start
systemd[1]: Walked on cycle path to dbus.socket/start
systemd[1]: Walked on cycle path to sysinit.target/start
systemd[1]: Walked on cycle path to open-iscsi.service/start
systemd[1]: Walked on cycle path to basic.target/start
systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start
Comment 5 Kay Sievers 2010-12-25 21:04:38 UTC
Seems the two identical init script names conflict with each other:
  $ rpm -ql open-iscsi | grep 'init\.d'
  /etc/init.d/boot.open-iscsi
  /etc/init.d/open-iscsi

Systemd strips the "boot." to compose the service name.
Comment 6 Kay Sievers 2010-12-25 21:18:57 UTC
Hannes, we need to rename one of the open-iscsi init scripts to have a different name.

Systemd strips the "boot." to compose the service name and we currently have:
  /etc/init.d/boot.open-iscsi
  /etc/init.d/open-iscsi
Comment 7 Duncan Mac-Vicar 2010-12-26 10:05:30 UTC
How does iscsi affects dbus and network here? :-)
Comment 8 Kay Sievers 2010-12-26 14:24:16 UTC
Systemd can not properly compose the graph of dependencies and throws out components until it has no cycles anymore.

We might be able to be smarter here, and not throw basic services out of the graph.

For now, deactivating the 'open-iscsi' service should make it work, until we renamed one of the init scripts, or found a way to work around the issue in systemd.
Comment 9 Duncan Mac-Vicar 2010-12-26 17:01:47 UTC
I wonder why I have iscsi on my system at all :-/
Comment 10 Hannes Reinecke 2011-01-10 13:13:09 UTC
Maybe we should get rid of the 'open-' prefix as well and rename the services to

/etc/init.d/iscsid

and

/etc/init.d/boot.iscsid-early

D'accord?
Comment 11 Kay Sievers 2011-01-10 13:31:13 UTC
Yeah, that sounds good to me.

At the moment we introduce native systemd files the issue will go away, but for now changing the name would be great.
Comment 12 Michal Vyskocil 2011-01-14 12:51:02 UTC
*** Bug 664514 has been marked as a duplicate of this bug. ***
Comment 13 Kay Sievers 2011-02-16 00:01:32 UTC
Hannes, mind renaming the script(s)?
Comment 14 Frederic Crozat 2011-10-24 13:20:30 UTC
ok, we are hit again by this bug (see bnc#725951)

It would be great to rename either both or just boot.open-iscsi (and patch yast-iscsi-client to use the right name) for openSUSE 12.1
Comment 15 Frederic Crozat 2011-10-24 13:21:13 UTC
*** Bug 725951 has been marked as a duplicate of this bug. ***
Comment 16 Duncan Mac-Vicar 2011-10-25 08:25:24 UTC
Assigning to Thomas, however this needs a simultaneous fix from Hannes.
Comment 17 Thomas Fehr 2011-10-25 10:12:25 UTC
Changing names in yast2-iscsi-client does not make sense unless
names on open-iscsi are changed. Reassigning to Hannes.
Comment 18 Frederic Crozat 2011-10-25 14:57:39 UTC
*** Bug 725915 has been marked as a duplicate of this bug. ***
Comment 19 Andreas Jaeger 2011-10-27 09:39:39 UTC
I've changed this now as suggested in comment #10. Thomas, could you change yast2-iscsi-client as well, please?

Submit request #89501 to devel project done.

This is needed for openSUSE 12.1, please submit asap.
Comment 20 Bernhard Wiedemann 2011-10-27 11:00:08 UTC
This is an autogenerated message for OBS integration:
This bug (661401) was mentioned in
https://build.opensuse.org/request/show/89507 Factory / open-iscsi
Comment 21 Thomas Fehr 2011-10-27 11:29:58 UTC
Did needed changes to yast2-iscsi-client.
RPM version is yast2-iscsi-client-2.21.8
Submit request to Factory is 89534
Comment 22 Bernhard Wiedemann 2011-10-27 12:00:08 UTC
This is an autogenerated message for OBS integration:
This bug (661401) was mentioned in
https://build.opensuse.org/request/show/89534 Factory / yast2-iscsi-client
Comment 23 Swamp Workflow Management 2018-04-12 10:03:08 UTC
This is an autogenerated message for OBS integration:
This bug (661401) was mentioned in
https://build.opensuse.org/request/show/595936 Factory / yast2-iscsi-client