You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, pasting this text into the configured Secrets ARN fails to pass the validator:
{
"configurationValidationErrors": [
{
"level": "ERROR",f
"type": "MungeKeySecretSizeAndBase64Validator",
"message": "The content of the secret arn:aws:secretsmanager:us-east-2:[redacted]:secret:pcluster-default-munge-key-YYYYYY is not a valid Base64 encoded string. Please refer to the ParallelCluster official documentation for more information."
}
],
"message": "Invalid cluster configuration."
}
I got the same results using dd and the suggested Python code. Any suggestions would be welcomed with open arms.
Required Info:
AWS ParallelCluster version [e.g. 3.1.1]: 3.10.1
The text was updated successfully, but these errors were encountered:
I followed the guidance outlined here to generate a custom Munge key: https://docs.aws.amazon.com/parallelcluster/latest/ug/Scheduling-v3.html#yaml-Scheduling-SlurmSettings-MungeKeySecretArn
I tried using the
mungekey
utility and Base64-encoding the resulting file.However, pasting this text into the configured Secrets ARN fails to pass the validator:
I got the same results using
dd
and the suggested Python code. Any suggestions would be welcomed with open arms.Required Info:
The text was updated successfully, but these errors were encountered: