iscsid.startup setting conflicts with systemd
Bug #1640422 reported by
Yutani
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Confirmed
|
High
|
Unassigned | ||
open-iscsi (Ubuntu) |
Incomplete
|
High
|
Unassigned |
Bug Description
iscsid automatically starts when an iscsi tool needs to access it. But after the iscsid process started up with the default setting in /etc/iscsid.conf, commands to control iscsid via systemd will fail since the process is NOT under control of iscsid.service. The default is this:
iscsid.startup = /sbin/iscsid
I believe the bellow should be the default if we stand on systemd.
iscsid.startup = /bin/systemctl start iscsid.service
I am using Ubuntu 16.04.1, kernel 4.4.0-38-generic.
Package: open-iscsi
Version: 2.0.873+
Changed in open-iscsi (Ubuntu): | |
importance: | Undecided → High |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.