Failed to parse structured output from Universal Packages tooling (ArtifactTool)

[praveen-pk]

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name
az artifacts universal download Extension Name: azure-devops. Version: 0.17.0.

Errors:

Process ['/home/xxxx/.azure/azuredevops/cli/tools/artifacttool/ArtifactTool_linux-x64_0.2.151/artifacttool', 'universal', 'download', '--service', 'https://xxxx.yyyy.com/', '--patvar', 'AZURE_DEVOPS_EXT_ARTIFACTTOOL_PATVAR', '--feed', XXXX-release', '--package-name', 'PACKAGE_', '--package-version', 'VERSION', '--path', '.'] with PID 816 exited with return code -6

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Put any pre-requisite steps here...
• az artifacts universal download --verbose --organization {} --feed {} --name {} --version {} --path {}

Expected Behavior

Environment Summary

Linux-4.4.0-18362-Microsoft-x86_64-with-fedora-31-Generic
Python 3.7.6

azure-cli 2.1.0

Extensions:
azure-devops 0.17.0

Additional Context

[praveen-pk]

This bug is being tracked internally, closing this external duplicate.

[andreiverdes]

Any news on a fix?

[karataliu]

@praveen-pk is there any update on this?

[praveen-pk]

I pinged the team that owns this bug. The owning team will provide an update on this bug.

[ankur8]

any update on this we are getting on centos machine same error ?

[lynshi]

I ran into this error when trying to download a universal artifact while building a Docker image based on debian:latest, and the workaround I used was to do

RUN export DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 && az artifacts universal download <...>

I found this workaround from this dotnet issue based on the output shown with --debug on the az artifacts universal download command.

Note that an Azure DevOps PAT is required to enable az artifacts universal download in the Dockerfile; for example;

RUN echo ${FEED_TOKEN} | az devops login --organization <organization>

---

I think #826 might be related to this issue.

[ggirard07]

Same issue here while running this command from docker image python:3.9-slim-buster