You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regards to nsg.provisioning_state not in ['Creating', 'Updating'] at provision/azure/instance.py::open_ports, it seems like we are waiting until the provisioning_state is updated to move on from either 'Creating' or 'Updating'. But nsg.provisioning_state would not be updated as the .provisioning_state does not stay synced with Azure's backend unless we refresh by calling list_network_security_groups(resource_group) again. Hence, current bug stays in an infinite loop when nsg.provisioning_state was either 'Creating' or 'Updating' when first list_network_security_groups(resource_group)was called within the for-loop.
We must add a logic to refresh by calling list_network_security_groups(resource_group) each time the check fails.
Version & Commit info:
sky -v: PLEASE_FILL_IN
sky -c: PLEASE_FILL_IN
The text was updated successfully, but these errors were encountered:
Regards to
nsg.provisioning_state not in ['Creating', 'Updating']
atprovision/azure/instance.py::open_ports
, it seems like we are waiting until theprovisioning_state
is updated to move on from either'Creating'
or'Updating'
. Butnsg.provisioning_state
would not be updated as the.provisioning_state
does not stay synced with Azure's backend unless we refresh by callinglist_network_security_groups(resource_group)
again. Hence, current bug stays in an infinite loop whennsg.provisioning_state
was either'Creating'
or'Updating'
when firstlist_network_security_groups(resource_group)
was called within the for-loop.We must add a logic to refresh by calling
list_network_security_groups(resource_group)
each time the check fails.Version & Commit info:
sky -v
: PLEASE_FILL_INsky -c
: PLEASE_FILL_INThe text was updated successfully, but these errors were encountered: