-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Time Series Insights] environment update: An operation is already in progress on the environment #9265
Comments
Thanks @jiasli for opening the issue. We're going to look into this. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Shipra1Mishra. |
Hi @jiasli , We could reproduce the issue and we're working on a fix. Thank you |
Hey @jiasli - I just got off a call with @riserrad and we were unable to repro this issue anymore, We see provisionig state az tsi environment gen2 update --resource-group kyrush-devtest --name kyrush-devtest28 --warm-store-config data-retention=P18D
{
"id": "/subscriptions/d431f80e-0a71-47c9-bb6a-2c0c65ae2afb/resourcegroups/kyrush-devtest/providers/Microsoft.TimeSeriesInsights/environments/kyrush-devtest28",
"kind": "EnvironmentResource",
"location": "westus2",
"name": "kyrush-devtest28",
"properties": {
"creationTime": "2021-05-20T22:50:55.1871149Z",
"dataAccessFqdn": "b38e4feb-ff07-452f-8eeb-1f799a7d19dc.env.crystal-dev.windows-int.net",
"dataAccessId": "b38e4feb-ff07-452f-8eeb-1f799a7d19dc",
"provisioningState": "Updating",
"requestApiVersion": "2020-05-15",
"storageConfiguration": {
"accountName": "kyrushdevtest28"
},
"timeSeriesIdProperties": [
{
"name": "kyrush-devtest",
"type": "string"
}
],
"warmStoreConfiguration": {
"dataRetention": "P18D"
}
},
"resourceGroup": "kyrush-devtest",
"sku": {
"capacity": 1,
"name": "L1"
},
"tags": {},
"type": "Microsoft.TimeSeriesInsights/Environments"
} Please reopen this issue if it's reproduceable with the current CLI version. |
Originally posted at #8758 (comment)
The first environment update operation succeeds with 200, without any indication this is a Long Running Operation. Note that
"provisioningState": "Succeeded",
Then the following command fails because the previous operation hasn’t finished.
If the previous update operation hasn't finished, it should show
"provisioningState": "Updating"
.The text was updated successfully, but these errors were encountered: