Bug 1380377

Description of problem:
osad saying that it's running even when it got SSLDisableError

Version-Release number of selected component (if applicable):
osad-5.11.44-10-sat

How reproducible:
always

Steps to Reproduce:
1. Modify /etc/sysconfig/rhn/up2date to get SSLDisableError (e.g. change FQDN to server IP address)
2. run service osad restart and check return code
3. run service osad status and check return code


If there is SSLDisabledError, return code of service osad restart is 0 and if you run service osad status you'll get:
[root@ibm-x3650m4-03-vm09 ~]# service osad status
osad (pid  29954) is running...
[root@ibm-x3650m4-03-vm09 ~]# echo $?
0

When you run service osad start on RHEL7 you wont get any traceback:
[root@localhost ~]# service osad start
Starting osad (via systemctl):                             [  OK  ]
[root@localhost ~]# echo $?
0
but when you run osad command it will print traceback
[root@localhost ~]# osad
Not able to reconnect - See https://access.redhat.com/solutions/45332 for possible solutions.

Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 253, in setup_connection
    c = self._get_jabber_client(js)
  File "/usr/share/rhn/osad/jabber_lib.py", line 320, in _get_jabber_client
    c.connect()
  File "/usr/share/rhn/osad/jabber_lib.py", line 606, in connect
    raise SSLDisabledError

Actual results:
service osad restart returns 0, even when there is SSLDisableError and service osad status says that it is running.

Expected results:
osad should't be running when there is SSLDisableError and service osad restart should return something else than 0