Failed Omnibus 15.5 RPM install gives successful exit code
Summary
When rpm fails to install the Omnibus RPM package due to hitting the FIPS mode bug, rpm reports exit code 0 (success).
From my customer:
When the
rpm -Uvh gitlab.x.y.z.rpmcommand is executed, when it failed with this FIPS issue, the exit code of therpmbinary was0(success), even though the post-install script was displaying an error message.
The error message mentioned is from the aforementioned issue.
Steps to reproduce
- Induce #7275 (closed)
- Check status code of
What is the current bug behavior?
The RPM fails to install but gives success exit code 0
What is the expected correct behavior?
rpm reports the correct exit code
Relevant logs
Relevant logs
1: from /opt/gitlab/embedded/lib/ruby/gems/2.7.0/gems/chef-config-17.10.0/lib/chef-config/config.rb:1284:in `enable_fips_mode'
/opt/gitlab/embedded/lib/ruby/gems/2.7.0/gems/chef-config-17.10.0/lib/chef-config/config.rb:1284:in `fips_mode=': This version of OpenSSL does not support FIPS mode (OpenSSL::OpenSSLError)
===
There was an error running gitlab-ctl reconfigure. Please check the output above for more
details.
===
warning: %posttrans(gitlab-ee-15.5.0-ee.0.el7.x86_64) scriptlet failed, exit status 1
=== end error output ===