Project

General

Profile

Actions

ERF12-5287 » History » Revision 5

« Previous | Revision 5/9 (diff) | Next »
Dominic Cleal, 05/05/2015 03:57 AM
BZ was fixed in 7.1


ERF12-5287: Unable to create realm entry

Possible solutions to this issue:

Expired Keytab

Do you see an error like this in /var/log/foreman-proxy/proxy.log?

ERROR -- : Failed to initailize credentials cache from keytab: krb5_get_init_creds_keytab: Decrypt integrity check failed

Your Keytab may be expired. The keytab expiration follows your password expiration policies.

You can get a new one by:

# kinit admin@EXAMPLE.COM (or other suitable IPA admin)
# ipa-getkeytab -s ipa01.example.com -p realm-proxy@EXAMPLE.COM -k /etc/foreman-proxy/freeipa.keytab
# chown foreman-proxy:foreman-proxy /etc/foreman-proxy/freeipa.keytab

Wrong Size Error

Do you see an error like this in /var/log/foreman-proxy/proxy.log?

E, [2014-11-03T15:23:02.715791 #21273] ERROR -- : Wrong size. Was 307, should be 191

This is due to a bug in Ruby:
https://bugs.ruby-lang.org/issues/8182

This has been fixed in RHEL 7.1 + rebuilds, please run yum update ruby. The relevant bugzilla
is: https://bugzilla.redhat.com/show_bug.cgi?id=1071187

On 7.0, you can temporarily work around the problem by commenting these out on lines 505-506 in
/usr/share/ruby/xmlrpc/client.rb:

      #elsif expected != "<unknown>" and expected.to_i != data.bytesize and resp["Transfer-Encoding"].nil?
            #  raise "Wrong size. Was #{data.bytesize}, should be
            #  #{expected}" 

Updated by Dominic Cleal over 9 years ago · 9 revisions