Azure / bicep-registry-modules

Bicep registry modules
MIT License
493 stars 346 forks source link

[AVM Module Issue]: VMSSET with orchestrationmode = uniform is failing with one issue after the other #3634

Open janvanuytrecht opened 2 hours ago

janvanuytrecht commented 2 hours ago

Check for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/compute/virtual-machine-scale-set

(Optional) Module Version

0.4

Description

Hi,

When trying to deploy with OrchestrationMode Uniform this is the sequence of errors we encountered, and how we tried to mitigate them. we left most other parameters with default values.

1/ PatchingMode Default AutomaticByPlatform OS: Linux ubuntu 22.04 gen2

Feature InGuestAutoPatchVmssUniformPreview fails to register. Registered it, it's stuck in state pending, this is more an issue on Azure side. Action: set to mode 'ImageDefault' for now, as workaround.

2/ networkApiVersion does not exist on networkprofile (if mode is Uniform?). Action: set in comment for now

3/ Health extension Error: Automatic repairs not supported for this Virtual Machine Scale Set because a health extension is not applied to all instances. Apply the health extension to all instances in the virtual machine scale set prior to switching to instance health repair mode.

Action: tried to add to the extensionHealthConfig object: autoUpgradeMinorVersion: true enableAutomaticUpgrade: true

Result: doesn't work. No clue how to resolve this.

Conclusion at the moment is that this module for orchestrationMode Uniform is not stable/ usable at the moment. We will use our own for now, alas.

(Optional) Correlation Id

No response

avm-team-linter[bot] commented 2 hours ago

@janvanuytrecht, thanks for submitting this issue for the avm/res/compute/virtual-machine-scale-set module!

[!IMPORTANT] A member of the @Azure/avm-res-compute-virtualmachinescaleset-module-owners-bicep or @Azure/avm-res-compute-virtualmachinescaleset-module-contributors-bicep team will review it soon!

microsoft-github-policy-service[bot] commented 2 hours ago

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.