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

Disable FIPS support within JVM for Puppet #828

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Mar 15, 2022

Puppet does not currently support FIPS on EL8 and needs to be disabled in order to run on a FIPS enabled EL8+ machine within the Java stack. This solution includes the disable flag out right as it does not break on environments where the flag is not present.

A couple questions to consider:

a) should this be a configurable parameter?
b) should this only be included conditionally? (complicates the code a little bit)

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we discussed this should be limited to EL8. I'd still prefer a class parameter:

Boolean $disable_fips = $facts['os']['family'] == 'RedHat' && $facts['os']['release']['major'] == '8',

That way it can at least be modified via Hiera.

I also expect that the tests will fail on this.

@evgeni
Copy link
Member

evgeni commented Mar 15, 2022

Does the JVM on EL7 even know about that parameter, or would it ignore it? No need to make it conditional then ;)

@ekohl
Copy link
Member

ekohl commented Mar 15, 2022

I think I'd still limit it to the RH OS family. No need to set it on others, which just causes changes that result in a server restart there.

@ehelms
Copy link
Member Author

ehelms commented Mar 15, 2022

Tests passing now, let me know what you think of the revamped design.

manifests/server/puppetserver.pp Outdated Show resolved Hide resolved
@ehelms
Copy link
Member Author

ehelms commented Mar 16, 2022

@ekohl could you have another look?

@evgeni
Copy link
Member

evgeni commented Mar 16, 2022

Why didn't CI run on this (anymore)?

@evgeni evgeni closed this Mar 17, 2022
@evgeni evgeni reopened this Mar 17, 2022
@evgeni
Copy link
Member

evgeni commented Mar 17, 2022

Ubuntu failure looks unrelated.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ubuntu failure looks unrelated.

Yes, I haven't looked too deeply into why it doesn't work. I think that particular one has never worked.

@ekohl ekohl merged commit c78916e into theforeman:master Mar 17, 2022
@ekohl
Copy link
Member

ekohl commented Mar 17, 2022

Yes, I haven't looked too deeply into why it doesn't work. I think that particular one has never worked.

Oh, and to add to that: in a VM it does work. So it's somehow the interaction between docker and systemd. Note that on Focal we only test puppetserver on 7 so that it passes on 6 is just because the agent works on 6. Perhaps it's the same thing that we see PostgreSQL fail on puppet-foreman with Focal.

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

Successfully merging this pull request may close these issues.

4 participants