http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c1 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmarek@novell.com |hare@novell.com --- Comment #1 from Michal Marek <mmarek@novell.com> 2010-08-12 09:46:46 UTC --- Dennis, you should SLES issues via the SLES support channels, not in the openSUSE bugzilla. Reassigning to Hannes nevertheless. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c3 --- Comment #3 from Dennis Olsson <DOlsson@WEB.de> 2010-08-12 21:05:07 CEST --- Yes, this is exactly the case here. Sorry that my bug reporting was not as clear as I thought. The problem is: (1) Doing as described in the SLES 11 SP1 documentation, i.e. - Setting the "node.startup" to "automatic", - Adding "nofail" option to the file system options in "/etc/fstab" for the file system found on the iSCSI disk(s), I end up with a system that boots, but is unusable, while the "/data" iSCSI file system has not been mounted. The iSCSI disk has been attached to the system (by "open-iscsi"), but the "/data" file system has not been *checked* nor *mounted*. I.e. using the "nofail" option on the "/data" file system in "/etc/fstab" only prevents the system from not booting at all, but it does not ensure that the system ends up in a usable state (in my case neither "nfsserver" nor "autofs" works correctly -- not even if "/data" is being manually mount after having booted up, except if "nfsserver" and "autofs" is stopped, "/data" mounted, restarting "autofs" and "nfsserver"). This is *not* the way the usage of iSCSI disks should be used! .-) (2) Doing as one would except the world to work (and as described above in comment #0 under "The correct way of handling iSCSI attached devices are"), i.e. - Setting the "node.startup" to "onboot", - Adding the "/data" file system as normal, just like when using a local disk to the "/etc/fstab", results in a non bootable system, while during the file system checking "fsck" cannot find the "/data" file system disk at all, and thus ending up in the "(repair filesystem)" shell prompt. As I wrote in comment #0, iSCSI based systems that need file systems to be mounted during the boot up sequence have to attached to the booting system during the execution of "boot.open-iscsi" using "node.startup" set to "onboot", allowing for these file systems to be checked and mounted by "boot.localfs". Just think what would happen to a system, if you have a "/" on a local disk and "/usr" on an iSCSI disk => Non bootable system. Using "automatic" only ensures that an iSCSI target gets attached to the system, but cannot be incorporated/used for normal mount points, simply because the attachment of the iSCSI targets happens far too late the in the booting sequence. The "automatic" setting is useful for iSCSI disks that are used by e.g. databases that are being started rather late in the boot sequence, but is absolutely *not* usable for iSCSI disks holding normal mounted file systems. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c4 --- Comment #4 from Dennis Olsson <DOlsson@WEB.de> 2010-08-13 11:08:59 CEST --- Reply to comment #1:

Dennis, you should SLES issues via the SLES support channels, not in the openSUSE bugzilla. Reassigning to Hannes nevertheless.

Michal, thanks, yes, I am aware of this. Have just first reported it here, while (1) the issue also affects openSUSE 11.3+, and (2) while I am must more familiar with the usage of Bugzilla (is far more easier to use;-) than with Novell's proprietary Support Requests. ;-) Issue was reported today as: Service Request: 10642695911 Description: Server refuses to boot, while used iSCSI based non "/" file system is not available. -- Configure bugmail: http://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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c6 --- Comment #6 from Hannes Reinecke <hare@novell.com> 2010-08-31 14:18:18 UTC --- I've been doing some tests here, and the 'udevmountd' service did indeed mount the device. Sadly, the 'block' device only, so multipath would refuse to run there. To fix this we need to update multipath-tools and sysconfig. multipathd from multipath-tools needs to be patched to emit a 'change' event for block devices whenever it's finished processing. This event can then be parsed by udevmountd, which then will know if it should try to check/mount the block device or if it's claimed by multipath. If the latter we can skip the fsck/mount step as we'll be getting a new multipath device eventually. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c8 --- Comment #8 from Hannes Reinecke <hare@novell.com> 2010-08-31 14:34:17 UTC --- Created an attachment (id=386539) --> (http://bugzilla.novell.com/attachment.cgi?id=386539) udevmountd-multipath-handling Patch to 'sysconfig' to allow mounting of multipath devices. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c10 Dennis Olsson <DOlsson@WEB.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|DOlsson@WEB.de | --- Comment #10 from Dennis Olsson <DOlsson@WEB.de> 2010-09-15 16:44:17 CEST --- Although I currently cannot test on SLES 11 SP1 (my XEN guest first needs to be upgraded, which I currently cannot do), I have tried to test on the running SLES 11 GM with all updates using the PTFs Stefan Bogner supplied me with: kpartx-0.4.8-40.19.1.1889.0.PTF.638468.x86_64.rpm multipath-tools-0.4.8-40.19.1.1889.0.PTF.638468.x86_64.rpm sysconfig-0.71.14-12.9.1.1889.0.PTF.638468.x86_64.rpm mkinitrd-2.4-49.10.1 Having installed these, rerun "mkinitrd" and rebooted, the system still refuses to boot, while the iSCSI devices are not attached to the system. Which does not surprises me, while the problem is that the "mkinitrd" still cannot figure out that it has to activate iSCSI during the booting up of "initrd". Also tried to update to (from SLES 11 SP1): module-init-tools-3.11.1-1.3.5.x86_64.rpm mkinitrd-2.4.1-0.11.1.x86_64.rpm but this did not change anything (yes, I did rerun "mkinitrd")! As a note, after having finished the "initrd" booting, it finishes with: .. System Boot Control: The system has been set up Skipped features: boot.open-iscsi boot.cycle which very clearly informs you that iSCSI has *not* been started nor that any iSCSI devices have been attached. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c12 --- Comment #12 from Dennis Olsson <DOlsson@WEB.de> 2010-09-15 17:20:19 CEST --- An additional note to comment #10: When doing the testing, I noticed that during a shutdown "open-iscsi" is called *before* any of the file systems used over iSCSI have been unmounted, resulting in having these file systems end up in an undefined state by the next start up. Not especially smart. By changing "/etc/init.d/open-iscsi" to have: # Required-Stop: $remote_fs $network the system is able to shutdown correctly. The problem is that the mounted file systems over iSCSI are being used by "autofs" resp. "nfsserver". By adding "$remote_fs", it is ensured that "open-iscsi" is executed after these services have been stopped, enabling "open-iscsi" to unmount its partitions before logging out from the iSCSI server. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c14 --- Comment #14 from Hannes Reinecke <hare@novell.com> 2010-09-20 17:04:25 UTC ---

The problem is just that "open-iscsi" is started *after* "boot.localfs", which means that "fsck" bails out, while the file systems from the iSCSI devices (in my case "/data" and "/home") are not available.

For which we have the option 'nofail' to avoid a failure here. The devices will then be mounted via udev. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c17 --- Comment #17 from Hannes Reinecke <hare@novell.com> 2010-09-27 08:29:46 UTC --- Hmm. Yes, you are correct, the 'nofail' option will not work for systems with any system directories (like /var or /usr) on iSCSI when root is _not_ on iSCSI. And I'm equally sure there is no way we can fix this without major restructuring. Reason being that network is started in runlevel 3 (and higher) only, and iscsi requires the network to run. So moving iscsi to the 'boot' runlevel is a no-go. On the other hand 'mkinitrd' considers the root fs _only, and as iSCSI is not required to get the root fs up and running it won't be including it. Of course we might be able to update mkinitrd to include iSCSI setup in these cases, but then the iSCSI setup might be more complicated than just a single connection to a single target, in which case we're bound to fail. So to make this work we need first to update mkinitrd to handle more than one network connected and then update mkinitrd to include iSCSI when /var or /usr is on iSCSI. But this is _not_ something we can do for an already released product. Sorry. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Ihno Krumreich <ihno@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium InfoProvider|ihno@novell.com |jw@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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c22 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|jw@novell.com |maintenance@opensuse.org --- Comment #22 from Marius Tomaschewski <mt@novell.com> 2011-01-06 10:33:22 UTC --- Mr Maintenance, the update will go out via multipath swampid 37050 for SLE-11-SP1. I've submitted it to git for 11.4 already and preparing for factory. What about 11.3? -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c24 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #24 from Marius Tomaschewski <mt@novell.com> 2011-01-11 14:40:12 UTC --- OK. Submitted package to 11.3: 57886 State:new By:mtomaschewski When:2011-01-11T15:31:18 submit: home:mtomaschewski:branches:openSUSE:11.3:Update:Test/sysconfig -> openSUSE:11.3:Update:Test Descr: SWAMPID 37050: fixes for bnc#630434 and bnc#660774 and added patchinfo. The other fixes (comment 21) are already released on 11.3 via SWAMPID 37959. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c26 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 | |maint:released:11.3:38138 --- Comment #26 from Swamp Workflow Management <swamp@suse.com> 2011-01-13 12:31:06 UTC --- Update released for: sysconfig, sysconfig-debuginfo, sysconfig-debugsource Products: openSUSE 11.3 (debug, i586, x86_64) -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c28 Shawn Starr <shawn.starr@rogers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |shawn.starr@rogers.com Resolution|FIXED | --- Comment #28 from Shawn Starr <shawn.starr@rogers.com> 2011-01-19 07:14:55 UTC --- Can I get some additional clarification: There seems to be TWO problems here: 1) Mounting system filesystems /var /home /usr - breaks with mkinitrd - Fine, you've documented that above but that is for that use case only. 2) mounting non-system or non-root '/' filesystems breaks - This is still not fixed. I have hit this problem with OpenSuSE 11.x and SLES 11 SP1, trying to mount a data partition (let's call it /somedata). Worse, even if I use /dev/disk/by-id or by-uuid in /etc/fstab, fsck fails and brings to emergency root login. telling open-iscsi to use 'automatic' doesn't work either. I use nofail to at least get the machine booted, but this isn't very good. So, is what you are saying is what USED to work in OpenSuSE 10.x/SLES 10.x no longer works in SLES 11 SP1 or in OpenSuSE? It sounds like I'm going to have to write an initscript wrapper, that will parse /etc/fstab, grab the uuid/by-id device name and mount it explicitly after network and open-iscsi has attached disk. This doesn't seem fully resolved, reopening to get attention. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c29 --- Comment #29 from Dennis Olsson <D.Olsson@Netzwerk-Design.de> 2011-09-14 13:40:24 CEST --- A work-around to fix the issue with not getting "onboot" configured iSCSI sessions attached during system boot up, when root is not on an iSCSI device, is to make use of the overriding feature of "mkinitrd" (only documented in the sources) by creating the file "/etc/sysconfig/initrd" containing the setting of "root_iscsi=1". See attached template of how a "/etc/sysconfig/initrd" could look like. Please, be aware of the bug in "mkinitrd" (bug 717590) that prevents the overriding feature to work correctly, although this bug does not prevent the feature of setting "root_iscsi=1" from working. After having set "root_iscsi=1" in "/etc/sysconfig/initrd", all you need is to rerun "mkinitrd" to get an "initrd" that will attach all "onboot" configured iSCSI sessions during system boot up. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Dennis Olsson <D.Olsson@Netzwerk-Design.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #450674|application/octet-stream |text/plain mime type| | -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c32 --- Comment #32 from Dennis Olsson <D.Olsson@Netzwerk-Design.de> 2011-09-14 14:56:49 CEST --- Created an attachment (id=450697) --> (http://bugzilla.novell.com/attachment.cgi?id=450697) Patch fixing missing inclusion of iSCSI stack, when having "onboot" configured iSCSI sessions. Attached patch for "open-iscsi-2.0.871-0.29.1" contains patching of "/etc/init.d/open-iscsi" & "/lib/mkinitrd/scripts/setup-iscsi.sh" and the removal of "/etc/init.d/boot.open-iscsi". This patch fixes the original reported problem (see comment 0) -- just as it makes the work-around described in comment 29 above unnecessary -- by changing the logic in "/lib/mkinitrd/scripts/setup-iscsi.sh" to look for all iSCSI devices / sessions that have their start up configured to "onboot" ("node.conn[0].startup = onboot") and when at least one is found ensures that "mkinitrd" includes the iSCSI session attachment of these during system boot up in "initrd". The patch also removes "/etc/init.d/boot.open-iscsi", while as far as I could see during my testing, this script is a NOOP script that is always either skipped (while the iSCSI was already loaded by "initrd") or fails (while it cannot start the "/sbin/iscsid" daemon, because the necessary kernel modules have not been loaded). Granted, I have not tested the case, where iSCSI is being used during the install, where the script might be of usage (see also comment 33 below). -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c34 --- Comment #34 from Dennis Olsson <D.Olsson@Netzwerk-Design.de> 2011-09-28 15:23:05 CEST --- Issue was reopened in Novell Support Center under Service Request: 10724107481 Description: Server refuses to boot, while used iSCSI based non "/" file system is not available. requesting subject to be handled in time for SLES 11 SP2 as well as an update to SLES 11 SP1. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c37 --- Comment #37 from Dennis Olsson <D.Olsson@Netzwerk-Design.de> 2011-10-10 14:46:17 CEST --- Well, yes, I thought that might be the case. I do not have a setup, where I am using root on an iSCSI device, and thus was unsure whether "boot.open-iscsi" would be kicking in these cases (assumed so, though;-), and have now been confirmed that it is so). The reasons for the suggested alternative changes (opposed to the removal of "boot.open-iscsi") in comment 33 is that in my test cases, the unconditional call of "startproc $DAEMON $ARGS" in "boot.open-iscsi" resulted in this script bailing out, while the iscsi daemon ($DAEMON) is already running at this point in time! Using the suggested patch, though, would ensure that the daemon only gets started in cases, where it is really not running, just as it ensures that "boot.open-iscsi" is capable of continue running its "start" section to the end without bailing out too early. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Lee Duncan <lduncan@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |DOlsson@WEB.de -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c42 --- Comment #42 from Lee Duncan <lduncan@novell.com> 2012-03-27 12:00:11 PDT --- Dennis: it does not look like the openSUSE 11.3 open-iscsi package is supported any longer. Are you looking for an 11.3 fix for this, or are you willing to move to a newer version of openSUSE? It looks like 11.4 is still supported. As for the mkinitrd and template changes, I believe I will fork them of as a separate bug. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c44 --- Comment #44 from Lee Duncan <lduncan@novell.com> 2012-04-03 15:06:52 PDT --- Dennis: I have looked at bug 717590, and I believe that we should also break out another part of this bug as a separate issue: I believe that mkinitrd template should be a separate bug. And I believe this current bug should depend on that new bug and on 717590. I believe I have the open-iscsi part of this bug fixed. Would you like a patch for the open-iscsi source package for SLES 12 SP2 GM? -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c46 Dennis Olsson <DOlsson@WEB.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |717590 --- Comment #46 from Dennis Olsson <DOlsson@WEB.de> 2012-04-04 21:07:35 CEST --- Lee, As requested, I have created bug 755748 to handle the "initrd" template, and made this bug depend on this bug and on 717590. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c48 --- Comment #48 from Lee Duncan <lduncan@novell.com> 2012-04-05 10:29:13 PDT --- (In reply to comment #45)

Well, I do not any longer have access to an iSCSI environment, but I would like to give the sources a review (I just cannot test in a live environment presently).

For SLES 12 SP2 GM??? I do believe, you mean SLES 11 SP2 GM, right?

My apologies: I was off-by-one. Yes, I meant SLES 11 SP2 GM. Note: I am trying to reproduce this problem to verify your suggested changes, and I am not having luck. Perhaps you can hep me. Here's what I'm doing: * Created an iSCSI target volume on a remote system * Set up my SLE 12 SP2 GM client with open-iscsi * Made sure client could connect to target * Created a filesystem on the target disc from the client (EXT3) * Set node.startup and node.conn[0].startup to "onboot" * Updated /etc/init.d/boot.open-iscsi and /etc/init.d/open-iscsi as you suggested * added your suggested initrd template and ran mkinitrd When I reboot, the /etc/init.d/boot.open-iscsi service finds no sessions, since it appears to not have logged into the target. And when I get up full running (after /etc/init.d/open-iscsi has ran), the session still is not present, i.e. no login has been attempted to my target! If I change the "startup" variables to "automatic" instead of "onboot", then I get automatic login to the target, so when I get to full multi-user mode, the disk is present (in my case, as /dev/sdc). So why is this not working when I set startup to "onboot", i.e. who/what is supposed to login to the target when its startup value is set to onboot? Is it initrd? Do I need to make changes to initrd itself? -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c50 --- Comment #50 from Lee Duncan <lduncan@novell.com> 2012-04-09 17:00:59 PDT --- I found my problem. I created a /etc/sysconfig/initrd file, and I set root_iscsi=1 and ADDITIONAL_FEATURES="iscsi" at first. But then the network was not getting loaded, so I added "network" to the list of additional features. I also updated the mkinitrd script itself, as per your suggestion. Now, when I reboot, my "/data", which is my iSCSI volume, is mounted at boot time, as desired. I will update this bug soon with my patches for boot.open-iscsi and open-iscsi, so they are captured. After that, work on SLES will resume when L3 status confirmed. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c52 --- Comment #52 from Lee Duncan <lduncan@novell.com> 2012-04-09 18:08:38 PDT --- Created an attachment (id=485399) --> (http://bugzilla.novell.com/attachment.cgi?id=485399) My setup-iscsi.sh patch for initrd My version of this patch differs from the bug filers since the script being patched has changed. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c54 --- Comment #54 from Dennis Olsson <DOlsson@WEB.de> 2012-04-15 16:20:58 CEST --- Having reviewed attachment id=485400 in comment 53, may I suggest that you change the line reading (now, where you are changing the line anyway.-): cat /proc/mounts | sed -ne '/^\/dev\/.*/p' | while read d m t o x; do to: sed -ne '/^\/dev\/.*/p' /proc/mounts | while read d m t o x; do instead. The use of "cat" is completely superfluous, using unnecessary resources (for no valid reasons). -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c61 --- Comment #61 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-01-11 00:00:11 CET --- This is an autogenerated message for OBS integration: This bug (630434) was mentioned in https://build.opensuse.org/request/show/147985 Maintenance / -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c65 --- Comment #65 from Lee Duncan <lduncan@suse.com> 2013-01-14 10:28:15 PST --- Here are the steps I used to test on all platforms: - apply patch - ensure open-iscsi is running - connect to remote target you want to mount - set node.conn[0].startup to "onboot" for that target - add an entry to /etc/fstab to mount that target (I used "/data"), and ensure options set to that it mounts at boot time (I used "auto,nofail"). The "no fail" ensures the boot will succeed even if the mount does not - set the defaults for mkinitrd in /etc/sysconfig/initrd, as per attached example - run "mkinitrd -v" (the "-v" is optional, but I like to see what is happening) - reboot You can tell if the patch worked if the iSCSI volume you want is mounted after reboot. In my case, /data was mounted after reboot, so the patch worked. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 |maint:released:11.3:38138 |maint:released:11.3:38138 |maint:released:sle11-sp1:37 |maint:released:sle11-sp1:37 |595 |595 maint:planned:update -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c68 Lee Duncan <lduncan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |751056 --- Comment #68 from Lee Duncan <lduncan@suse.com> 2013-01-21 15:31:54 PST --- The SP2 Update may be backed up behind a major open-iscsi version update for SP2. If that major version update occurs this patch will have to be ported, so it may make sense to block this until that other bug gets fixed. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c71 --- Comment #71 from Lee Duncan <lduncan@suse.com> 2013-03-14 14:08:22 PDT --- found this problem was not yet fixed in openSUSE 12.3 and openSUSE Factory, so changes submitted today for those two packages. Still blocked, but not for much longer, on SP2, by bnc#751056. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c74 --- Comment #74 from Swamp Workflow Management <swamp@suse.de> 2013-03-19 13:04:45 UTC --- openSUSE-RU-2013:0483-1: An update that has two recommended fixes can now be installed. Category: recommended (important) Bug References: 630434,766300 CVE References: Sources used: openSUSE 12.3 (src): open-iscsi-2.0.870-47.4.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.

https://bugzilla.novell.com/show_bug.cgi?id=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 |maint:released:11.3:38138 |maint:released:11.3:38138 |maint:released:sle11-sp1:37 |maint:released:sle11-sp1:37 |595 |595 |maint:running:52031:low | -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c76 --- Comment #76 from Lee Duncan <lduncan@suse.com> 2013-05-16 12:04:53 PDT --- Updated the patch for current SP2 open-iscsi. Tested that open-iscsi came up and worked on a normal (non-boot-time) target. Then, tested this patch as per Comment#65, i.e. with patch in place and open-iscsi up and running: - connected to remote target - set node.conn[0].startup to "onboot" for that target - added entry for that target in /etc/fstab with options "auto,nofail", then mounted it - set /etc/sysconfig/initrd to: ADDITIONAL_FEATURES="network iscsi" root_iscsi=1 - run "mkinitrd -v" - reboot And /data is mounted after boot. I will submit the updated SP2 patch today, then SP3 shortly after. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c79 --- Comment #79 from Lee Duncan <lduncan@suse.com> 2013-05-20 13:57:47 PDT --- Changes submitted to build service for SP3, request id 26423. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c81 --- Comment #81 from Lee Duncan <lduncan@suse.com> 2013-05-21 08:45:11 PDT --- The fix for this bug is integrated now in SP3, but still under review in SP2. So bug can remain open until an SP2 decision is made. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c88 --- Comment #88 from Lee Duncan <lduncan@suse.com> 2013-06-26 04:06:55 PDT --- I propose to *not* fix this in an SP2 update, since SP2 is more mature now than when this bug was filed, and consequently is not an appropriate place for a fix with as much risk as this fix has. Therefore, once this the submitted SP3 fix is accepted I will mark this bug as resolved. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c90 Lee Duncan <lduncan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |821695 --- Comment #90 from Lee Duncan <lduncan@suse.com> 2013-06-27 08:06:38 PDT --- The openSUSE fix for this will be merged into the openSUSE open-iscsi update (bnc#821695), so marking this bug as dependent on that one. When that one gets fixed, this bug will be complete. -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Bug 630434 depends on bug 821695, which changed state. Bug 821695 Summary: open-iscsi should be updated to latest version http://bugzilla.novell.com/show_bug.cgi?id=821695 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c93 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 |maint:released:11.3:38138 |maint:released:11.3:38138 |maint:released:sle11-sp1:37 |maint:released:sle11-sp1:37 |595 maint:running:52031:low |595 maint:running:52031:low |maint:planned:update | maint:running:56918:low --- Comment #93 from Swamp Workflow Management <swamp@suse.de> 2014-04-07 20:35:22 UTC --- The SWAMPID for this issue is 56918. This issue was rated as low. Please submit fixed packages until 2014-05-05. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/56918 -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c95 --- Comment #95 from SMASH SMASH <smash_bz@suse.de> 2014-04-22 14:41:04 UTC --- Affected packages: SLE-11-SP2: 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c97 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 |maint:released:11.3:38138 |maint:released:11.3:38138 |maint:released:sle11-sp1:37 |maint:released:sle11-sp1:37 |595 maint:running:52031:low |595 maint:running:52031:low | maint:running:56918:low | maint:running:56918:low |maint:planned:update |maint:released:sle11-sp3:57 | |014 --- Comment #97 from Swamp Workflow Management <swamp@suse.de> 2014-05-26 20:46:56 UTC --- Update released for: open-iscsi, open-iscsi-debuginfo, open-iscsi-debugsource Products: SLE-DEBUGINFO 11-SP3 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP3 (i386, x86_64) SLE-SERVER 11-SP3 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP3 (i386, x86_64) -- 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=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:38 |maint:released:sle11-sp1:38 |085 |085 |maint:released:11.3:38138 |maint:released:11.3:38138 |maint:released:sle11-sp1:37 |maint:released:sle11-sp1:37 |595 maint:running:52031:low |595 maint:running:52031:low | maint:running:56918:low | |maint:released:sle11-sp3:57 |maint:released:sle11-sp3:57 |014 |014 -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c99 --- Comment #99 from Bernhard Wiedemann <bwiedemann@suse.com> --- This is an autogenerated message for OBS integration: This bug (630434) was mentioned in https://build.opensuse.org/request/show/57457 Factory / sysconfig https://build.opensuse.org/request/show/57886 11.3:Test / sysconfig -- You are receiving this mail because: You are on the CC list for the bug.