https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c Ye Yuan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |mmarek@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c2 --- Comment #2 from Kai Lappalainen 2013-07-11 18:16:17 UTC --- Created an attachment (id=547624) --> (http://bugzilla.novell.com/attachment.cgi?id=547624) requested mkinitrd logfile -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c3 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lduncan@suse.com, | |mmarek@suse.com AssignedTo|mmarek@suse.com |hare@suse.com --- Comment #3 from Olaf Hering 2013-09-02 20:38:47 CEST --- I do not have an iscsi setup. But I suspect the bug is in the mkinitrd helpers contained in open-iscsi.rpm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c5 Lee Duncan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Lee Duncan 2013-09-06 19:48:16 PDT --- I manually logged into a remote iSCSI target, which became /dev/sdb. I set up an iSCSI volume to be mounted as /data from /dev/sdb1, with "noauto,nofail" set as the mount options, and mounted it. I then rebooted. No problems. The iSCSI target was not logged into because it had "manual" as the startup mode, and of course /data was not mounted. I *did* however find a problem when running "mkinitrd -v", as that did seem to include iscsi even though it should not be needed in this case. I will look into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c7 Kai Lappalainen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kl@httgmbh.net | --- Comment #7 from Kai Lappalainen 2013-09-10 23:37:26 UTC ---

From my understanding the bug ist in /lib/mkinitrd/setup/81-iscsi.sh in the check_for_node_onboot() function:

if [[ "${startup}" != "onboot" ]] ; then.... There is a note also: "## Note: could set "onboot" ourselves here, but that seems heavy-handed" Beware of setting "onboot" "ourselves"!!! If "onboot" is not set, then iSCSI should not be included by mkinitrd. Simple as that, no? If I would want a real boot-time iSCSI volume I would set "startup type" to "onboot". The 81-iscsi.sh script should respect the choosen "startup type". I want the iSCSI volume mounted automatically during system startup after normal network initialisation, but not during boottime from initrd, as indicated by not setting "onboot" startup value. This works perfectly as long as mkinitrd does not add iSCSI stuff and network drivers to initrd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c9 Lee Duncan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kl@httgmbh.net --- Comment #9 from Lee Duncan 2013-10-02 12:08:42 PDT --- Kai: It sounds like you believe there are two problems: - mkinitrd includes iscsi in the initrd image if there are any iSCSI volumes listed in /etc/fstab, and - mkinitrd scans for iSCSI volumes in /etc/fstab and warns if it sees any that do not have "onboot" set I agree this is broken. The idea was to scan for "important" iSCSI volumes listed in /etc/fstab, with the assumption that the user may not have correctly marked such volumes as "onboot", but that is indeed what they wanted. I think the solution is to stop scanning /etc/fstab in setup-iscsi.sh, since the script already scans system discs as well as all iSCSI nodes in the database. This would fix both of the problems listed above. I can supply a patch to test if you agree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c11 --- Comment #11 from Lee Duncan 2013-10-21 11:35:16 PDT --- (In reply to comment #10)

Lee, there is a third problem:

- mkinitrd scans only for iSCSI volumes if the iscsi daemon is running. It does not test, if the service is enabled which is IMHO also broken.

I agree with you that setup-iscsi.sh should stop scanning /etc/fstab.

Good.

Furthermore there should be a test if iscsid is actually enabled - running or not.

IMHO iscsi should only be included in the initrd image if:

- iscsi daemon is enabled (running or not while executing mkinitrd), and

- the configured volume is set "onboot"

I do not agree with this this new issue being a bug. The mkinitrd process is highly dependent on the current state of the system. For example, it only enables network devices that are configured at the time the initrd image is created. If you still feel this is a bug please file it as a separate issue (referencing this bug), and adding me on the cc list. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c13 --- Comment #13 from Lee Duncan 2013-12-12 11:57:21 PST --- Submitted to network/open-iscsi (i.e. Factory) as OBS sr request#210730. Submitted to openSUSE:12.3:Update as OBS new request#210734. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c15 --- Comment #15 from Bernhard Wiedemann 2013-12-12 23:00:13 CET --- This is an autogenerated message for OBS integration: This bug (826700) was mentioned in https://build.opensuse.org/request/show/210741 Factory / open-iscsi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=826700 https://bugzilla.novell.com/show_bug.cgi?id=826700#c17 --- Comment #17 from Swamp Workflow Management 2013-12-23 15:07:27 UTC --- openSUSE-RU-2013:1945-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 826700 CVE References: Sources used: openSUSE 12.3 (src): open-iscsi-2.0.873-47.18.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.