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

Failed to get client due to [digital envelope routines: EVP_DigestInit_ex] disabled for fips #427

Closed
Magoa opened this issue Feb 7, 2022 · 11 comments

Comments

@Magoa
Copy link

Magoa commented Feb 7, 2022

Info:
Using ansible community.kubernetes.k8s module, which uses this openshift python package, to run tasks on kubernetes.

Problem occurred using: 0.13.1
Workaround: Continue using 0.12.1

Have cluster that is FIPS compliant, noticed that while attempting to run k8s module tasks w/ updated openshift dependency, we would fail to deploy and have below error in logs.

02:50:12 msg: 'Failed to get client due to [digital envelope routines: EVP_DigestInit_ex] disabled for fips'

@venkataramanam
Copy link

Yes, it is confirmed that 0.13.1 has an issue.
0.12.1 works for us.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2022
@venkataramanam
Copy link

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 19, 2022
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 18, 2022
@aaronmcohen
Copy link

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 18, 2022
@venkataramanam
Copy link

This has now been resolved.
operator-framework/operator-sdk#5723 (comment)

@venkataramanam
Copy link

/close

@openshift-ci
Copy link

openshift-ci bot commented Oct 26, 2022

@venkataramanam: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

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.

@jmrodri
Copy link

jmrodri commented Oct 26, 2022

/close based on operator-framework/operator-sdk#5723 (comment)

@jmrodri
Copy link

jmrodri commented Oct 26, 2022

/close

@jmrodri jmrodri closed this as completed Oct 26, 2022
@openshift-ci
Copy link

openshift-ci bot commented Oct 26, 2022

@jmrodri: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants