Azure / Azure/azure-quickstart-templates

DSC registration doesn't work when using generalized images

Open
#2,198 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

[201-vmss-automation-dsc](https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-automation-dsc)
### Issue Details

I have a generalized/custom image I'm trying to provision the VMSS based upon it.
It works, but then only one node gets registered on the DSC Automation Account.
### Repro steps (_if necessary, delete otherwise_)
1. Deploy the template;
2. Verify that everything was deployed and registered under DSC Automation Account;
3. Delete the Resource Group created on the previous steps;
4. Change the current image in the template to a custom/generalized one;
5. Deploy the updated template again;
6. Verify that everything was deployed, but not all VMs were registered under DSC Automation Account.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked 201-vmss-automation-dsc template and reproduce the deployment using a generalized/custom image after deleting the original resource group. Compare the VMSS instances with the nodes registered in the DSC Automation Account. Done means all provisioned VMs from the generalized image are registered under the DSC Automation Account.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.