[Bugs] [Bug 1218060] [SNAPSHOT]: Initializing snap_scheduler from all nodes at the same time should give proper error message

[bugzilla at redhat.com]

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



--- Comment #1 from senaik at redhat.com ---
Same issue seen while checking snap_scheduler.py status from all nodes at the
same time 

Node1:
======
snap_scheduler.py status
snap_scheduler: Snapshot scheduling status: Disabled

Node2,Node3, Node4:
===================
 snap_scheduler.py status
Traceback (most recent call last):
  File "/usr/sbin/snap_scheduler.py", line 575, in <module>
    sys.exit(main())
  File "/usr/sbin/snap_scheduler.py", line 545, in main
    os.makedirs(LOCK_FILE_DIR)
  File "/usr/lib64/python2.6/os.py", line 157, in makedirs
    mkdir(name, mode)
OSError: [Errno 17] File exists:
'/var/run/gluster/shared_storage/snaps/lock_files/'

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