Desktop Image Validation - Enhance NIC Naming Strategy

Avatar
Michel van Eeuwen

We use a naming convention for our Desktop images. Because of this the first part of the image name is the same for multiple images. When validating images at the same time for each desktop image an VM is created, the VM's gets the same (full) name as the desktop images. The NIC's created for these VM's are named like “val-<first 6 characters of Desktop Image Name>-nic”. 

The first VM that is created to validate the first image is without errors but during the creation of the NIC for the second VM an error occurs which says “Error: Network interface with same name (val-AVD-MC-nic) already exists (created by another task).”.

Is it possible to use another method for generating the name off the NIC for the validating VM in a way that conflicts will not occur?

5

Comments (3 comments)

Sort by
0
Avatar
Martijn Van Braeckel

Got the same issue and reported it as a bug at support but they suggested to create a feature request.

At the beginning of the ‘set as image’ task a check is performed if there are existing validation resources with the same name, but this check should be performed just before the validation vm is created. There is a chance more ‘set as image’ jobs run simultaneously causing failed validation steps.

0
Avatar
Carl Long
Thank you for submitting your feature request—we truly value input from our community.

Next steps:
     • We will review your request and update its status as it progresses through our evaluation process.
     • If any clarification is needed, we'll follow up with you directly in the comments.

We also encourage the community to influence our decision through comments, votes, and feedback.
1
Avatar
Stefan Stapf

Same “problem” here

Please sign in to leave a comment.