microsoft / microsoft/MicroHack

[BUG] Zonal deployment of MH-Linux VM

Open
#256 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs triage
Dominant language
Jupyter Notebook
Stars
198
Forks
184
Avg merge
16h 57m
Merged PRs (30d)
70

Description

Is there an existing issue for this?
  • I have searched the existing issues
Microhack

03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native

Current Behavior

The mhX-linux vm is not deployed to an azure zone.

The "zones" definition is missing from the vm.bicep module.

Expected Behavior

@description('Virtual machine')
resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = {
name: Name
location: location
zones: zones

Steps To Reproduce

Deploy MH and try to do challenge 2.2

Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in 03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native and locate the vm.bicep module used for the mhX-linux VM. Compare its virtual machine resource with the expected zonal deployment, then deploy MH and try challenge 2.2 to confirm the VM is placed in an Azure zone.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.