osa-dispatcher service can not be started after migration from SUSE Manager 3.2 to 4.1

This document (000019830) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager Server 3.2
SUSE Manager Server 4.1

Situation

osa-dispatcher service can not be started after migration with following error message:

● osa-dispatcher.service - OSA Dispatcher daemon
   Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2021-01-12 16:15:31 CET; 14s ago
  Process: 8466 ExecStart=/usr/sbin/osa-dispatcher --pid-file /var/run/osa-dispatcher.pid (code=exited, status=1/FAILURE)
  Process: 8465 ExecStartPre=/bin/rm -f /var/run/osa-dispatcher.pid (code=exited, status=0/SUCCESS)
 Main PID: 2823 (code=killed, signal=TERM)

Jan 12 16:15:30 somehostname systemd[1]: Starting OSA Dispatcher daemon...
Jan 12 16:15:31 somehostname osa-dispatcher[8466]: SUSE Manager 8466 2021/01/12 16:15:31 +02:00: ('Traceback caught:',)
Jan 12 16:15:31 somehostname osa-dispatcher[8466]: SUSE Manager 8466 2021/01/12 16:15:31 +02:00: ('Traceback (most recent call last):\n  File "/usr/lib/py>
Jan 12 16:15:31 somehostname osa-dispatcher[8466]: sys:1: ResourceWarning: unclosed <socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOC>
Jan 12 16:15:31 somehostname systemd[1]: osa-dispatcher.service: Control process exited, code=exited status=1
Jan 12 16:15:31 somehostname systemd[1]: Failed to start OSA Dispatcher daemon.
Jan 12 16:15:31 somehostname systemd[1]: osa-dispatcher.service: Unit entered failed state.
Jan 12 16:15:31 somehostname systemd[1]: osa-dispatcher.service: Failed with result 'exit-code'.

in osa-dispatcher log file (/var/log/rhn/osa-dispatcher.log) you can see following Traceback:

2021/01/12 16:15:31 +02:00 8466 0.0.0.0: osad/jabber_lib.connect('ERROR', 'Traceback (most recent call last):\n  File "/usr/lib/python3.6/site-packages/osad/jabber_lib.py", line 661, in connect\n    ssl.do_handshake()\n  File "/usr/lib/python3.6/site-packages/OpenSSL/SSL.py", line 1806, in do_handshake\n    self._raise_ssl_error(self._ssl, result)\n  File "/usr/lib/python3.6/site-packages/OpenSSL/SSL.py", line 1546, in _raise_ssl_error\n    _raise_current_error()\n  File "/usr/lib/python3.6/site-packages/OpenSSL/_util.py", line 54, in exception_from_error_queue\n    raise exception_type(errors)\nOpenSSL.SSL.Error: [(\'SSL routines\', \'tls_process_server_certificate\', \'certificate verify failed\')]\n')

Resolution

Make sure that the hostname (FQDN) and the IP address of target system are matching the hostname and IP address of source system as noticed at the end of the migration process:

Migration complete.
Please shut down the old SUSE Manager server now.
Reboot the new server and make sure it uses the same IP address and hostname
as the old SUSE Manager server!
 
IMPORTANT: Make sure, if applicable, that your external storage is mounted
in the new server as well as the ISO images needed for distributions before
rebooting the new server!

Cause

IP address and hostname mismatch between the source (SUSE Manager 3.2) and target system (SUSE Manager 4.1).

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.