Description of problem:
GNBD, for the most part, relies upon GULM to handle cluster membership
and fencing. If it is going to do that, it needs to wait until GULM
is in a quorate state on startup to ensure that in the event of a node
failure that it is properlly fenced. Without gulm in a quorate state,
the GNBD resources can start up in a split brain scenario which could
lead to data loss or corruption.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start lock_gulmd only on a single node
2. Start gnbd_export
gnbd_export is able to export block devices in non-cached mode
gnbd_export should wait until GULM is quorate before it allows block
devices to be exported
We decided that the init scripts were an acceptable way to solve this
bug for this release, so I'm closing it out.