[Bugs] [Bug 1207629] nfs-ganesha: feature.ganesha enable options fails

[bugzilla at redhat.com]

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



--- Comment #17 from Saurabh <saujain at redhat.com> ---
So after updating the trusted pool thing, 

I able to see that the cluster is up,

gluster features.ganesha enable
Enabling NFS-Ganesha requires Gluster-NFS to bedisabled across the trusted
pool. Do you still want to continue? (y/n) y
ganesha enable : success 
[root at nfs3 ~]# pcs status
Cluster name: ganesha-ha-1
Last updated: Fri Apr 10 12:37:14 2015
Last change: Fri Apr 10 12:37:09 2015
Stack: cman
Current DC: nfs3 - partition with quorum
Version: 1.1.11-97629de
2 Nodes configured
8 Resources configured


Online: [ nfs3 nfs4 ]

Full list of resources:

 Clone Set: nfs-mon-clone [nfs-mon]
     Started: [ nfs3 nfs4 ]
 Clone Set: nfs-grace-clone [nfs-grace]
     Started: [ nfs3 nfs4 ]
 nfs3-cluster_ip-1    (ocf::heartbeat:IPaddr):    Started nfs3 
 nfs3-trigger_ip-1    (ocf::heartbeat:Dummy):    Started nfs3 
 nfs4-cluster_ip-1    (ocf::heartbeat:IPaddr):    Started nfs3 
 nfs4-trigger_ip-1    (ocf::heartbeat:Dummy):    Started nfs3 

[root at nfs3 ~]# pcs config
Cluster Name: ganesha-ha-1
Corosync Nodes:
 nfs3 nfs4 
Pacemaker Nodes:
 nfs3 nfs4 

Resources: 
 Clone: nfs-mon-clone
  Resource: nfs-mon (class=ocf provider=heartbeat type=ganesha_mon)
   Operations: start interval=0s timeout=40s (nfs-mon-start-timeout-40s)
               stop interval=0s timeout=40s (nfs-mon-stop-timeout-40s)
               monitor interval=10s timeout=10s (nfs-mon-monitor-interval-10s)
 Clone: nfs-grace-clone
  Resource: nfs-grace (class=ocf provider=heartbeat type=ganesha_grace)
   Operations: start interval=0s timeout=40s (nfs-grace-start-timeout-40s)
               stop interval=0s timeout=40s (nfs-grace-stop-timeout-40s)
               monitor interval=5s timeout=20s (nfs-grace-monitor-interval-5s)
 Resource: nfs3-cluster_ip-1 (class=ocf provider=heartbeat type=IPaddr)
  Attributes: ip=10.70.36.217 cidr_netmask=32 
  Operations: start interval=0s timeout=20s
(nfs3-cluster_ip-1-start-timeout-20s)
              stop interval=0s timeout=20s (nfs3-cluster_ip-1-stop-timeout-20s)
              monitor interval=15s (nfs3-cluster_ip-1-monitor-interval-15s)
 Resource: nfs3-trigger_ip-1 (class=ocf provider=heartbeat type=Dummy)
  Operations: start interval=0s timeout=20 (nfs3-trigger_ip-1-start-timeout-20)
              stop interval=0s timeout=20 (nfs3-trigger_ip-1-stop-timeout-20)
              monitor interval=10 timeout=20
(nfs3-trigger_ip-1-monitor-interval-10)
 Resource: nfs4-cluster_ip-1 (class=ocf provider=heartbeat type=IPaddr)
  Attributes: ip=10.70.36.218 cidr_netmask=32 
  Operations: start interval=0s timeout=20s
(nfs4-cluster_ip-1-start-timeout-20s)
              stop interval=0s timeout=20s (nfs4-cluster_ip-1-stop-timeout-20s)
              monitor interval=15s (nfs4-cluster_ip-1-monitor-interval-15s)
 Resource: nfs4-trigger_ip-1 (class=ocf provider=heartbeat type=Dummy)
  Operations: start interval=0s timeout=20 (nfs4-trigger_ip-1-start-timeout-20)
              stop interval=0s timeout=20 (nfs4-trigger_ip-1-stop-timeout-20)
              monitor interval=10 timeout=20
(nfs4-trigger_ip-1-monitor-interval-10)

Stonith Devices: 
Fencing Levels: 

Location Constraints:
  Resource: nfs3-cluster_ip-1
    Enabled on: nfs4 (score:1000) (id:location-nfs3-cluster_ip-1-nfs4-1000)
    Enabled on: nfs3 (score:2000) (id:location-nfs3-cluster_ip-1-nfs3-2000)
    Constraint: location-nfs3-cluster_ip-1
      Rule: score=-INFINITY  (id:location-nfs3-cluster_ip-1-rule) 
        Expression: ganesha-active ne 1 
(id:location-nfs3-cluster_ip-1-rule-expr-1) 
  Resource: nfs4-cluster_ip-1
    Enabled on: nfs3 (score:1000) (id:location-nfs4-cluster_ip-1-nfs3-1000)
    Enabled on: nfs4 (score:2000) (id:location-nfs4-cluster_ip-1-nfs4-2000)
    Constraint: location-nfs4-cluster_ip-1
      Rule: score=-INFINITY  (id:location-nfs4-cluster_ip-1-rule) 
        Expression: ganesha-active ne 1 
(id:location-nfs4-cluster_ip-1-rule-expr-1) 
Ordering Constraints:
  start nfs3-trigger_ip-1 then start nfs-grace-clone (kind:Mandatory)
(id:order-nfs3-trigger_ip-1-nfs-grace-clone-mandatory)
  start nfs-grace-clone then start nfs3-cluster_ip-1 (kind:Mandatory)
(id:order-nfs-grace-clone-nfs3-cluster_ip-1-mandatory)
  start nfs4-trigger_ip-1 then start nfs-grace-clone (kind:Mandatory)
(id:order-nfs4-trigger_ip-1-nfs-grace-clone-mandatory)
  start nfs-grace-clone then start nfs4-cluster_ip-1 (kind:Mandatory)
(id:order-nfs-grace-clone-nfs4-cluster_ip-1-mandatory)
Colocation Constraints:
  nfs3-cluster_ip-1 with nfs3-trigger_ip-1 (score:INFINITY)
(id:colocation-nfs3-cluster_ip-1-nfs3-trigger_ip-1-INFINITY)
  nfs4-cluster_ip-1 with nfs4-trigger_ip-1 (score:INFINITY)
(id:colocation-nfs4-cluster_ip-1-nfs4-trigger_ip-1-INFINITY)

Cluster Properties:
 cluster-infrastructure: cman
 dc-version: 1.1.11-97629de
 no-quorum-policy: ignore
 stonith-enabled: false

-- 
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=gPUefTs7Ss&a=cc_unsubscribe