Closed mleprince018 closed 1 year ago
looking into this issue thanks for flagging
I also experience this problem.
Not sure about the Authors problem, but for me, I was able to resolve this by making sure that the resource group is created somewhere near me.
The setup.sh
script explicitly creates the resource group in the location westus
. Me being in europe, if I change it to westeurope
everything works fine.
I guess this has to do with the azure portal taking some time to propagate changes made in the us region when querying from a European region. A fix could be to get the region of the cloud shell and creating the rg in that region or a region nearby
Hi
I also experienced this issue today, and managed to workaround it using @mettke 's suggestion. E.g. changing lines 13 and 34 to a local region (uksouth
in my case) allows the script to work fine.
Thanks.
The issue has been fixed. We changed the setup script to choose a region from a random list, rather than staying fixed with westus. This worked when testing, eliminating all errors.
Module: DP-900
Lab/Demo: 05 - Streaming Analytics
Task: 00
Step: 00
Description of issue: streaming/setup.sh fails to recognize iot hub in subscription despite azure portal showing it has been created.
Steps to issue:
bash setup.sh
and ran into the below error