Aria Automation Code Stream Pipelines executions are failing to open with "Illegal base64 character a" error

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Aria Automation Code Stream Pipelines executions are failing to open with "Illegal base64 character a" error:
  

Environment

VMware vRealize Automation 8.x

Cause

• The issue happens due to change in a package of the base64 library which uses an encoder and decoder. 
  After the March release, the base64 library from java.util package is being used, which does not allow storing \n as a character in the encoded form. 
  Since, some executions that were triggered before March 11th (before the upgrade) and completed after the upgrade are there in the database which have \n as the character in encoded form, the new decoder from base 64 library from java.util package is not able to decode properly and that is the reason why following error Illegal base64 character a.
• Before March 11th, 2023 (March cloud release date), the base64 library from vPostgres version 42.2.18 util package is being used, in which the encoder allowed storing \n as a character in the encoded form and the corresponding decoder was able to decode it properly. 

Resolution

VMware is aware of this issue and is being considered for inclusion in a later release. 

See the Workaround section below for more information.

Workaround:
For older executions which are impacted by this issue, you may retrieve the data of the pipeline execution via Postman or any API client tool by passing the REST API call with the following query parameters, expand=PIPELINE and expand=PIPELINE_STAGE, similar to the example below:

curl --location --request GET 'https://api.mgmt.cloud.vmware.com/codestream/api/executions/########-####-####-####-########c74a?expand=PIPELINE_STAGE' --header 'Authorization: Bearer value_of_token'

Additional Information

Impact/Risks:
Older executions of a pipeline before March release will have this issue.