SaltStack Config / RAAS service reporting internationalization errors

Products

• VMware Aria Suite

Issue/Introduction

The purpose of this KB article  is to provide fix for the error listed above.

Symptoms:
RAAS service reporting error in the RAAS logs located in /var/log/rass/raas. Similar to below example: 

Traceback (most recent call last):
  File "tornado/web.py", line 1701, in _execute
    result = method(*self.path_args, **self.path_kwargs)
  File "/var/lib/raas/unpack/_MEI8CM2Ja/raas/mods/rest/vip_proxy.py", line 139, in get
    return self.process_proxy(requests.get)
  File "/var/lib/raas/unpack/_MEI8CM2Ja/raas/mods/rest/vip_proxy.py", line 102, in process_proxy
    r = request_method(
  File "requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "raven/breadcrumbs.py", line 341, in send
    resp = real_send(self, request, *args, **kwargs)
  File "requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='<IP>', port=8091): Max retries exceeded with url: /i18n/api/v2/locale/supportedLanguageList?productName=SSC&version=8.10.1&language= (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7xxxxxxxxfa0>: Failed to establish a new connection: [Errno 111] Connection refused'))
2023-01-23 08:45:45,076 [tornado.access][ERROR   :2246][Webserver:2573] 500 GET /i18n/api/v2/locale/supportedLanguageList?productName=SSC&version=8.10.1&language= (<IP>) 10.28ms

Environment

VMware Aria Automation Config 8.12.x

Cause

The error is due to "vmware internationalization service" is missing on the RAAS machine. This service came out as part of 8.6.2. In general SaltStack Config will run without it, but you will see a lot of errors in the logs. To fix the errors you need to install missing packages for Singleton service: 

• singleton-manager-i18n
• ssc-translation-bundle.

Resolution

Prerequisites:

JAVA_JRE 11 must be installed and configured on the system

To resolve the problem, follow the steps below:

1. Download RAAS installation package from  https://customerconnect.vmware.com/ that match your RAAS version , example: vRA_SaltStack_Config-8.10.2.4-1.el7_Installer.tar.gz
2. After extraction missing files you will find in the location: /sse-installer/salt/sse/eapi_service/files/ 

• singleton-manager-i18n-0.6.9-0.el7.x86_64.rpm
• ssc-translation-bundle-8.10.2-2.ph3.noarch.rpm

3. Copy installation files to RAAS node.
4. Login to RAAS node as root via SSH or console.
5. Install packages
   sudo yum install singleton-manager-i18n-0.6.9-0.el7.x86_64.rpm
   sudo yum install ssc-translation-bundle-8.10.2-2.ph3.noarch.rpm
6. After the package installation you can check the status of the service:
   systemctl status singleton-manager-i18n.service

Service is running OK you will see the following message :
Jan 27 08:55:08 centosD.localdomain systemd[1]: Starting VMware Internationalization Service...
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: start Singleton service
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: execute start function
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: executing:  /usr/local/vip/bin/start-vip.sh /usr/local/vip/vip-manager-i18n-common.jar /usr/local/vip/work/vip-runtime.log /usr/local/vip/work
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: =====startup singleton=====
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: found java home:  /etc/alternatives/jre
Jan 27 08:55:08 centosD.localdomain init.sh[14040]: run singleton from:  /usr/local/vip/vip-manager-i18n-common.jar
Jan 27 08:55:08 centosD.localdomain systemd[1]: Started VMware Internationalization Service.

7. After successful installation restart the RAAS service:
   systemctl stop raas
   systemctl start raas
8. The error should disappear from the logs.