Open caarlos0 opened 5 years ago
Are you on a system with FIPS enabled?
Are you on a system with FIPS enabled?
AFAIK no, how can I double check?
@caarlos0 Check for the existence of /proc/sys/crypto/fips_enabled
and if it exists whether it contains a 1
. Lack of existence or a 0
in that file mean the system is not running in FIPS mode.
We ask because the OpenSSL FIPS module does not support MD5. Otherwise it is weird to see that not being supported. Lets check that first and if that is not the issue we will keep troubleshooting.
Description
This is a weird case, so I'm not sure if here is the right place...
Anyway, I have a Jenkins instance which runs several jobs (yeah, I know that the start of this story is already bad), some of them call chef, berks and etc.
We already had a very weird issue a few months ago related to kitchen docker driver and the container naming, which we worked around without finding out what's happening. +info
If we start jenkins using its provided init script (
service jenkins start
-> systemd calls the sysvinit script underneath and start it up), we get errors likeUnsupported digest algorithm (MD5)
onberks vendor
and also onkitchen test
.If I copy the
java -jar
cmd line and start it manually, everything works.ChefDK Version
Platform Version
Replication Case
That's the problem, I don't have one.
Stacktrace
I also did check, running from jenkins:
Seems like the correct version of openssl and all.
Before this berks issue started, we were running chefdk
3.1.0
. Back then, the only issue we had was the kitchen name thing. When we upgraded, we started to see the berks issue too.I'm happy to provide any more info you think is relevant... I've looked at so many things I'm not sure what really matters and what doesn't. Let me know!
Thanks