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

[Bug]: Projects with uppercase letters fail to provision GCP instances #1247

Closed
r4victor opened this issue May 20, 2024 · 1 comment · Fixed by #1248
Closed

[Bug]: Projects with uppercase letters fail to provision GCP instances #1247

r4victor opened this issue May 20, 2024 · 1 comment · Fixed by #1248
Assignees
Labels
bug Something isn't working

Comments

@r4victor
Copy link
Collaborator

Steps to reproduce

  1. Create a project which name contains uppercase letters
  2. Submit a run to GCP
  3. Observe errors when provisioning an instance
Invalid value for field 'resource.name': 'MyProject-local-2-slimy-pig-1-0-0'. Must be a match of regex '(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)'

Actual behaviour

No response

Expected behaviour

No response

dstack version

master

Server logs

No response

Additional information

No response

@r4victor r4victor added the bug Something isn't working label May 20, 2024
@r4victor
Copy link
Collaborator Author

GCP has strict requirements on resource names.

For resources on Compute Engine, the resource name must meet the following format (unless specified differently in the documentation for creating that resource):

  • Be 1-63 characters in length.
  • Comply with RFC 1035 conventions.
  • Match the regular expression ^[a-z]([-a-z0-9]*[a-z0-9])?. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen.

https://cloud.google.com/compute/docs/naming-resources

Labels have similar requirements: https://cloud.google.com/compute/docs/labeling-resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant