[Bugs] [Bug 1395652] New: ganesha-ha.conf --status should validate if the VIPs are assigned to right nodes

bugzilla at redhat.com bugzilla at redhat.com
Wed Nov 16 11:05:58 UTC 2016


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

            Bug ID: 1395652
           Summary: ganesha-ha.conf --status should validate if the VIPs
                    are assigned to right nodes
           Product: GlusterFS
           Version: 3.8
         Component: common-ha
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: kkeithle at redhat.com
                CC: aloganat at redhat.com, amukherj at redhat.com,
                    asrivast at redhat.com, bugs at gluster.org,
                    jthottan at redhat.com, kkeithle at redhat.com,
                    rhinduja at redhat.com, rhs-bugs at redhat.com,
                    sashinde at redhat.com, skoduri at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1395539, 1395648, 1395649
            Blocks: 1351528, 1364410, 1393966, 1394815




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1364410
[Bug 1364410] [ganesha+gdeploy]: Validate status of HA cluster once ganesha
is enabled on the cluster.
https://bugzilla.redhat.com/show_bug.cgi?id=1393966
[Bug 1393966] gdeploy: Incorrect Console message when nfs-ganesha cluster
creation fails.
https://bugzilla.redhat.com/show_bug.cgi?id=1394815
[Bug 1394815] ganesha-ha.conf --status should check whether for all
services used in nfs-ganesha are running
https://bugzilla.redhat.com/show_bug.cgi?id=1395539
[Bug 1395539] ganesha-ha.conf --status should validate if the VIPs are
assigned to right nodes
https://bugzilla.redhat.com/show_bug.cgi?id=1395648
[Bug 1395648] ganesha-ha.conf --status should validate if the VIPs are
assigned to right nodes
https://bugzilla.redhat.com/show_bug.cgi?id=1395649
[Bug 1395649] ganesha-ha.conf --status should validate if the VIPs are
assigned to right nodes
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list