Azure / Azure/MachineLearningNotebooks

SnapshotException (status_code: 403)

未關閉
#1,176 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
doc-enhancement Metastore MLOps
主要語言
Jupyter Notebook
星號
4.4k
分支
2.6k
PR 合併指標
30 天內沒有已合併 PR

描述

Hi,

I have encountered SnapshotException with status code 403. It turns out that I have a read permission but not write permission for the subscription I was trying to submit my job to. It would be better if the error message was more informative.

This is the current error message
```
raise SnapshotException(get_http_exception_response_string(response))
azureml.exceptions._azureml_exception.SnapshotException: SnapshotException:
Message: {
"status_code": 403,
"url": "..."
}
InnerException None
ErrorResponse
{
"error": {
"message": "{\n \"status_code\": 403,\n \"url\": \"...\"\n}"
}
}
```

I think a better error message would be
```
Please make sure that you have write permission to subscription XYZ.
```

It might also be a good idea to document here what the typical causes for different status codes are.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 9c023d0b-94c0-8b80-3a43-e0d5beb2eefb
* Version Independent ID: 22714d0e-0f49-7264-5329-7c7b3e163d2d
* Content: [azureml.exceptions.SnapshotException class - Azure Machine Learning Python](https://docs.microsoft.com/en-us/python/api/azureml-core/azureml.exceptions.snapshotexception?view=azure-ml-py)
* Content Source: [AzureML-Docset/stable/docs-ref-autogen/azureml-core/azureml.exceptions.SnapshotException.yml](https://github.com/MicrosoftDocs/MachineLearning-Python-pr/blob/live/AzureML-Docset/stable/docs-ref-autogen/azureml-core/azureml.exceptions.SnapshotException.yml)
* Service: **machine-learning**
* Sub-service: **core**
* GitHub Login: @debfro
* Microsoft Alias: **debfro**

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

此 issue 指出 azureml.exceptions.SnapshotException,以及位於 AzureML-Docset/stable/docs-ref-autogen/azureml-core/azureml.exceptions.SnapshotException.yml 的 SnapshotException 參考來源;先追蹤 403 回應如何被呈現。完成的標準是提供更具資訊性的權限錯誤、記錄相關狀態碼的常見原因,然後驗證 403 情況。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
azure, machine-learning, python
領域
documentation, machine-learning
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。