ocfs2 startup link prior to open-iscsi

This is a tough call, since ocfs2 can also be used on FC hardware, which doesn't need a network connection to share storage. However, given that ocfs2 requires the network to do the clustered locking and communication via o2cb, it makes sense to put its init scripts into runlevel 2, IMO.

The same things can be done about drbd8-utils ( /etc/rc2.d/S70drbd ) before ocfs2 stuffs

However the update-rc.d script about ocfs2 and o2cb raise some warning about non LSB conformant issues.

Ex:
~# update-rc.d ocfs2 defaults 90 05
update-rc.d: warning: ocfs2 start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (2 3 5)
update-rc.d: warning: ocfs2 stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none)

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

I have no idea why you claim the 3 listed items are not provided, they in fact have been.

1. install ofcs2-tools (apt-get install ofcs2-tools)
2. it should work, including after reboots
3. reread first post, it doesn't work after reboots due to startup order

Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Fix Released' to current development
release as the issue does not apply to it any longer.

If you disagree or have new information, we would be grateful if
you could please open a new bug mentioning new affected versions with
a possible reproducer in the bug description.