Skip to content
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.

Sign up for GitHub

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

Jump to bottom

azure signalR is still updating even though the provisioning status shows succeeded. #23986

Open
xiaxyi opened this issue May 15, 2023 · 3 comments
Open

azure signalR is still updating even though the provisioning status shows succeeded. #23986

xiaxyi opened this issue May 15, 2023 · 3 comments
Labels
Service Attention Workflow: This issue is responsible by Azure service team. SignalR

Comments

@xiaxyi
Copy link

xiaxyi commented May 15, 2023

When deleting the signalR custom certificate/ domain, the resource can't be deleted because the parent siganlR resource is still in updating status, despite of the "succeeded" provisioning status returned by the API (409 conflict error).
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 15, 2023
@xiaxyi xiaxyi mentioned this issue May 15, 2023
Merged
@JackTn JackTn added SignalR Service Attention Workflow: This issue is responsible by Azure service team. labels May 15, 2023
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 15, 2023
@ghost
Copy link

ghost commented May 15, 2023

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sffamily, @chenkennt.

Issue Details

When deleting the signalR custom certificate/ domain, the resource can't be deleted because the parent siganlR resource is still in updating status, despite of the "succeeded" provisioning status returned by the API (409 conflict error).

Author: xiaxyi
Assignees: -
Labels:

SignalR, Service Attention, needs-triage
Milestone: -

@chenkennt
Copy link
Member

@ArchangelSDY please take a look

@ArchangelSDY
Copy link
Contributor

Ack. Already had some discussion with issue author. There will be an improvement in next release so hopefully resource deletion will not be blocked by background operations any more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Service Attention Workflow: This issue is responsible by Azure service team. SignalR
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ArchangelSDY @chenkennt @JackTn @xiaxyi