iscsid.startup setting conflicts with systemd

Bug #1640422 reported by Yutani on 2016-11-09
This bug affects 4 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
open-iscsi (Ubuntu)

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+git0.3b4b4500-14ubuntu3.1

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in open-iscsi (Ubuntu):
status: New → Confirmed
Changed in open-iscsi (Ubuntu):
importance: Undecided → High
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → High
Yutani (hiroaki-yutani) wrote :

The attachment "fix-iscsid-startup.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Nish Aravamudan (nacc) wrote :


Can you clarify exactly what you are seeing?

a) the default conf file is /etc/iscsi/iscsid.conf not /etc/iscsid.conf (it moved at some point in the past)

b) systemctl is able to control iscsid.service just fine

Can you provide an exact command/test case to show what you mean as the issue?

Changed in open-iscsi (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers