aws / aws/amazon-sagemaker-feedback
Do not finish to update MLflow Tracking Server
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio
### Issue Description
After edit MLflow Tracking Server information, the status of tracking server is "Updating".
The status does not change even after 1 day.
As edit, I changed s3 path of Artifact storage location.
### Expected Behavior
Finished to update the MLflow Tracking Server
### Observed Behavior
Do not finish to update MLflow Tracking Server.
So I'm not able to update/delete the Tracking Server.
```
$ aws sagemaker stop-mlflow-tracking-server --tracking-server-name MLflowTrackingServerSandbox
An error occurred (ValidationException) when calling the StopMlflowTrackingServer operation: Tracking Server with ARN arn:aws:sagemaker:::mlflow-tracking-server/MLflowTrackingServerSandbox is currently in status UPDATING, can't be stopped.
$ aws sagemaker delete-mlflow-tracking-server --tracking-server-name MLflowTrackingServerSandbox
An error occurred (ValidationException) when calling the DeleteMlflowTrackingServer operation: Tracking Server is in un-deletable state (UPDATING), so it cannot be deleted.
```
### Product Category
Experiments
### Feedback Category
Error Handling and Debugging
### Other Details
> As edit, I changed s3 path of Artifact storage location.
The s3 path is include half space like the following.
`s3://XXXX /XXX`
Contributor guide
Research direction
No repository files or tests are identified. Start with the reported SageMaker Studio update and the stop/delete AWS CLI commands; confirm whether changing the S3 artifact path containing a space leaves the tracking server in UPDATING. Done means the update completes and subsequent stop or delete operations are no longer blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100