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

Run testsuite on FIPS enabled RHEL host #12422

Closed
stianst opened this issue Jun 9, 2022 · 6 comments · Fixed by #17131
Closed

Run testsuite on FIPS enabled RHEL host #12422

stianst opened this issue Jun 9, 2022 · 6 comments · Fixed by #17131
Assignees
Milestone

Comments

@stianst
Copy link
Contributor

stianst commented Jun 9, 2022

The testsuite should have an option to run in FIPS mode and we need CI to run this. It may be just in the internal Jenkins pipelines, or also in GitHub Actions.

@mposolda
Copy link
Contributor

mposolda commented Feb 6, 2023

@rmartinc Assigning to you as it is related to #15069

@mposolda
Copy link
Contributor

@rmartinc I guess this can be considered resolved (based on your work on #15069, which is sufficient IMO). However I am not 100% sure if we need to test on ubi8 or ubi9. I've started thread on keycloak team ML with title "Do we target ubi8 or ubi9 for RHBK 22?"

So until now, we can keep this open as placeholder to eventually update our testsuite to ubi9 if needed.

@rmartinc
Copy link
Contributor

Yes, I think this one is for the moment not needed if nobody says the contrary. The current github-actions use the ubi8 image but I suppose we can use ubi9 if necessary (although not checked).

@mposolda
Copy link
Contributor

@rmartinc Official Keycloak container was updated to ubi9. See discussion on keycloak team mentioned above and also the related PR #17058 . So looks like we can also update fips tests to use ubi9 in GH actions?

@rmartinc
Copy link
Contributor

Yes, we can do it. Do you want to use this issue for the PR?

@mposolda
Copy link
Contributor

Yes, we can do it. Do you want to use this issue for the PR?

@rmartinc +1

rmartinc added a commit to rmartinc/keycloak that referenced this issue Feb 15, 2023
mposolda pushed a commit that referenced this issue Feb 15, 2023
@mposolda mposolda added this to the 21.0.0 milestone Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants