Description of problem:

'snap_scheduler.py init' returns incorrect error message when cronie package is not installed in the system. This is seen during rhgs container testing where chronie package is not installed by default. Refer: 1305764

Version-Release number of selected component (if applicable):
# cat /etc/redhat-storage-release 
Red Hat Gluster Storage Server 3.1 Update 2 ( Container)

# rpm -qa |grep glusterfs
glusterfs-libs-3.7.5-16.el7rhgs.x86_64
glusterfs-client-xlators-3.7.5-16.el7rhgs.x86_64
glusterfs-fuse-3.7.5-16.el7rhgs.x86_64
glusterfs-geo-replication-3.7.5-16.el7rhgs.x86_64
glusterfs-3.7.5-16.el7rhgs.x86_64
glusterfs-api-3.7.5-16.el7rhgs.x86_64
glusterfs-cli-3.7.5-16.el7rhgs.x86_64
glusterfs-server-3.7.5-16.el7rhgs.x86_64

How reproducible: Always


Steps to Reproduce:
1. Try running # snap_scheduler.py init in a system where chronie package is not installed by default
2.
3.

Actual results: 'snap_scheduler.py init' returns incorrect error when cronie package is not installed in the system

#####
# snap_scheduler.py init              
snap_scheduler: Another snap_scheduler command is running. Please try again after some time.

From snap_scheduler.log:

[2016-02-09 07:32:18,739 snap_scheduler.py:710 main] INFO /var/run/gluster/shared_storage/snaps/lock_files/lock_file is being processed by another agent.
[2016-02-09 07:40:16,628 snap_scheduler.py:710 main] INFO /var/run/gluster/shared_storage/snaps/lock_files/lock_file is being processed by another agent.
[2016-02-09 07:41:46,502 snap_scheduler.py:710 main] INFO /var/run/gluster/shared_storage/snaps/lock_files/lock_file is being processed by another agent.
[2016-02-09 07:42:03,157 snap_scheduler.py:710 main] INFO /var/run/gluster/shared_storage/snaps/lock_files/lock_file is being processed by another agent.
#####

Expected results: 'snap_scheduler.py init' should return a proper and relevant error message when it's pre-requisites are not met.


Additional info: