-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Can't install ansible-2.10.7 with ansible-operator:v1.26.1 & 1.27.0 on s390x platform while 1.26.0 works #6342
Comments
ansible-operator:v1.27.0 has same issue. |
@YanFenGuo Thanks for raising this issue! We had a previous issue open that I believe is related to this (#6302) that we thought we had resolved but resulted in some build failures while we were trying to cut the v1.28.0 release. I think this particular error you are receiving is the exact problem we were encountering in our build process and we had significant trouble resolving that error. I recently created a PR (#6348) to revert our changes that led to the creation of #6302. The plan as of now is to make sure this fix lands in the v1.28.0 release successfully and then create patch releases for v1.26 and v1.27 that fixes the problem in v1.26.1 and v1.27.0. |
@everettraven , the PR (#6348) reset cryptography = "==3.3.2" . While is it possible for ansible-operator to preset cryptography to 39.0.1 or higher to address vulnerability CVE-2023-23931 on all supported architectures (including amd64/s390x/ppc64le). I noticed there is active PR for that #6297 but no further updates. |
@caixiangibm #6348 was reverting a bump to cryptography 39.0.0 that was made in #6269 . This caused some issues in our CI resulting in our s390x and ppc64le builds of the ansible-operator no longer working properly because the cryptography package does not have a wheel built by default for these architectures. We attempted to try and update the build process to build the cryptography package within the image but that would consistently fail in our CI resulting in no images being built and we were unable to figure out why. Due to this, our short-term plan is to stick with rolling back to cryptography 3.3.2 since that it what it was pinned to previously. We are still looking into and discussing longer term solutions. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
@everettraven , what about your long-term solution for cryptography version upgrade on s390x / ppc64le ? |
@caixiangibm Apologies for my delayed response! I just recently created a PR (#6483) that is a fairly large update to the ansible operator and dependencies. I included multi-stage builds in that PR in an attempt to make it so that these changes are also available on s390x and ppc64le architectures |
Thanks @everettraven , hope the PR to be merged soon and we will see it will be fixed in which version. |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
@everettraven , Found that the released version of quay.io/operator-framework/ansible-operator:v1.31.0 with your PR - #6483, and cryptography on amd64/s390x/ppc64le all at 41.0.2 version.
|
Hi @caixiangibm , this is because |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Bug Report
What did you do?
I'm trying to install Ansible 2.10 into ansible-operator:v1.26.1.
What did you expect to see?
I want to install Ansible 2.10 into ansible-operator:v1.26.1, I can do this with ansible-operator:v1.26.0, but not 1.26.1.
I can also do this on x86 or ppc64le, only s390x platform doesn't work.
What did you see instead? Under which circumstances?
Launch Ansible Operator with below command:
Then execute below commands to update Ansible:
It failed with below error:
Pls let me know how I can make this work. Thank you.
The text was updated successfully, but these errors were encountered: