[Bugs] [Bug 1563500] New: nfs-ganesha: in case pcs cluster setup fails then nfs-ganesha process should not start

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1563500

            Bug ID: 1563500
           Summary: nfs-ganesha: in case pcs cluster setup fails then
                    nfs-ganesha process should not start
           Product: GlusterFS
           Version: 3.10
         Component: common-ha
          Keywords: Triaged
          Severity: urgent
          Priority: high
          Assignee: jthottan at redhat.com
          Reporter: jthottan at redhat.com
                CC: amukherj at redhat.com, asriram at redhat.com,
                    bugs at gluster.org, divya at redhat.com,
                    jthottan at redhat.com, kkeithle at redhat.com,
                    msaini at redhat.com, mzywusko at redhat.com,
                    nlevinki at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, sankarshan at redhat.com,
                    saujain at redhat.com, sheggodu at redhat.com,
                    skoduri at redhat.com, storage-qa-internal at redhat.com



+++ This bug was initially created as a clone of Bug #1226874 +++

Description of problem:
As per the new implementation for 3.1 that we are propsoing is HA by default
for nfs-ganesha server. The problem is that there have been cases when pcs
cluster setup has failed in some scenarios but the point to note is that
nfs-ganesha process has spawned on the nodes, whereas nfs-ganesha should also
not spawn in case pcs cluster setup has failed. Otherwise we are not providing
HA as default with the setup that we are doing

One of the example scenario is BZ 1225507, there may be others.

Version-Release number of selected component (if applicable):
glusterfs-3.7.0-2.el6rhs.x86_64
nfs-ganesha-2.2.0-0.el6.x86_64

How reproducible:
several times


Expected results:
We need to have a check that decides if the pcs cluster is up only then
nfs-ganesha should be spawned.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zDg7fmAT4W&a=cc_unsubscribe