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

[azcli 2.48.1] Warning messages are considered as errors #26330

Closed
bcouavoux opened this issue May 4, 2023 · 3 comments
Closed

[azcli 2.48.1] Warning messages are considered as errors #26330

bcouavoux opened this issue May 4, 2023 · 3 comments
Assignees
@bebound @jiasli
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Installation question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Backlog

Comments

@bcouavoux
Copy link

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

Related command

All azcli commands that generate warnings

Describe the bug

Warning messages are considered as errors and fail all our pipelines with the failOnStandardError parameter set to true. In workaround, we are forced to go back over all our pipelines and set the parameter to false to resolve the problem. Already stated in this issue on version 2.45.0: #25406

To Reproduce

Expected behavior

Environment summary

Pipeline azure devops
Agent pool : ubuntu-latest
azcli version : 2.48.1

Additional context

Ex logs :

WARNING: Readonly attribute name will be ignored in class <class 'azure.mgmt.resource.locks.v2016_09_01.models._models_py3.ManagementLockObject'>
##[error]WARNING: Readonly attribute name will be ignored in class <class 'azure.mgmt.resource.locks.v2016_09_01.models._models_py3.ManagementLockObject'>
WARNING: Readonly attribute name will be ignored in class <class 'azure.mgmt.resource.locks.v2016_09_01.models._models_py3.ManagementLockObject'>
##[error]Script has output to stderr. Failing as failOnStdErr is set to true.
@ghost ghost added customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot Installation labels May 4, 2023
@ghost ghost assigned jiasli May 4, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented May 4, 2023

Thank you for opening this issue, we will look into it.

@ghost ghost added this to the Backlog milestone May 4, 2023
@yonzhan yonzhan added Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 4, 2023
@bebound
Copy link
Contributor

bebound commented May 5, 2023

This issue is not related to #25406.

Duplicate of #26155.

@bebound bebound closed this as completed May 5, 2023
@bebound bebound mentioned this issue May 10, 2023
Merged
3 tasks
@jiasli
Copy link
Member

jiasli commented Jun 14, 2023

The topic of using failOnStderr is tracked by #18372.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bebound bebound

@jiasli jiasli

Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Installation question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@bebound @jiasli @bcouavoux @yonzhan