[Bugs] [Bug 1209112] New: [Snapshot] Scheduler should display error message when shared storage is not mounted on node, when checking snap_scheduler.py status

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 6 08:32:37 UTC 2015


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

            Bug ID: 1209112
           Summary: [Snapshot]  Scheduler should display error message
                    when shared storage is not mounted on node,  when
                    checking snap_scheduler.py status
           Product: GlusterFS
           Version: pre-release
         Component: snapshot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: ashah at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

When shared storage volume is not mounted on one of the storage node, and if
you check the snap_scheduler.py status on that particular node, it shows
"snap_scheduler: Snapshot scheduling status: Disabled"  even if its enabled on
other storage nodes

Version-Release number of selected component (if applicable):

[root at localhost upsteam_build]# snap_scheduler.py status
snap_scheduler: Snapshot scheduling status: Enabled
[root at localhost upsteam_build]# rpm -qa | grep glusterfs
glusterfs-fuse-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-rdma-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-libs-3.7dev-0.910.git17827de.el6.x86_64
samba-glusterfs-3.6.509-169.4.el6rhs.x86_64
glusterfs-api-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-geo-replication-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-cli-3.7dev-0.910.git17827de.el6.x86_64
glusterfs-server-3.7dev-0.910.git17827de.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Create 2*2 distributed replicate volume
2. create shared storage and mount on each storage node
3. run snap_scheduler.py init  command on each storage node
4. run snap_scheduler.py enable on single storage node
5  unmount shared storage volume on one of the storage node
6 Check snap_scheduler.py status on each storage node

Actual results:

snap_scheduler.py status shows disable on storage node where shared storage is
not mounted. 

Expected results:

Scheduler should display message shared storage is not mounted.

Additional info:


[root at localhost upsteam_build]# gluster v info

Volume Name: meta
Type: Distributed-Replicate
Volume ID: bb7646be-8096-4cb1-a836-6d8c7ef7a075
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.47.143:/rhs/brick2/mb1
Brick2: 10.70.47.145:/rhs/brick2/mb2
Brick3: 10.70.47.150:/rhs/brick2/mb3
Brick4: 10.70.47.151:/rhs/brick2/mb4
Options Reconfigured:
auto-delete: disable
snap-max-soft-limit: 90
snap-max-hard-limit: 256

Volume Name: vol0
Type: Distributed-Replicate
Volume ID: 176c3b9a-6f08-434e-bc35-c4ef20dd0bcf
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.47.143:/rhs/brick1/b1
Brick2: 10.70.47.145:/rhs/brick1/b2
Brick3: 10.70.47.150:/rhs/brick1/b3
Brick4: 10.70.47.151:/rhs/brick1/b4
Options Reconfigured:
features.barrier: disable
auto-delete: disable
snap-max-soft-limit: 90
snap-max-hard-limit: 256

-- 
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