[Azure] Launching a cluster that is just terminated with the same name can cause RoleAssigmentUpdateNotPermitted error

[Michaelvll]

This is because in our SkyPilot provisioner, we removed the uuid for the role of the deployment. We should add it back:

Original:

skypilot/sky/skylet/providers/azure/config.py

Line 129 in bce117d

cluster_id = "{}-{}".format(config["cluster_name"], unique_id)

Our SkyPilot provisioner:

skypilot/sky/provision/azure/config.py

Lines 121 to 126 in 61c9c87

	'clusterId': {
	# We use the cluster name as the unique ID for the cluster,
	# as we have already appended the user hash to the cluster
	# name.
	'value': cluster_name_on_cloud
	},

Version & Commit info:

• sky -v: PLEASE_FILL_IN
• sky -c: PLEASE_FILL_IN