Skip to content

Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose, on a Virtual Machine encrypted using BEK "without AAD". #6325

@Diofe

Description

@Diofe
  • If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Related command

Extension name (the extension in question)

Vm-repair

Description of issue (in as much detail as possible)

Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose --debug, on an Virtual Machine encrypted using BEK "without AAD".

We are getting the error:

cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/invocation.py", line 111, in _validation
self._validate_cmd_level(parsed_ns, cmd_validator)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 849, in _validate_cmd_level
cmd_validator(**self._build_kwargs(cmd_validator, ns))
File "/home/divyam/.azure/cliextensions/vm-repair/azext_vm_repair/_validators.py", line 64, in validate_create
encryption_type, _, _, _ = _fetch_encryption_settings(source_vm)
File "/home/divyam/.azure/cliextensions/vm-repair/azext_vm_repair/repair_utils.py", line 355, in _fetch_encryption_settings
if enabled.tolower() == 'false':
AttributeError: 'bool' object has no attribute 'tolower'

I suspected that this problem is related to:
f209607
#6238

Can you please check if this problem is related to da code change?


Metadata

Metadata

Labels

Auto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamCXP AttentionThis issue is handled by CXP team.Computecustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions