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.

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

Azure CLI task was failing with ERROR: An error occurred. Pip failed with status code 1. #6030

Closed
Prudhvi1236 opened this issue Mar 17, 2023 · 14 comments
Assignees
Labels
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. issue-addressed This issue is addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@Prudhvi1236
Copy link

We are using azure CLI task in our pipeline to connect to our azure postgres flexi server to run scripts. Below is the command we have used in our AZ CLI task.

            "  **az config set extension.use_dynamic_install=yes_without_prompt** "

FYI : day before yesterday also the task works fine, but from yesterday onwards I am getting below error.

WARNING: The command requires the extension rdbms-connect. It will be installed first.
ERROR: An error occurred. Pip failed with status code 1. Use --debug for more information.
##[error]Script failed with exit code: 1

Seems issue with installing the extension, kindly help.

@ghost ghost added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Mar 17, 2023
@yonzhan yonzhan added this to the Backlog milestone Mar 17, 2023
@yonzhan yonzhan added the Azure CLI Team The command of the issue is owned by Azure CLI team label Mar 17, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented Mar 17, 2023

@kairu-ms for awareness

@kairu-ms
Copy link
Contributor

Hi @Prudhvi1236, could you provide the version of rdbms-connect and azure-cli. It seems caused by dependencies issues.

@bebound
Copy link
Contributor

bebound commented Mar 17, 2023

Please provide the output of az extension add -n rdbms-connect --debug

@Prudhvi1236
Copy link
Author

@kairu-ms

Azure CLI task version is 2
for rdbms-connect, I was not adding version externally so I think it will consider the latest version whatever.

@Prudhvi1236
Copy link
Author

Prudhvi1236 commented Mar 17, 2023

@bebound

Please find the log output file.

@thrsn-ur
Copy link

tasklog_13.log
Hi, we are also experiencing this issue in an Azure DevOps Release pipeline running Ubuntu 20.04. I have attached the logs.

@bebound
Copy link
Contributor

bebound commented Mar 17, 2023

I can repro it in version 2.46.
The error is

 ./psycopg/psycopg.h:35:10: fatal error: Python.h: No such file or directory
         35 | #include <Python.h>
            |          ^~~~~~~~~~
      compilation terminated.

@Prudhvi1236
Copy link
Author

Any alternative solution available for this?

@bebound
Copy link
Contributor

bebound commented Mar 17, 2023

Workaround:
Update setuptools to latest version:
/opt/az/bin/python3 -Im pip install -U setuptools

The bug is introduced by Azure/azure-cli#24992.
It is related to pypa/setuptools#3589

@thrsn-ur
Copy link

We are able to get the Release pipeline working with this workaround, thanks!

@Prudhvi1236
Copy link
Author

Prudhvi1236 commented Mar 17, 2023

One more workaround I identified, using ubuntu 18.04 my pipeline works well. but it is going to deprecate in future.

@yonzhan yonzhan added the issue-addressed This issue is addressed and ready to close. label Mar 17, 2023
@ghost
Copy link

ghost commented Mar 17, 2023

Hi @Prudhvi1236. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

@ghost
Copy link

ghost commented Mar 25, 2023

Hi @Prudhvi1236, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.

@ghost ghost closed this as completed Mar 25, 2023
@imranrazakhan
Copy link

I have to install rust and this error get resolved.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. issue-addressed This issue is addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

7 participants