ansible-builder is slow/sometime fail due to pip depsolver

[grimlokason]

Hello,

Is it possible to add the possibility to use a constraint file to avoid the check of outdated python package ?

In my case :

• lot of time lost due to PyJWT boto3 and botocore backtracking dependencies
• faillure because it want to install openshift==0.13.0 while there is a 0.13.1 available ( CF : Problem pip installing openshift==0.13.0 openshift/openshift-restclient-python#425 )

Best regards !

[wiad]

I am also hitting the error caused by ansible-builder downloading openshift==0.13.0

[Akasurde]

@grimlokason @wiad You can use requirements.txt to specify the constraints.

[wiad]

@Akasurde when i try this (openshift!=0.13.0) I get rid of the error but the ansible-builder command takes forever to complete because of pip backtracking dependencies (not just of the openshift package but for almost every package). After almost 5 hours I gave up and aborted the build.

[grimlokason]

You can use requirements.txt to specify the constraints.

Hello, @Akasurde

Every package within the requirements.txt is going to be installed, thats not what the constraints option of pip is doing.

[MallocArray]

I was able to speed up my builds by adding a minimum version to each item in the file

ucsmsdk>=0.9.14
pywinrm>=0.4.3

[grimlokason]

I was able to speed up my builds by adding a minimum version to each item in the file

ucsmsdk>=0.9.14
pywinrm>=0.4.3

Hello,
And how do you do when the package that is leading to the issue is not in your requirement file but is a dependencies ?
It's quite annoying in my point of view to have to add a dependencies in the requierement :/

[MallocArray]

And how do you do when the package that is leading to the issue is not in your requirement file but is a dependencies ?

I ended up just doing pip3 list after a successful build to show all installed packages and then added whatever they are currently running as the minimum to requirements.txt