Upgrade issue with VCF Salt (formally Aria Automation Config) v8.18.3+

Products

• VCF Automation

Issue/Introduction

Following the migration to Valkey, the RaaS service may fail to run, generating errors like the following in the raas application log.

TypeError: 'NoneType' object is not subscriptable and Connection to Redis lost

Environment

Standalone Aria Automation Config deployment on an RHEL base OS

Cause

Mismatched credentials in the original /etc/raas/raas.secconf file

Resolution

RaaS Connection to Valkey Failing

• This connection failure occurs if the legacy Redis configuration utilized a different password than the standard password applied during the new Valkey installation, causing a mismatch with the existing encrypted raas.secconf file.

• As a temporary troubleshooting step, adding a plaintext password directly to the /etc/raas/raas configuration file,
  (e.g., redis: url: redis://default:MyPassword@localhost:6379) will restore the connection because it takes precedence over the raas.secconf file.

• To resolve the issue permanently and remove plaintext credentials, administrators must regenerate the raas.secconf file using the Valkey password that was used during its installation.

• Reference Broadcom KB 390800 for specific steps on using GPG encrypted YAML to safely store password information for Redis/Valkey.