Clicking on a JID hyperlink in Aria Automation Config will throw an error of "This job has either not returned, does not exist, or was executed against an inaccessible target group."

Products

• VMware Aria Suite

Issue/Introduction

Jobs submitted for Salt from the command line or within the Aria Automation Config (AAC) UI will run successfully, however, when clicking on its JID hyperlink in Aria Automation Config, it will throw an error of "This job has either not returned, does not exist, or was executed against an inaccessible target group."

Environment

Aria Automation Config (AAC) version 8.16.0 or higher

Salt version 3006.4 or higher

Cause

When Salt is integrated with AAC, it will create several cache database files with the sqlite3 extension in the /var/cache/salt/master directory (Review the "Understanding the sseapi_cache runner" section of the AAC documentation).  In this situation where the job results are not available, the sseapi-events.sqlite3 file may be too large for processing and may throw an error like "[sseape.utils.engine:212 ][INFO    ][1835] sseapi_event_queue: failed to send entries to SSE (will requeue): EOF occurred in violation of protocol (_ssl.c:2426)" in /var/log/salt/master.  Properties for this file are defined in /etc/salt/master.d/raas.conf within the "sseapi_events_queue:" section.

Resolution

1. Stop the salt-master service; systemctl stop salt-master
2. Delete /var/cache/salt/master/sseapi-events.sqlite3
3. Start the salt-master service; systemctl start salt-master
4. Confirm that a new /var/cache/salt/master/sseapi-events.sqlite3 has been created
5. Run a Salt job from either the command-line or the AAC UI to confirm that the job results are now available from the JID hyperlink