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

[ImageBuilder] StatusCode of run operation doesn't define the statusCode of 200 #9233

Closed
wyunchi-ms opened this issue Apr 27, 2020 · 4 comments
Closed

[ImageBuilder] StatusCode of run operation doesn't define the statusCode of 200 #9233

wyunchi-ms opened this issue Apr 27, 2020 · 4 comments
Assignees
@danielsollondon
Labels
Compute - Images Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@wyunchi-ms
Copy link

After the long running operation from path /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.VirtualMachineImages/imageTemplates/{imageTemplateName}/run, service response 200 not 204, but 200 is not defined in the swagger.
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 27, 2020
@wyunchi-ms wyunchi-ms changed the title [ImageBuilder] StatusCode of run operation doesn't return 200 [ImageBuilder] StatusCode of run operation doesn't define the statusCode of 200 Apr 27, 2020
@feiyushi
Copy link
Contributor

feiyushi commented Apr 28, 2020 •
edited
Loading

Service returns 202 for this operation. Does it work?

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 1, 2020
@akning-ms akning-ms added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. Service Attention Workflow: This issue is responsible by Azure service team. labels May 1, 2020
@ghost
Copy link

ghost commented May 1, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @mjconnection, @Drewm3, @Vaibhav-Agar.

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 1, 2020
@akning-ms akning-ms removed customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 1, 2020
@Drewm3 Drewm3 assigned Drewm3 and danielsollondon and unassigned Drewm3 May 1, 2020
@Drewm3
Copy link
Member

Drewm3 commented May 1, 2020

@danielsollondon, could you look into this issue.

@feiyushi
Copy link
Contributor

feiyushi commented May 1, 2020

@wyunchi-ms Please let us know if you are unblocked since last time we chatted.

@feiyushi feiyushi mentioned this issue May 4, 2020
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danielsollondon danielsollondon

Labels
Compute - Images Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Drewm3 @zikalino @danielsollondon @feiyushi @wyunchi-ms @akning-ms