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.

Sign up for GitHub

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

Jump to bottom

New-ClientVM naming bug when TenantName ends in numeric value #14

Open

ghost opened this issue Oct 22, 2020 · 1 comment

Assignees

Labels

bug good first issue

ghost commented Oct 22, 2020

When I use TenantName "InTuneTraining987" and create 2x VMs in sequence, the resulting HyperV VM's are named:

InTuneTraining987_1 (correct)
InTuneTraining987_9872 (should be InTuneTraining987_2).

When I use TenantName "TestTraining" and create 2x VMs in sequence, the resulting HyperV VM's are named:

TestTraining_1 (correct)
TestTraining_2 (correct).

Could this be a bug that affects any TenantName that ends in a numeric value?

tabs-not-spaces added the bug label

tabs-not-spaces self-assigned this

tabs-not-spaces added the good first issue label

Owner

tabs-not-spaces commented Jun 8, 2021

More than likely. I'll review the naming code and try and replicate, remediate.

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