azure.devices: devices API group times out on deletion

[ytsarev]

What happened?

Encountered during work on upbound/official-providers#501 and upbound/official-providers#580.

uptest looks fine on apply but fails on deletion

   logger.go:42: 22:17:11 | case/0-apply | test step completed 0-apply
    logger.go:42: 22:17:11 | case/1-delete | starting test step 1-delete
    logger.go:42: 22:17:11 | case/1-delete | running command: [/home/runner/work/official-providers/official-providers/.cache/tools/linux_x86_64/kubectl-v1.25.0 delete managed --all]
    logger.go:42: 22:17:15 | case/1-delete | resourcegroup.azure.upbound.io "example-iothub-op-w4lol8oj" deleted
    logger.go:42: 22:17:15 | case/1-delete | iothubendpointstoragecontainer.devices.azure.upbound.io "example-op-w4lol8oj" deleted
    logger.go:42: 22:17:15 | case/1-delete | iothub.devices.azure.upbound.io "example-op-w4lol8oj" deleted
    logger.go:42: 22:17:15 | case/1-delete | account.storage.azure.upbound.io "exampleforiothub" deleted
    logger.go:42: 22:17:15 | case/1-delete | container.storage.azure.upbound.io "example" deleted
I0901 22:37:12.439416   16558 request.go:655] Throttling request took 1.041364398s, request: GET:https://127.0.0.1:40321/apis/pkg.crossplane.io/v1beta1?timeout=32s
    case.go:361: failed in step 1-delete
    case.go:363: command "$***KUBECTL*** delete managed --all" exceeded 1200 sec timeout, context deadline exceeded
Warning: events.k8s.io/v1beta1 Event is deprecated in v1.22+, unavailable in v1.25+

How can we reproduce it?

make uptest-local PROVIDER_NAME=provider-azure EXAMPLE_LIST=$(find provider-azure/examples/devices/*.yaml | tr '\n' ',')

What environment did it happen in?

• Crossplane Version: universal-crossplane-1.9.0-up.3
• Provider Name: azure
• Provider Version: 4542bf42d9911fb4377d33d8859de226d2046f26

[turkenf]

@ytsarev does this issue occur for all resources(yaml files) in the devices group?

[ytsarev]

@turkenf in the reproducer it was all yamls test. It was reported on Sep 2, 2022 , so many things have changed, worth the full retest to validate the issue

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions]

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!