Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create a valid Base64 encoded Munge key #6378

Closed
rmarable-flaretx opened this issue Aug 2, 2024 · 4 comments
Closed

Unable to create a valid Base64 encoded Munge key #6378

rmarable-flaretx opened this issue Aug 2, 2024 · 4 comments

Comments

@rmarable-flaretx
Copy link

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.

$ mungekey -c -k munge-custom.key -b 1024 -f
$ base64 -w 0 munge-custom.key

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
@hanwen-pcluste
Copy link
Contributor

Sorry for the late reply.
Please make sure the key is stored as "Plaintext" (instead of "Key/value") in secret manager.

@rmarable-flaretx
Copy link
Author

Hi @hanwen-pcluste - thanks for getting back to me.

The "Plaintext" field was explicitly used to save the key.
Screenshot 2024-08-10 at 12 10 05 AM

@hanwen-pcluste
Copy link
Contributor

So in the plaintext, please use the value directly (e.g. W0p...), instead of using the dictionary (e.g. {"xxx":"xxx"})

@rmarable-flaretx
Copy link
Author

Thank you, that did the trick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants