Bug 1261419 - Proper message should be reflected in cron logs while trying to acquire lock for snapshot creation when gluster_shared_storage is stopped.
Proper message should be reflected in cron logs while trying to acquire lock ...
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot (Show other bugs)
3.1
x86_64 Unspecified
unspecified Severity low
: ---
: ---
Assigned To: rjoseph
storage-qa-internal@redhat.com
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-09 05:44 EDT by Shashank Raj
Modified: 2017-03-25 12:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Shashank Raj 2015-09-09 05:44:20 EDT
Description of problem:

Proper message should be reflected in cron logs while trying to acquire lock for snapshot creation when gluster_shared_storage is stopped


Version-Release number of selected component (if applicable):
glusterfs-3.7.1-14.el7rhgs.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Schedule a Job using snap_scheduler.py for creating snapshot at specific intervals
2. Stop the gluster shared volume
3. Observe that when the scheduled job starts, the cron log messages doesn't indicate the proper reason for the failure of it (snippet of logs below).

Sep  8 15:00:01 dhcp35-135 CROND[16705]: (root) CMD (PATH=$PATH:/usr/local/sbin:/usr/sbin gcron.py testvolume Job1)
Sep  8 15:00:01 dhcp35-135 CROND[16704]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Sep  8 15:00:01 dhcp35-135 CROND[16706]: (root) CMD (PATH=$PATH:/usr/local/sbin:/usr/sbin gcron.py --update)
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (Traceback (most recent call last):)
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (  File "/usr/sbin/gcron.py", line 188, in <module>)
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (    main())
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (  File "/usr/sbin/gcron.py", line 184, in main)
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (    doJob("Scheduled-" + jobname + "-" + volname, locking_file, takeSnap, volname))
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (  File "/usr/sbin/gcron.py", line 91, in doJob)
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (    f = os.open(lockFile, os.O_RDWR | os.O_NONBLOCK))
Sep  8 15:00:01 dhcp35-135 CROND[16698]: (root) CMDOUT (OSError: [Errno 107] Transport endpoint is not connected: '/var/run/gluster/shared_storage/sn
aps/lock_files/Job1')


Actual results:

Not what is expected.


Expected results:

it should reflect proper error message saying "failed to acquire the lock for snaphot creation"

Additional info:

Note You need to log in before you can comment on or make changes to this bug.