Skip to content

az lab vm show and az lab vm list response always have applicableSchedule and scheduleParameters as null #29132

Description

@joekru

Describe the bug

The json response for a VM in either 'az lab vm show' or 'az lab vm list' always has these 2 fields as null:

  • applicableSchedule
  • scheduleParameters
    I tried several permutations on a Lab VM to opt-in or opt-out of the shutdown schedule and change the shutdown time and time zone. The 2 fields show as null no matter what the VM settings.
    I did notice that opt-in to auto start adds a Tag to the Lab VM.
    I'm trying to produce a report that will let a lab admin know if a lab VM has been opted out of shutdown time or is running on a different shutdown schedule

Related command

az lab vm show -g myGroup --lab-name myLabName --name myVmName
az lab vm list -g myGroup --lab-name myLabName

Errors

No error messages are apparent to the user

Issue script & Debug output

nothing apparent in debug - commands complete successfully

Expected behavior

applicableSchedule and scheduleParameters should not always be null

Environment Summary

azure-cli 2.61.0

core 2.61.0
telemetry 1.1.0

Extensions:
costmanagement 0.3.0
quota 1.0.0

Dependencies:
msal 1.28.0
azure-mgmt-resource 23.1.1

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Joel.Kruse.azure\cliextensions'

Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb 6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Auto-AssignAuto assign by botDevtestlabaz labService AttentionThis issue is responsible by Azure service team.act-codegen-extensibility-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions