Bug #23543
closed
Package[foreman-proxy] foreman 1.16 and 1.17 install failure due to rubygem-rkerberos depends not found
Description
p5foreman: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'
p5foreman: /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
p5foreman: /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install fore
man-proxy' returned 1: Error: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11(kadm5clnt_mit_11_MIT)(64bit)
p5foreman: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11()(64bit)
p5foreman: You could try using --skip-broken to work around the problem
Updated by Stephen Cooke over 6 years ago
I have noticed that fresh installs on Centos7.4 of foreman1.16 or above are failing due to 'foreman-proxy' returned 1: Error: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11(kadm5clnt_mit_11_MIT)(64bit)
p5foreman: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11()(64bit)
Where can I find a working version of "libkadm5clnt_mit.so" that will work or a version of "rubygem-rkerberos" that doesnt need it, or a version of foreman that dont need either.
my stable release of foreman 1.15, doesnt have this issue
Updated by Stephen Cooke over 6 years ago
Stephen Cooke wrote:
I have noticed that fresh installs on Centos7.4 of foreman1.16 or above are failing due to 'foreman-proxy' returned 1: Error: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11(kadm5clnt_mit_11_MIT)(64bit)
p5foreman: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11()(64bit)Where can I find a working version of "libkadm5clnt_mit.so" that will work or a version of "rubygem-rkerberos" that doesnt need it, or a version of foreman that dont need either.
my stable release of foreman 1.15, doesnt have this issue
https://bugzilla.redhat.com/show_bug.cgi?id=1330431
This issue is not fixed in RHE till 7.5 comes out, can some provide a workaround for everyone not using RHE7.5
having the older version of rubygem-rkerberos in a foreman repo may be a temp solution
Updated by Anonymous over 6 years ago
- Tracker changed from Bug to Support
Please see https://community.theforeman.org/t/rubygem-rkerberos-currently-not-installable-on-el7-5/8829 for more information and workaround details.
Updated by Stephen Cooke over 6 years ago
- Tracker changed from Support to Bug
- Difficulty set to medium
Stephen Cooke wrote:
Stephen Cooke wrote:
I have noticed that fresh installs on Centos7.4 of foreman1.16 or above are failing due to 'foreman-proxy' returned 1: Error: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11(kadm5clnt_mit_11_MIT)(64bit)
p5foreman: Package: rubygem-rkerberos-0.1.3-6.el7.x86_64 (epel)
p5foreman: Requires: libkadm5clnt_mit.so.11()(64bit)Where can I find a working version of "libkadm5clnt_mit.so" that will work or a version of "rubygem-rkerberos" that doesnt need it, or a version of foreman that dont need either.
my stable release of foreman 1.15, doesnt have this issue
https://bugzilla.redhat.com/show_bug.cgi?id=1330431
This issue is not fixed in RHE till 7.5 comes out, can some provide a workaround for everyone not using RHE7.5
having the older version of rubygem-rkerberos in a foreman repo may be a temp solution
I would like to answer my own question, please leave this available for others. The following repo can resolve "CentOS-CR.repo"
Updated by Stephen Cooke over 6 years ago
rubygem-rkerberos-0.1.3-5.el7.x86_64 : A Ruby interface for the the Kerberos library( this one works)
rubygem-rkerberos-0.1.3-6.el7.x86_64 : A Ruby interface for the the Kerberos library( this one breaks it)
Updated by Tomer Brisker over 6 years ago
- Translation missing: en.field_release changed from 296 to 360
Updated by Tomer Brisker over 6 years ago
- Project changed from Foreman to Smart Proxy
- Category changed from Smart Proxy to Packaging
Updated by Ewoud Kohl van Wijngaarden over 6 years ago
- Status changed from New to Resolved
- Triaged set to No
By now 7.5 has been out for a while and the issue should be solved.