Skip to content

az pipelines agent list returns invalid JSON #755

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

Closed
WillTheProgrammer opened this issue Aug 12, 2019 · 7 comments · Fixed by #787
Closed

az pipelines agent list returns invalid JSON #755

WillTheProgrammer opened this issue Aug 12, 2019 · 7 comments · Fixed by #787
Assignees
Labels
Area: ProToCol The bugs under ProToCol Team bug

Comments

@WillTheProgrammer
Copy link

Describe the bug
The command az pipelines agent list --pool-id [any valid pool id] return a JSON object that has two entries for oSDescription, the first key oSDescription always has a value of 'null'. This invalid format prevents it from being parsed.

To Reproduce
Azure Cli Version: 2.0.69

Azure-Devops extension version: 0.12.0

Steps to reproduce the behavior:

  1. login using az login
  2. setup defaults..
  3. az pipelines agent list --pool-id [any valid pool id] -- make sure to use a pool id that has agents associated.
  4. See error
@WillTheProgrammer WillTheProgrammer added Area: ProToCol The bugs under ProToCol Team bug labels Aug 12, 2019
@atbagga
Copy link
Collaborator

atbagga commented Aug 13, 2019

@WillTheProgrammer This is the json response I am getting.. the oSDescription is Null yes but I do not get the error.
image

The output should be compliant with the API output as described here.

Can you share more on what you are getting? Depending on the details I can work with the team owning that API to help fix it.

@atbagga atbagga self-assigned this Aug 13, 2019
@atbagga
Copy link
Collaborator

atbagga commented Aug 19, 2019

@WillTheProgrammer Awaiting details on this issue. It is not reproducible at my end. Please share more details like json output you are getting or debug logs of output in case of failure.

@WillTheProgrammer
Copy link
Author

WillTheProgrammer commented Aug 20, 2019

I am still seeing the error on my end. It appears to be present any time that there is an oSDescription available for the agent. I noticed that in your example you get back a single null description for 'oSDescription'. Could you try running this command on a pool-id with a pool that has an agent with an oSDescription that is not null? I believe that you will see the duplicate key (making it an invalid json) then.

Thanks!

@atbagga
Copy link
Collaborator

atbagga commented Aug 21, 2019

@WillTheProgrammer Thank you for sharing the details. I will give it a try.

@WillTheProgrammer
Copy link
Author

@WillTheProgrammer Thank you for sharing the details. I will give it a try.

@atbagga -> Any success?

@atbagga
Copy link
Collaborator

atbagga commented Sep 6, 2019

@WillTheProgrammer Was working on some other tickets. Will get back to this one next.

@atbagga
Copy link
Collaborator

atbagga commented Sep 12, 2019

Fix will be available in release 0.13.0 in next couple of weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: ProToCol The bugs under ProToCol Team bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants