Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

az resource delete not working as expected for Microsoft.EventHubs/namespaces

See original GitHub issue

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name az resource delete

Errors:

(InvalidResourceType) The resource type 'locations' could not be found in the namespace 'Microsoft.EventHub' for api version '2021-11-01'. The supported api-versions are '2017-04-01,2018-01-01-preview'.
Code: InvalidResourceType
Message: The resource type 'locations' could not be found in the namespace 'Microsoft.EventHub' for api version '2021-11-01'. The supported api-versions are '2017-04-01,2018-01-01-preview'.

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Create a event hub namespace
Delete with the following command
az resource delete --ids "/subscriptions/xxxx/resourceGroups/RG/providers/Microsoft.EventHub/namespaces/rrtest1" --verbose --debug

Expected Behavior

No error should show up. Delete is finished with success but an error occurs when getting the status of the operation.

Environment Summary

Linux-5.4.0-1073-azure-x86_64-with-glibc2.28 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.8.12
Installer: DEB

azure-cli 2.34.1

Extensions:
ai-examples 0.2.5
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

Adding full debug output for reference: deleteEHlog.txt

Adding a previous version explicitly works as a workaround.

az resource delete --ids "/subscriptions/xxxx/resourceGroups/RG/providers/Microsoft.EventHub/namespaces/rrtest1" --api-version "2018-01-01-preview" --verbose --debug

Issue Analytics

State:
Created a year ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

raribeiroMScommented, Mar 31, 2022

You are correct, it works like that. The thing is it should work without specifying a version, as it did. If I use this command, with a list of multiple resources with different versions, I expect it to work without specifying a version.

0reactions

navba-MSFTcommented, Apr 11, 2022

@raribeiroMS I have looped you offline with the Product Owners to keep the track of the release and tentative ETA for the fix. Until then you can use --api-version “2021-06-01-preview” parameter in the command. Please feel free to reopen this issue if you have any further queries.