Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Diofe opened this issue May 25, 2023 · 3 comments
Assignees
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team Compute customer-reported Issues that are reported by GitHub users external to the Azure organization. CXP Attention This issue is handled by CXP team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@Diofe
Copy link

Diofe commented May 25, 2023

  • 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?


@ghost ghost added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels May 25, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented May 25, 2023

Thank you for opening this issue, we will look into it.

@ghost ghost added the Compute label May 25, 2023
@ghost ghost added this to the Backlog milestone May 25, 2023
@ghost ghost assigned zhoxing-ms May 25, 2023
@ghost ghost added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team labels May 25, 2023
@yonzhan yonzhan added the CXP Attention This issue is handled by CXP team. label May 25, 2023
@ghost
Copy link

ghost commented May 25, 2023

Thank you for your feedback. This has been routed to the support team for assistance.

@Diofe Diofe changed the title Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose, on an Virtual Machine encrypted using BEK "without AAD". Unable to run az vm repair create -g {rg} -n {source-vm-name} --verbose, on a Virtual Machine encrypted using BEK "without AAD". May 25, 2023
@haagha
Copy link
Member

haagha commented May 26, 2023

@Diofe Thanks for reporting. This bug has been addressed by PR #6326

Please check if it works for you now.

@haagha haagha self-assigned this May 26, 2023
@Diofe Diofe closed this as completed May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team Compute customer-reported Issues that are reported by GitHub users external to the Azure organization. CXP Attention This issue is handled by CXP team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants