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

ResponseError('too many 500 error responses') #14840

Open
jarpsimoes opened this issue Aug 19, 2020 · 4 comments
Open

ResponseError('too many 500 error responses') #14840

jarpsimoes opened this issue Aug 19, 2020 · 4 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. DevOps Service Attention This issue is responsible by Azure service team.

Comments

@jarpsimoes
Copy link

az feedback auto-generates most of the information requested below, as of CLI version 2.10.1

Describe the bug

When I trying delete board from project on command line with AZ CLI:
$ az boards area project delete --path [board_path] --project [project_name] --org [ORG_URL] --yes

I've got an error bellow:

request failed: Error occurred in request., RetryError: HTTPSConnectionPool(host='dev.azure.com', port=443): Max retries exceeded with url: /EX93137/demo-project-automated/_apis/wit/classificationNodes/areas/ (Caused by ResponseError('too many 500 error responses',))

To Reproduce
Run command:
$ az boards area project delete --path [board_path] --project [project_name] --org [ORG_URL] --yes
on terminal

Expected behavior
The selected board being deleted from project

Environment summary

azure-cli                         2.10.1

command-modules-nspkg              2.0.3
core                              2.10.1
nspkg                              3.0.4
telemetry                          1.0.4

Extensions:
azure-devops                      0.18.0

Python location '/opt/az/bin/python3'
Extensions directory '/home/ex93137/.azure/cliextensions'

Python (Linux) 3.6.10 (default, Aug  6 2020, 08:50:28) 
[GCC 9.2.1 20191008]
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 19, 2020
@yonzhan yonzhan added the Service Attention This issue is responsible by Azure service team. label Aug 19, 2020
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Aug 19, 2020
@yonzhan yonzhan added bug This issue requires a change to an existing behavior in the product in order to be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 19, 2020
@yonzhan
Copy link
Collaborator

yonzhan commented Aug 19, 2020

boards

@yonzhan yonzhan added the DevOps label Aug 20, 2020
@ghost
Copy link

ghost commented Aug 20, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @narula0781, @ashishonce, @romil07.

@yonzhan
Copy link
Collaborator

yonzhan commented Aug 20, 2020

devops

@azure-sdk azure-sdk added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Sep 24, 2020
@Winson-030
Copy link

Is this issue solved?

ERROR: Error occurred in request., RetryError: HTTPSConnectionPool(host='dev.azure.com', port=443): Max retries exceeded with url: /x/x/x/x (Caused by ResponseError('too many 500 error responses'))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. DevOps Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jarpsimoes @azure-sdk @yonzhan @Winson-030