Unable to use the salt master target matching settings after upgrading Aria Automation Config to v8.17.0

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After upgrading Aria Automation config to version 8.17.0 and recreating the /etc/salt/master.d/raas.conf and /etc/raas/raas files as described in the upgrade documentation, grains from some minions (running on Windows OS's) are failing to show up in the the UI, which then creates an issue with grains matching for the Targe Groups.  You may see errors like the following in /var/log/raas/raas:

2025-04-03 17:20:43 EDT,770 [org_id:None][raas.utils.rpc                                                    ][ERROR   :216 ][Webserver:2194232] (psycopg2.errors.DuplicateTable) relation "_tgminions_tmp_XXXXXX" already exists
 
 [SQL: CREATE TEMPORARY TABLE _tgminions_tmp_XXXXXX (minion_id text)]
 (Background on this error at: http://sqlalche.me/e/13/f405)
 Traceback (most recent call last):
   File "sqlalchemy/engine/base.py", line 1276, in _execute_context
     self.dialect.do_execute(
   File "sqlalchemy/engine/default.py", line 608, in do_execute
     cursor.execute(statement, parameters)
 psycopg2.errors.DuplicateTable: relation "_tgminions_tmp_XXXXXX" already exists

Environment

A manually deployed Aria Automation Config environment running on RHEL 8 with Salt version 3006.10 

Salt minion v3006.10 running on Windows servers

Cause

The minion is configured with multiprocessing enabled (multiprocessing: True).

Resolution

Create and set the multiprocessing configuration value to False since the default is True