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

Validation error when listing deployments in the dashboard from other clients #2364

Closed
A-Harby opened this issue Mar 6, 2024 · 12 comments
Closed
Assignees
Labels
dashboard type_bug Something isn't working
Milestone

Comments

@A-Harby
Copy link
Contributor

A-Harby commented Mar 6, 2024

Description

A clear description of the bug is:

Validation error from deployments made outside of the TS client, either go or terraform (name validation is different from go compared with the TS).
image

Must include any relevant identifiers like:

Steps to reproduce

  • Deploy a VM or K8s from a Go client, CLI, TFRobot, or even Terraform.
  • Navigate to the dashboard.
  • Connect your wallet with the same account.
  • Navigate to the deployment page and check the logs.
@A-Harby A-Harby added type_bug Something isn't working dashboard labels Mar 6, 2024
@ramezsaeed
Copy link
Contributor

@A-Harby
this is only for logs, or the deployment is not shown if the validation is different ?

@A-Harby
Copy link
Contributor Author

A-Harby commented Mar 7, 2024

No, The deployments were listed, but I was only testing listing from other clients so maybe it could cause a problem with adding a domain in vms or works in the kubernetes from ts client

@ramezsaeed ramezsaeed added this to 3.13.x Mar 7, 2024
@ramezsaeed ramezsaeed added this to the 2.3.0 milestone Mar 7, 2024
@ramezsaeed ramezsaeed removed this from 3.13.x Mar 7, 2024
@ramezsaeed ramezsaeed added this to 3.14.x Mar 7, 2024
@ramezsaeed ramezsaeed modified the milestones: 2.3.0, 2.4.0 Mar 7, 2024
@0oM4R 0oM4R moved this to Accepted in 3.14.x Mar 18, 2024
@zaelgohary zaelgohary self-assigned this Apr 14, 2024
@zaelgohary zaelgohary moved this from Accepted to In Progress in 3.14.x Apr 14, 2024
@zaelgohary zaelgohary moved this from In Progress to Accepted in 3.14.x Apr 14, 2024
@zaelgohary zaelgohary removed their assignment Apr 14, 2024
@xmonader xmonader modified the milestones: 2.4.0, 2.5.0 Apr 14, 2024
@amiraabouhadid amiraabouhadid self-assigned this May 1, 2024
@amiraabouhadid amiraabouhadid moved this from Accepted to In Progress in 3.14.x May 1, 2024
@Mahmoud-Emad
Copy link
Contributor

What is the status here?

@amiraabouhadid
Copy link
Contributor

amiraabouhadid commented May 2, 2024

Sorry for the delay took some time to investigate, was able to duplicate the error. Identifying the source of error in client.

@amiraabouhadid
Copy link
Contributor

Might be caused by inconsistent type casting in client.

@amiraabouhadid amiraabouhadid moved this from In Progress to Accepted in 3.14.x May 7, 2024
@amiraabouhadid
Copy link
Contributor

error is due to missing validations for number of characters in name in go client which is inconsistent with the validation implemented in the ts client. @A-Harby please list any other missing validations in go client. Please also let us know if validations are missing in terraform

@A-Harby
Copy link
Contributor Author

A-Harby commented May 8, 2024

The naming validation is different for every client (TS, GO, and Terraform). Only the TS client has an alphanumeric validation naming for any deployment name, disk name, and network name with a minimum and maximum length.

while the terraform doesn't have any length validation and can accept underscores only beside alphanumeric, and the same goes for the Go client so far(there could be a difference in some cases).

image

@amiraabouhadid
Copy link
Contributor

opened an issue for it in the go sdk here

@amiraabouhadid amiraabouhadid moved this from Accepted to In Verification in 3.14.x Jun 2, 2024
@ramezsaeed ramezsaeed removed this from 3.14.x Jun 10, 2024
@AhmedHanafy725
Copy link
Contributor

@0oM4R
Copy link
Contributor

0oM4R commented Oct 23, 2024

should set the name length to 35 characters

and check for dashboard name length validation as well

@0oM4R 0oM4R added this to 3.15.x Oct 23, 2024
@0oM4R 0oM4R modified the milestones: 2.7.0, 2.6.0 Oct 23, 2024
@0oM4R 0oM4R moved this to Accepted in 3.15.x Oct 23, 2024
@amiraabouhadid amiraabouhadid moved this from Accepted to Pending Review in 3.15.x Oct 23, 2024
@amiraabouhadid amiraabouhadid moved this from Pending Review to In Verification in 3.15.x Nov 4, 2024
@A-Harby
Copy link
Contributor Author

A-Harby commented Nov 7, 2024

Verified, Devnet a004c81.

The Go client now has a length validation.
image
And the VM is showing successfully without any error.
image
But the VM isn't listed on the deployment page anymore, and I have reported it in a new issue.
image

@A-Harby A-Harby moved this from In Verification to Done in 3.15.x Nov 7, 2024
@A-Harby
Copy link
Contributor Author

A-Harby commented Nov 10, 2024

Add a new test case on Dashboard Suite: TC2927 - List deployment from different clients

Update validation in CLI: TC1492 - Deploy VM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard type_bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

8 participants