https://bugzilla.novell.com/show_bug.cgi?id=231077 ------- Comment #5 from rsarraf@netapp.com 2007-01-11 06:07 MST ------- Yes, you're correct that ocfs2 has really nothing to do with it. The init scripts of ocfs2 and o2cb also just show a "Should-Start" dependency on open-iscsi. There's nothing odd in the pre/post installation scripts of the ocfs2 RPMs which would be changing the order. Doing just an installation of the ocfs2 RPMs (supplied by SLES10) doesn't create this bug. This bug is only seen (the order being changed) when the user does a configuration of cluster services using ocfs2 following the docs available at: http://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2_users_guide.pd... If ocfs2 configuration is the culprit which is modifying the boot order _internally_, it still is an ocfs2 related issue which breaks other services of the OS. -- 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, or are watching someone who is.