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

Slurmqueue naming validation errors #6548

Open
QuintenSchrevens opened this issue Nov 6, 2024 · 2 comments
Open

Slurmqueue naming validation errors #6548

QuintenSchrevens opened this issue Nov 6, 2024 · 2 comments
Labels

Comments

@QuintenSchrevens
Copy link

QuintenSchrevens commented Nov 6, 2024

Issue: Error when using hyphens in SlurmQueue names

AWS ParallelCluster Version

  • Tested on versions: 3.10 & 3.11

Description

When configuring a cluster with hyphens in the SlurmQueue names, the following error occurs:

Example Configuration snippet:

SlurmQueues:
  - Name: a10-medium
    JobExclusiveAllocation: true
    ComputeResources:
      - Name: a10-medium
        InstanceType: g5.12xlarge
        MinCount: 0
        MaxCount: 4
        Efa:
          Enabled: true

Error Message

{
  "configurationValidationErrors": [
    {
      "level": "ERROR",
      "type": "NameValidator",
      "message": "Invalid name 'a10-medium'. Name must begin with a letter and only contain lowercase letters, digits and hyphens."
    }
  ]
}

Expected Behavior

The configuration should allow hyphens in SlurmQueue names without producing a validation error.

Steps to Reproduce

  1. Define a cluster configuration with a SlurmQueue name that includes hyphens (e.g., a10-medium).
  2. Attempt to create the cluster.

Request

Is there any plan to adjust the validation rules to allow hyphens in SlurmQueue names, or should I follow a different naming convention?

Thanks!

@hgreebe
Copy link
Contributor

hgreebe commented Nov 8, 2024

Hello, slurm queue names do allow hypens (ex: queue-0), however they must start with a letter. The example you gave starts with a number and therefore throws a validation error.

@QuintenSchrevens
Copy link
Author

Hi,

indeed your right, but even with the new update comment it errors

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

No branches or pull requests

2 participants